HN user

fatal94

25 karma
Posts0
Comments10
View on HN
No posts found.

You're being downvoted because you're pushing punishing a company for having a better product. They do not engage in anticompetitive practices, there is no enforced barrier to entry in the market nor do they gate entry like the companies you have listed. They are only a monopoly because they have the best product.

No amount of legislation can stop subpoenas, wiretapping and other extrajudicial means the US has used for data surveillance since the inception of the Patriot Act. With data privacy increasingly becoming a critical matter of national security, strengthening data sovereignty laws and holding corporations accountable was always the way forward.

Driving towards a solution of "imprisoning more people" as punishment rather than other punishment have never succeeded. Many states already have first time drug offender and strike programs, people are already imprisoned over a weekend for things even as simple as misdemeanor possession until they can get a bail set. Rehabilitative forms of punishments such as severe fines, community service or mandatory classes and broadcasting them is much more effective in actually driving down rates of impaired drivers.

Whats more, police officers already have a wide authority of judgement when considering these factors around marijuana impairment currently. Relying on subjective evaluation from FST and physical presentation will only result in a higher rate of non impaired drivers being imprisoned.

Ofc, and not everybody needs or cares for all the features Kafka has. Then use another known and tested messaging system. Use NATS or ZMQ. Or any cloud native pubsub system

My main point is, I have zero interest in creating novel solutions to a solved problem. It just artificially increases the complexity of my work and the learning curve for contributors.

What you're doing is fine for a homelab, or learning. But barring any very specific reason other than just not liking Kafka, its bad. The second that pattern needs to be fanned out to support even 50+ producers/consumers, the overhead and complexity needed to manage already-solved problems becomes a very bad design choice.

Kafka already solves this problem and gives me message durability, near infinite scale out, sharding, delivery guarantees, etc out of the box. I do not care to develop, reshard databases or production-alize this myself.

Sure, if you're working on a small homelab with minimal to no processing volume.

The second you approach any kind of scale, this falls apart and/or you end up with a more expensive and worse version of Kafka.