Farewell, mon capitaine. See you out there.

Millions of users don't have proper connectivity, they are stuck behind CGNAT and cannot self host or p2p. They are dependent on those walled gardens hosted by someone else.

The continued use of legacy IPv4 and slow rollout of IPv6 breaks that notion completely. Now you have a two tier system of users with full connectivity, and many millions of second tier users with partial connectivity stuck behind CGNAT.

These second tier users can't self host, can't p2p, and become dependent on additional third parties for things that first-tier users take for granted. Many of these third parties are abusive in various ways.

Back in the day you could host a low bandwidth chat server such as IRC, and high bandwidth activities like file sharing or video calls were direct p2p. Now many users cannot p2p so you need a high bandwidth and low latency server to relay all of that traffic. Only a few large players have the resources to do this.

Because there are so many second-tier users now this abusive system has become the norm, and many users aren't even aware of other options.

Normal industry: Your factory has an expensive milling machine and a cheap stamping machine. Thankfully, customers actually seem to prefer stamped parts for most cases and you can produce those quickly; so you keep stamping out parts and rolling in cash.

Tech industry: As above but your entire c-suite believes that the milling machine with turn into mecha-jesus and end history; so you are bulldozing everything you can to build more milling machines.

Your best engineers will be AuDHD, and AuDHD folk don't do well in these sorts of synthetic tests.

I can code in 20+ languages for over 12 different OS', write code that's good enough for CERN to run for particle accelerator data collection for a decade, have accelerated systems by an order of magnitude by understanding the poem space better than their previous engineers, but I am abysmal at exam style settings.

The software industry is riddled with SEs who write abysmal code but can pass a coding test easily. They're the folk that you have always needed to reject but didn't because they ticked a box.

If we build it, then it will frictionlessly tell us what to build.

It seems likely that the answer to this question is 'yes'; but it seems like a mistake to be distracted by it when we are talking about people who are, busily and intentionally, building 'AI' products against the public.

It's mildly comical when they attempt to emulate humanity; but the important bit isn't the cluelessness; it's the malice.

I suspect that this would be more tedious(and potentially less flattering); but you'd think that the metric you'd really care about for the juche-computer would be component availability.

Going by cost is interesting if you are trying to get the attention of balance-of-trade types and tariffs and dumping hawks; but it's an almost perfectly wrong measure if you are trying to catch any "oops, turns out that only the Chinese vendors so hungry they are considering offshoring to Vietnam still make a random passive or unexciting tolerances switching IC because it's a zero-margin part with no real room for differentiation that everyone who could got out of years ago" type situations.

If it's a real, drop-dead, 'national security' problem some of those are probably less serious, if there's a much fancier TI part that is overkill for the job but could be subbed in for only 3-4 factors of ten more; but if you want to keep economically viable civilian production open or it doesn't have a direct upmarket analog that could get really awkward; even if you've ensured that all the fancy logic ICs, copper, and gold are geopolitically friendly.

That's basically the Nexperia story, slightly simplified. Philips decided to private equity semiconductors generally; NXP decided to shove a bunch of the boring parts out to WingTech; then 'oops' European manufacturers who need diodes and ESD protection parts they thought were cheap jellybean stuff have cars piling up on the line because they can't get them.

Obviously losing a really cutting edge capability isn't preferred; but it's also the sort of thing that people notice because those tend to be pretty valuable; while low and middling capabilities, including ones that are sophisticated enough that you can't just throw money at restoring them fast, are things that are voluntarily surrendered because getting rid of low margin products makes line go up.

Sure there has been ARM64 windows for 5+ years, but it generally has poor reviews - compatibility issues (x64 emulation is only in userland so drivers won't work unless there's a native version), poor performance (mostly caused by emulation) etc.

Linux applications already natively support ARM64, and it runs the same kernel with the same drivers so most of these problems don't exist.

Apple are also in a much better place as they can mandate ARM64 as the only way forward. For Apple developers porting to ARM64 is a hard requirement unless you want to abandon your software, whereas for Windows developers porting to ARM64 is a cost with very little benefit. That's why virtually all mac software is now native ARM64, whereas for Windows it's a very small percentage.

This reminds me of a segment I saw about 15 or 20 years ago on a show called "How It's Made" that played on a channel like the Discovery Channel (before all cable became reality TV).

The segment was "How CRTs are Made". I was kind of surprised that CRTs were still being made, but I was especially surprised by the fact that they appeared to be American workers in the factory. They were doing everything pretty much by hand with no automation, and they were making some rather skinny looking CRTs. The show never elaborated on what the CRTs were for, but they sure didn't look like TVs.

I dug into it a bit after that using some clues I noticed in the show, and found out that these were cockpit displays for F15s or similar military aircraft. It's probably an item that you just don't go changing the specs on, and they understandably aren't going to farm out to TCL. I can't imagine how much each one cost, though. And I certainly wouldn't try to rack it up as a "win" for any of GWB's or Obama's trade policies.

This seems like a great pick if you want to be absolutely sure that your computing stays between you, the techbros, republican loyalists in 'national security'; and possibly an Israeli software partner or two.

At least no chicom lithium stealing your thoughts.

"with some employees complaining about issues with style, paragraph formatting, blank pages, and challenges with tracking changes." sounds like they got the replacement they were looking for to me.

But it's the same with any new technology, the incumbents hate it and either ignore it and hope it goes away, or try to push back against it, stifling progress. Usually this is a kneejerk response from people who are afraid of change and don't even understand the new tech.

Sensible people evaluate the new technology properly and determine how to make the best use of it, while understanding what weaknesses it might have and when its use might not always be the best option.

Anyone who dismisses a new technology without having properly tested and understood it is not worth listening to.

I didn't mean to imply that it is a single monolithic application, it does consist of several, but the relations must be pretty tight for there to be an article not even about language-independence; but about support for a single additional language, one often targeted by "C but cleaned up" efforts,

I was honestly surprised to see this myself. Regardless of its reputation for being more monolithic than classic init systems it still is, and has to be, capable of interacting with basically any flavor of service you'd want a service manager to manage; and I would assume that it doesn't include a d-bus implementation in order to not be capable of abstracted inter-process communication.

No doubt there are considerations at work here that I'm not smart enough to grasp; if you aren't having a bad time handling x.509 certificates you probably aren't doing it carefully enough; but I would not have expected it to be remarkable at all for a certificate-wrangling component to be implemented in a different language than some of the other components.

I assume that this is more pragmatic than just waiting for Sam to finish lying about transcendent AGI; but it feels a little dissonant to have the botmongers going back and forth between praising the glorious natural-language suitability of their progeny and putting together an entire platform, with more apparent effort than they have dedicated to human UI/UX considerations since sometime in win7(excluding dark pattern R&D) to aid you in discovering your sins against bot comprehensibility and fixing them.