Hacker News .hnnew | past | comments | ask | show | jobs | submit | fatal94's commentslogin

The fact they were able to strike a deal in the first place hours after Anthropic was declared a supply chain risk should make this obvious. Their employees are smart people, the only way they can reason past this is their compensation.


Apparently Sam was secretly negotiating with DoD since Wednesday. While publicly proclaiming solidarity with Anthropic. Just vile, and expected.


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.


This is untrue. Subpoenas, wiretapping, and other extrajudicial means can be stopped by legislation that bans them. You can't say in one breath that legislation that enables it (Patriot Act) cannot be undone by more legislation. There are many hurdles required to produce the required legislation, which may not even be broadly supported by the public, but it isn't correct to say "no amount of legislation can stop existing legislation".


If they could be stopped by legislation that bans them, they would have been stopped by the legislation that banned them prior to the legislation that authorised them, but we know this is not the case. They were being done on a wide scale long before they were legal.


That would require to repeal the FISA and the Patriot acts. That won't happen.

More fundamentally, however, the US constitution only protects Americans and American companies. Europeans would be foolish to trust the US with their data given this lack of basic protection and oversight.


> That won't happen.

Never say never.


Extrajudicial means something not legally authorized. The surveillance apparatus in the US for decades has operated outside the confines of legality. By definition, they cannot be stopped by legislation that bans them.


A bad legislation is comparatively difficult to revert than a good legislation


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.


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.


I think there is a wide spectrum between small-homelab and google scale.

I was surprised how far sqlite goes with some sharding on modern SSDs for those in-between scale services/saas


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.


sqlite can do 40,000 transactions per second, that's going to be a lot more than 'homelab' (home lab).

Not everything needs to be big and complicated.


Some people don't and won't need 50+ producers/consumers for a long while, if ever. Rewriting the code at that point may be less costly than operating Kafka in the interim. Kafka is also has a higher potential for failure than sqlite.


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.


Okay, then those people don’t have to use Kafka. What is your point?


I was responding to someone who was responding to someone that wasn't using Kafka telling them to use Kafka. What's yours?


"Any kind of scale" No, there's a long way of better and more straightforward solutions than the simple SELECT

(SELECT * from EVENTS where TIMESTAMP > LAST_TS LIMIT 50) for example


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: