The defense IMO is just trying to muddy the waters between "irreversible AI training that updates weights" and "AI learning by just storing secrets in text files".

Even in the 5% chance this AI model actually was fine-tuned or fully-trained (i.e the weights were updated), the employee did this while employed at Apple and used Apple IP as the training data. Even if the output is under fair-use (because it's transformative), (1) any IP created while employed during work duties almost always belongs to your employer and (2) the act of accessing Apple's IP would be (trade secret or regular) theft if done outside normal work duties.

I tried using the flatpak Chromium in case it was some NixOS build optimization oddities but didn't see much of a difference.

If you don't want to run Windows, is there even a choice? My issue now with the non-Apple computers if you want to run Linux it's really hard to predict how awful Chromium/Firefox will be. My work Dell Laptop is only a 3 year old CPU with integrated GPU (and unused Nvidia GPU) but Chromium and Firefox are both slow as shit just loading pages like Slack and Outlook. Even resizing the browser windows seems 4-5x times slower than my M3 Macbook Air.

Maybe this is strictly a Linux issue but it hardly matters when the Windows ecosystem is pretty stagnant, full of junk-ware, and software development is much, much better on Linux/MacOS.

My wife also drives a smaller Forester that we realize could have been an EV or hybrid. Although in CA, electricity is so expensive that it’s not much improvement over gas especially if you spend more on the car itself. Really, just a same model year but more fuel efficient sedan or one of those old 100-mile range EV cars is what you have to “downgrade” too.

Of course, it’s silly seeing all the oversized, sparkling clean massive trucks and SUVs on my commute while I’m driving my heavily scratched glorified minivan (since that’s what SUVs are now days).

Lots of dental stuff like Invisalign or even regular braces involve keeping plastic and adhesives in the mouth for long periods of time. I think even some gum (non-nicotine or otherwise) contain plastics technically.

If I’m spending $10K on something, I want the Android/iOS experience to be first-class instead of some shitty UI designed be people who I presume don’t drive cars.

Cars are otherwise fungible between brands. If one has CarPlay/Android Auto there is little reason to pick a brand that lacks support.

Using what? Using NixOS to configure a system is orthogonal to the system actually running the Nix binary. Nix/Nixpkgs provide well maintained package derivations and module configuration for the largest amount of software of any ecosystem. IMO it's far simpler than Yocto or Buildroot or the dozen OCI container builder ecosystems that go in and out of favor.

I’d still probably just implement this in Nix/Nixpkgs so I could leverage the rest of the ecosystem but that’s not trivial at all.

I wouldn’t even say Nix as a language is better than Starlark. The author is certainly well informed in the choices made.

build-vm is the same as building the configs “config.system.build.vm” attribute.

nixos-rebuild is fine for getting started but you end up needing to use the attribute path to do anything more complicated like CI caching or inspecting the drvPath.

$ my-arm-system = nixpkgs.lib.nixosSystem { system = "aarch64-linux"; modules = [ ./configuration.nix ]; };

$ :b arm-system.config.system.build.images.iso

Like the article points out, the software stacks people use for embedded devices are the same as people use non-embedded use; Rust, Go, NodeJS, and sure still C++. The only real difference with embedded devices is non-OS components like the bootloader (u-boot, EDK2) and customizing the device tree. (And of course firmware flashing). Fundamentally those are all just packages that I can describe in Nix. I don't need a separate tool just because the board is small.

IMO the embedded space, especially in the US, is already pretty Niche. Most companies either just ship the vendors BSP example (Ubuntu/Debian/Yocto) and pay very little attention to the detail or re-useablity. Once you vendor declares the BSP EOL you are stuck unless you re-implement it yourself.

Using Nix (or Guix) has the massive advantage of a large and active community that isn't fractured like the Yoctoo/Buildroot community. (By fractured I mean there may by many, many people using those tools at $DAYJOB but due to vendor BSP customization they likely share much less with the upstream community maintained sources).

Unfortunately that means they can play both cards, they can benefit from scarcity while pretending to be anti-gentrification. And they can claim any pro-housing group is actually “pro scary capitalist developer”.

IMO the danger to US service members outside of combat seems way too high. It's a well known fact most fatalities occur during training than during combat. (Sure this due to there being many more training exercises than active combat engagements but from a policy perspective it is very worrying).

https://en.wikipedia.org/wiki/List_of_accidents_and_incident...

The 7.84% state would probably be significantly diluted over this time frame so 4-5% is probably a more accurate estimate but perhaps high estimate.