I'm sure if I cared enough to go looking, I'd find him contributing to the exact same authoritarian campaigns and bullshit.

Billionaires are like birds of a feather. Even Tim Cook donated to the stupid fucking ballroom. Why would I think any of these guys are "on our side" ?

So your take is that it's a nonviable solution for everyone, everywhere because you had a contractor who acted like a crook?

Meanwhile, when we moved into this house, I called up an electrician and had him come out the same week for a free estimate, and then the next week they put in exactly the circuit I needed for a very reasonable price.

Anecdote != data. Neither yours or mine.

Good lord.

You'll have to explain that one. Literally millions of installs out there, and we're not hearing of a large percentage of sudden and total roof compromise, are we?

Save the FUD for social media - we deal with facts and statistics here.

Fair enough.

It might be possible on a MacBook Pro with the "Max" CPU but I doubt it would sustain 100/sec

Especially since, if we're honest, most bugs and misses in software are bugs and misses in the spec.

No matter how experienced the entity is that is writing code, if you give a shit specification, you get a shit product.

Until Congress changes the name, there most certainly is.

Wank.

Just because you don't understand, doesn't make it not true.

Cosmic radiation indeed causes higher storage failure rates in avionics systems. However, because we can do things like redundant storage, the problem usually isn't in the file system, but the SSD firmware.

It's incredibly common to replace an LRU (Line Replaceable Unit), take the SSD out of the replaced LRU and reflash the firmware on it, and reinstall and test to find out that the device works perfectly again because it was a bit-flip in the SSD controller firmware.

Source: I am an avionics engineer.

It's not like this is new behavior from PHP.

It's not like PHP is the only choice.

This is called "risk management" and a good technical staff will be doing it constantly. If PHP is a problem, make a strategy to get the fuck off of it, and start executing.

Now only if there was a way to mirror the upstream, to render that risk null.

Oh, wait...

So what you are saying is that testing is still important.

When did it stop being important with meatspace coders? Why would you not critically test things that are critical, regardless of code source?

Horseshit.

Just because you haven't doesn't mean nobody can. Break a problem down into manageable sizes, and let it do the heavy lifting on those manageable chunks. You know, just like Agile development basically says to do. And then check the hell out of it, which you should be doing anyway regardless of where the code came from.

I've had plenty of luck using Qwen to get things done, because I don't expect to tell it some high-level goal and then walk away. Learn how the tool works, and then use the damn tool - it's no different then using any other tool.

There's other factors too. Example: if you don't need fast but you have a specific domain you're working in, you can throw regular RAM and CPU inference at doing things with a defined pattern.

For example, no software engineering manager wants to throw hours of work at refactoring declarative infrastructure-as-code to modern tooling from old shit - it's hours of work to arrive at the same place, but with better capability and supportability; classic tech-debt everyone loves to ignore until it's too late. So, instead, create a queue and a few mid-grade servers behind it running qwen3-coder and give it a good tuned prompt to convert some ancient CloudFormation shit to modern Pulumi in Go, using shared modules that you already wrote to abstract complexity and cloud best practices / secure design. Who gives a shit if it takes 3 hours to figure it out - that's still far less time than it would take an actual engineer to do it, and it's probably a best-case scenario for an AI: a tight declarative 1:1 target where you can compare the previous stack to the `pulumi preview` and know if you've hit the target or not.

Your engineers get to spend time doing useful productive product development where their time produces tangible value, and you get policy-compliant imperative IaC code for the cost of the electricity to run a few boxes you already own blinking away in the night, reducing technical debt.

It only "seems" inaccurate if you don't know the definition of genocide.

Hint: forced relocation == genocide. And Russia has been forcing Ukrainian children to relocate further into Russia for "Russification".

Does that shit count as genocide to you?

If Russia had the ability to "roll tanks into [Kyiv]" why haven't they done that?

Oh, they tried and got their asses kicked. And now they've been in a stalemate for ~2 years.

Your bullshit doesn't intersect with easily observed reality. Go fuck yourself sideways with a garden weasel, Putin shill.

It might surprise the hell out of you, but not everyone lives in a place with a population density of a thousand endpoints on a single node. Or even has a shared medium with all of their neighbors at all.

It might also come as a galloping shock that this solution may not be acceptable to 100% of the market. If you are outside of the target market... well, what is, is.