I stopped using Rust because the compiler is an unmitigated pain in the ass. I'm not a 5-year-old. I know damn well when something is safe. If I have to tag everything unsafe to access memory in an optimal way, then what is Rust bringing to the table other than frustration? I moved over to Zig, which is much C-like, produces faster, smaller, and arguably just as safe binaries, and also happens to support C-FFI and cross-compilation out of the box. There is literally no advantage Rust has over Zig for C programmers.

I could argue that there's a shortage of houses because nobody will build me one for $5K. I wouldn't be wrong, but the trick to not being wrong is the $5K caveat, and that's the issue with all these labor shortage proclamations. Labor shortage always means there's "nobody willing to do this job for what I want to pay", not a blank "nobody is willing to do this job". I guarantee you, without a shadow of a doubt, if cleaning restrooms paid $750K a year, there would be an endless pool of labor for restroom cleaners.

Neither is Elordi

The good thing is hiring 9,000 H1Bs now could cost $900,000,000 in filing fees, and visas are weighted so that the highest wage H1Bs are given 4x the weight of the lowest wage H1Bs. I've noticed the number of H1B “entry-level openings" meaningfully decrease, which means it was never actually about talent "scarcity" and all about talent "cost". The H1B funnel is also getting a double whammy with AI consuming exactly the offshore-able, entry-level work the H-1B and offshore IT models were built around. The cost advantage that enabled both to work is at the point of economic unviability.

There is zero chance I'd go back to an ICE car. The maintenance, reliability, and fuel costs are not even comparable. The math behind driving an ICE car today only makes sense if you need to tow large loads for significant distances. The caveat is that you need a place to charge them for it to be stress-free. We calculated not long ago that it would take $0.25/gallon gas to make an ICE car break even with what we're spending on EVs.

"Windows is more for power users and MacOS is more for people who want their hand held"

That's the funniest thing I've read all day. Let me be blunt: macOS is an engineer's machine, Windows is for Susan in accounting. I spend 90% of my day in terminal windows on macOS, using make and compilers. I write code running on more machines, including Linux and Windows, on my Mac that you can even begin to imagine. I agree that Linux workstations tend to be used by more technical people. I have an ARM64 Ubuntu workstation myself, but to state that Windows is for "power users" shows that you have never worked in Silicon Valley circles. Virtually nobody in any form of advanced engineering uses Windows. The notable exception are a handful of terrible PCB design tools that are Windows only that everybody hates with a passion. Funny enough, most of them are now using AI agents to drive those tools ... from their Macs.

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

I remember that from the US automaker CEOs, so what possible harm could there be? We'll just ignore those Chinese EVs and keep buying ICE-powered vehicles, right? Ford stopped selling their F150 EV because nobody wanted them. GM is stopping production of the Bolt because nobody wants them. I mean who wouldn't want a $32K version of a $20K budget subcompact with zero amenities? So let BYD try to sell EVs nobody wants, it'll cost them a fortune, and they'll retreat having learned the lesson that internal combustion engines rule the day here. US automakers absolutely gave it their all by over-pricing and under-delivering on affordable EVs, it's all but certain BYD will fail the same way, right???

There is a part of me that is ever so slightly disappointed that they didn't emerge from the capsule wearing ape masks.

What if we enacted policies to make having children, you know, affordable?

We're cooked, literally