You misspelled "intrusive".

I've heard of traffic 'accidents' where a diabetic went hypoglycemic, passed out, and drove into other cars, pedestrians, etc. For some reason the news always reports it as a 'medical event', but the point is, people are killed by diabetics due to their diabetes way too often. It is an apt analogy. An idiot decides to drink and drive an puts people at risk. An idiot with diabetes fails to control their blood sugar and decides to drive, putting people at risk.

Yeah, it's easy to add more code to fix stuff that should be deleted. Just have the launcher code call your new code which bypasses all the old code. The old code can happily remain, it'll just never be called. No special skills required. If you look at the windows codebase, you'll see this technique everywhere.

He had WiFi or 4G on the aircraft carrier? I don't think so.

And if the Strava app uploaded the logged run later when it got connectivity at port or something, by then the ship was long gone.

> "The cloud" just means "Somebody elses C: drive"

Nah. Nobody is dumb enough to run a cloud service on Windows.

Keep your energy to provide it to Canadians for cheaper. The US has plenty of oil and coal I've been told.

Yes. So far, the LLM tools seem to be much more useful for general research purposes, analysing existing code, or producing example/prototype code to illustrate a specific point. I haven't found them very useful for much of my serious work writing production code yet. At best, they are hit and miss with the easy stuff, and by the time you've reviewed everything with sufficient care to have confidence in it, the potential productivity benefits have been reduced considerably. Meanwhile even the current state of the art models are worse than useless for the more research-level stuff we do. We try them out fairly regularly but they make many bad assumptions and then completely fail to generate acceptable quality code when told no, those are not acceptable and they really do need to produce a complete and robust solution of the original problem that is suitable for professional use.

But one of the common distinctions between senior and junior developers -- almost a litmus test by now -- is their attitude to new, shiny tools. The juniors are all over them. The seniors tend to value demonstrable results and as such they tend to prefer tried and tested workhorses to new shiny things with unproven potential.

That means if and when the AI code generators actually start producing professional standard code reliably, I expect most senior developers will be on board. But except for relatively simple and common scenarios ("Build the scaffolding for a user interface and database for this trivial CRUD application that's been done 74,000 times before!") we don't seem to be anywhere near that level of competence yet. It's not irrational for seniors to be risk averse when someone claims to have a silver bullet but both the senior's own experience and increasing amounts of more formal study are suggesting that Brooks remains undefeated.

and all the disgusting corporations putting profits above people's livelihoods along with it.

That is all.

I run Debian 13 and Chromium has been available as a package for a long time.

So I'm not sure why you would want to wait for Google to release Chrome on ARM, since it's essentially Chromium with Google's nastyware added to it. Just use Chromium.

Ads? Never saw that many, now I only see ONE on the page at all.

Guess you haven't heard of Brave and are still being tracked all over the internet,then.

Now I definitely know I don't want a Galaxy phone as my next phone.

And she's probably still a threat to national security!

Big Tech will buy the latest and greatest in power generation / suppliers, and the general population will be left with the legacy power infrastructure that will keep on aging and becoming more and more obsolete, because domestic power isn't where the big money is.

You can shove your dystopian future where the sun don't shine, is what I think.