So just run your own inference infrastructure then?

A traditional "developer" laptop generally costs around $2000-3000 for high end engineers. An extremely capable inference laptop, otherwise doing the rest of the same jobs, is around $5000-6000. One time cost. Everything runs locally, which also solves the "do I trust LLM vendor?" issue.

Yeah, they are. We know they are. That isn't magical knowledge. It happens in every country, and is mostly public knowledge. Guess who the US Military works with? Just look at publicly disclosed contracts. BAM, not that hard. Hell, AWS openly advertises its "Gov Cloud" region. Who the fuck do you think the "gov" is? Yeah. You think Alibaba doesn't do the same domestically? Of fucking course they do. Governments don't operate in vacuums, they have contracts with vendors to build shit, even if its the same shit a normal consumer can get.

Broadcom is also the manufacturer of the Internet's darling, the Raspberry Pi.

What you just described predates Linux by a couple decades.

The word you're looking for there is "UNIX" and there are still plenty of UNIX derivatives live and well today that never touched SystemD to begin with.

Adobe was one of the absolute earliest adopters into modern AI tech, so no, it has absolutely nothing to do with "riding the AI stock wave"

They were promoting AI tech a decade ago:
https://www.dpreview.com/news/...

And yes, it works amazingly well. That is a common tool used every day, as well as most of the other AI tooling in their products. The big difference is that the tools that have the "AI" label visually get the hate, the ones that dont have the "AI" label visually people love.

1) The Law is only 3 years old. This isn't some massive change, as it has barely been on the books at all.
2) It only applies to Federal facilities, not general data centers, so has absolutely NOTHING to do with all the other bullshit hype around AI datacenters.

"The deal is expected to close in the first half of 2027 with the companies forecasting $400 million in savings."

AKA: mass layoffs.

The part people miss is the assumption that "AI" = "LLM"

The reality is that "AI" = "Machine Learning"

What Meta (Facebook and their other properties) are using machine learning for? Ad delivery. They're working on more powerful and faster models for inference, not for text, but to service more targeted advertising based on more data on the individual.

This isn't just a theory or hyperbole, previous generations of Facebook "AI" accelerators have found their way onto the used market, ones used for this exact purpose internally.

It isn't visibly marketed as "AI" which is any nobody sees it as such, and thus why so many comments are saying "no" instead of "yes"

Office 2019 is available for Apple Silicon though. That's not the issue in question. The issue is that the "license" is tied to a certificate with a relatively short expiration date (the one mentioned next month) and Microsoft's refusal to issue an updated cert.

Something I've been toying with lately, LLMs can not only analyze the codebase, but also the git commit history and log messages. The developer intent IS there, it IS documented, but not in traditional documents that are easy for humans. These are instead in a form that is easy for LLMs to consume which then can summarize them back out into human readable documents. I've been using this for the exact reason described, I inherited several codebases after employee turnover with no chain of custody to bring forward that tribal knowledge directly.

So which is it, does the government love Flock data or hate it? I've lost track at this point.

The lack of consistency. I know the while "customize everything" is praised as good, but that only goes so far. We're to the point where there is so much fragmentation, its almost a form of anti-standardization. Just look at package management for example. A single application, in different packages (dnf/apt vs flatpak) for instance, will have wildly different permissions models to the point that things break in, like camera or screen sharing in Discord or similar applications. Its a complete mess, but bringing up these shortcomings, the answer is always something along the lines "well of COURSE that's how it works, you should have KNOWN that already! - deamonizing the end user for the shortcomings of the infra itself.

I'm not sure what you mean by "poorly" and "constant handholding"? Its full blown KDE on a very capable base operating system. Its at the point where Steam gaming is working, it has all the great server/developer tools needed for productivity, and pretty much any F/OSS app you can name on Linux is also on FreeBSD, but without most of the headaches of modern Linux.

Having more options for end-users is a good thing, not a bad thing.

at scale, EVERYTHING is an "eventual consistency" model, especially for global cloud providers. nothing is instant. it takes time to issue all the requests behind the scenes to all the targets and to get everything synced up properly.

should there be faster syncing for auth tokens? yeah, probably. but anyone who has done any admin work in any cloud environment probably knows that a ton of requests are no where near instant. you issue a command, and job workers async pull those requests and then act upon them. that's just how this shit works at scale.

Half of "Hollywood" content is filmed in Vancouver BC anyways. Problem solved!