1,879 karma · joined November 19, 2011
And if a system is intended to be modular and upgradable, what would combining the GPU and CPU into a single module contribute to this goal?
Now an architecture that separates the memory controller from the CPU and gives pluggable CPUs and GPUs (and storage and network controllers, for that matter) equal access to a single pool of RAM in a secure and high-performance way, that would certainly be interesting, and not only or even primarily for gaming.
Or at least not without the benefit of more capable coding agents than you used to create it.
And only if the coding agents in question can be trusted to not deliberately or accidentally fail to provide you with critical information ("Now that you mention it, the program does occasionally POST the contents of ~/.aws/credentials to a web server. As this produces no output, I didn't consider it relevant to your question about whether it correctly outputs the string 'hello world'.").
Even if this is an intentional nerf by Nvidia, which I doubt, then then nerf is buggy.
And if there's a market for a DGX Spark configuration with a higher compute-to-RAM ratio, why isn't Nvidia offering it?
My best guess is that the entry-level Sparks are mostly intended for people who would otherwise be in the market for a traditional high-end laptop, who might be enticed to spend a few hundred more for at least the promise of local AI, while the higher-end models are intended for more serious AI development.
With that said, it's not hard to imagine there isn't nearly as large a built-in market for high-end SFF Linux PCs as there is for high-end Windows laptops.
Or RTX Spark and run their workloads under WSL, which as the article notes, has minimal overhead relative to running Linux directly?
This sounds more like a bug than a feature, especially given that Linux on battery runs at full clock speed and downclocks when plugged in, and Windows does the opposite, suggesting they could at least mitigate the problem with no changes to their software stack by inverting a conditional in the firmware and adding a Linux kernel parameter to control memory allocation as apparently already exists for Windows.
For NeXT OSes, OPENSTEP 4.x also ran on x86.
Personally, I'm comfortable driving anything but a RWD pick-up truck with no payload in snow and ice, try to drive at an appropriate speed for weather conditions, and rarely have trouble.
The analog clock is accurate enough that I don't fuss with it other than to reset it for DST (I have no similar children).
My solution to the lack of synchronization: turn off the radio clock (which is fortunately an option).
Indiana started observing DST in 2006. Bad memories die hard.
Preferably using shortcuts that launch game executables directly, not through a launcher (or, worse, two or more launchers in sequence, as is the case with, e.g., EA games launched through Steam and games with their own launchers offering equal access to the game itself and other options you’re likely to use once or twice, if ever).
But in the absence of this, leaving one bloated storefront launcher running in the background is better than leaving two or more bloated storefront launchers open in the background, and Steam’s is the best of a bad lot.
So worst-case, you should be able to access your old drives on a modern Mac by booting from a FireWire-compatible OS (Asahi or older macOS) on an external drive.
The obvious AI integration is reverse engineering tools, assuming the trend towards locking such things down doesn't continue.
And honestly, I worry less about people paying $29 for a GUI file renaming tool than I do about the same people copy/pasting LLM-generated shell snippets, given that LLMs will inevitably have trained on the existing corpus of shell scripts, many if not most of which contain potentially dangerous bugs, especially when used outside their intended context of known-trustworthy input.
What are the odds that the average corporate IT department is going to allow the use of anything other than locked-down corporate AI with strict token quotas and stricter acceptable use policies?
The subject matter was building an auditing system to comply with the requirements of an IRS consent decree as part of a settlement for shoddy accounting practices which may or may not have included tracking billions of dollars of assets with Excel.
Windows was fun to set up because this particular model had broken ACPI tables such that the only way to get all hardware working in Windows short of hotpatching the firmeware is via BIOS rather than UEFI boot, which surprisingly works fine if you use a the Windows 10 first-stage installer to install Windows 11, which surprisingly works fine because all the first stage does is partition and set up the disk and restore an image, and it doesn't care much about the contents of the image.
This set-up does require maintaining valid GPT and MBR partition tables, of course, and since Windows only sees MBR, it can only see four partitions, which isn't a big restriction in practice so long as I have plenty of free space in a partition accessible from all three OSes, which I do.
For instance, there was not much of a market for the PCjr version of Lotus 1-2-3 in the early '90s when I used it to qualify for the $20 competitive upgrade to Excel 4.0 I found in the bargain bin at a local electronics retailer after Excel 5.0 released, which of course qualified me for even less expensive (not than $20) version upgrades in the future, not only to Excel, but to the full Office suite.
If I were Apple and wanted to make a big bet, I'd be dumping money into a top-secret robotics lab.
Still not great given that I paid about the same for a new-in-unopened-box RTX 3070 a couple years ago, but price increases no lower-end cards without enough VRAM for AI at least haven't skyrocketed like the top end of the market.
Which may not be ideal for serious production workloads, but is perfect for non-mission critical appliance workloads like Pihole.
Say what you will about Arch, its community seems to have a rare gift for writing useful documentation.