An LLM has “zero context” about your project’s specific stack and style guidelines. In other words, an AI might produce a generic <Modal> component, but integrating it into your app’s unique architecture is still a human task. This is very old. Nowadays, in Copilot for example, you add files to context and tell "hey look how I did that thing there, do this new thing following the same structure, with the same naming conventions" and it's enough. And tools like Cursor just throw your whole project into context by default.

Heck yeah! Gotta watch that again, thank you kind stranger!

which one would sell more I mean they would charge a lot of money for the stripped down one because it doesn't allow them to monetize it on the back end, and the vast majority would continue using the resource-slurping ad-riddled one.

Weird headline. Is it the city making this recommendation, or the... Despite universal opposition by the dozens of residents present at the meeting, commissioners voted to recommend changes to the city’s zoning laws to allow data centers in areas zoned for light industrial use and to rezone a 700-acre property from agricultural to light industrial to accommodate the construction of a hyperscale data center.

I really wish their whole lap-dock concept had succeeded. Or at least ran a few more generations, so I could get an upgraded model with USBc

Archive

Forgive me for not explaining better. Here are the terms potentially needing explanation. Provisioning in this case is initial system setup, the kind of stuff you would do manually after a fresh install, but usually implies a regimented and repeatable process. Virtual Machine (VM) snapshots are like a save state in a game, and are often used to reset a virtual machine to a particular known-working condition. Preboot Execution Environment (PXE, aka ‘network boot’) is a network adapter feature that lets you boot a physical machine from a hosted network image rather than the usual installation on locally attached storage. It’s probably tucked away in your BIOS settings, but many computers have the feature since it’s a common requirement in commercial deployments. As with the VM snapshot described above, a PXE image is typically a known-working state that resets on each boot. Non-virtualized means not using hardware virtualization, and I meant specifically not running inside a virtual machine. Local-only means without a network or just not booting from a network-hosted image. Telemetry refers to data collecting functionality. Most software has it. Windows has a lot. Telemetry isn’t necessarily bad since it can, for example, help reveal and resolve bugs and usability problems, but it is easily (and has often been) abused by data-hungry corporations like MS, so disabling it is an advisable precaution. MS = Microsoft OSS = Open Source Software Group policies are administrative settings in Windows that control standards (for stuff like security, power management, licensing, file system and settings access, etc.) for user groups on a machine or network. Most users stick with the defaults but you can edit these yourself for a greater degree of control. Docker lets you run software inside “containers” to isolate them from the rest of the environment, exposing and/or virtualizing just the resources they need to run, and Compose is a related tool for defining one or more of these containers, how they interact, etc. To my knowledge there is no one-to-one equivalent for Windows. Obviously, many of these concepts relate to IT work, as are the use-cases I had in mind, but the software is simple enough for the average user if you just pick one of the premade playbooks. (The Atlas playbook is popular among gamers, for example.) Edit: added explanations for docker and telemetry