computers

26 Apr 2026

Slashdot

Remembering The 1984 Unix PC. Why Did It Fail So Hard?

"I love these machines," writes long-time Slashdot reader Shayde: I was super-active in the Unix-PC Usenet groups back in the 90s... We hacked the hell out of them. They were small, sexy, and... they ran Unix! Unfortunately, they were a commercial failure. There were so many things wrong with them - not just stuff that broke, but the baseline configuration was nigh on worthless. I recently was able to get another machine and got it up and running (with a few hiccups). I whipped up a video showing all the cool things it can do, but also running through what went wrong and why it ultimately failed. The video shows the ancient green-on-black screen of 1984's AT&T Unix PC (with the OS running on a silicon drive emulation). The original machine had 512K of memory and a 10-megabyte hard drive described as slow, failure-prone, and noisy. There's also a drive for inserting floppy disks, and a separate MS-DOS board (with its own CPU) that could be plugged into the expansion slot - but the device was "remarkably heavy," weighing in aqt 40 pounds See the strange 1984 mouse, and its keyboard with both a Return key and a separate Enter key. There's even plug-in ports for phone landlines. "It looked great," Shayde says in the video, showing off its Spirograph demo and '80s-era games like Pong, Conway's Game of Life, GNU Chess, "Trk", and NetHack. But besides slow startup times, it was expensive - in today's dollars, it would've cost roughly $15,000 - and suffered from Unix's lack of spreadsheets, word processing software and other office productivity tools at the time. At that price the Unix PCs couldn't compete with IBM's home computers and their desktop applications. "It just didn't have the resources, the software, the capabilities and the price point that made it attractive."

How Will Apple Change Under Its New CEO?

How will Apple change in September under its new CEO - former hardware chief John Ternus? The blog Geeky Gadgets is already expecting "significant updates to the iPhone over the next three years," as well as streamlined internal engineering (plus durability enhancements and high-capacity batteries). 2026: Foldable display 2027: Bezel-less iPhone 20 (celebrating the iPhone's 20th anniversary) CNET's web sites (which include ZDNET, PCMag, Mashable and Lifehacker) are even hosting a contest "to see which of our readers can make the best Apple predictions for 2026. Answer five questions in any of our three rounds of the contest to be entered to win [$applePrize] in September." But the blog 9to5Mac already has a list of new upcoming Apple products, courtesy of Bloomberg's Mark Gurman (who appeared on the TBPN podcast this week "to talk about Apple's CEO transition, what to expect from John Ternus, and more." As part of the conversation, Gurman said: "There are six major Apple products in development right now, six major new product categories." Here's the full list he shared: 1. AI AirPods 2. Smart glasses 3. Pendant 4. Smart display 5. Tabletop robot 6. Security camera [...] Gurman has reported on the Pendant before as a new AI wearable that's an alternative to AI AirPods and Glasses. All three products are expected to rely heavily on a paired iPhone for Siri and other AI features. The smart display ('HomePad'), tabletop robot, and security camera are all brand new Apple Home products. The AI features arrive "thanks to the revamped Apple Foundation Models trained by Google Gemini," reports the AppleInsider blog (citing Gurman's Power On newsletter at Bloomberg). The smart doorbell camera will include "an Apple Intelligence-upgraded version of the facial recognition already included with HomeKit Secure Video. Today, HSV can utilize the Apple Home admin's tagged faces in their Photos app to label people that are viewed on the camera. When a known person rings the doorbell, Siri will announce them by name over the HomePod chime."

Ars Technica

Strange New Worlds S4 teaser strikes a more serious tone

"I have ever been prone to seek adventure and to investigate where wiser men would have left well enough alone."

26 Apr 2026 7:52pm GMT

Slashdot

Linux Version of Framework's Laptop 13 Pro is Outselling Its Windows Variant

Framework began shipping its new Laptop 13 Pro this week. And the Ubuntu variant is outselling the Windows variant, reports PC World: [I]t's selling quickly by Framework's internal metrics, with six batches of the Intel version of the laptop already sold out. [A later Framework social media post added "Spoke too soon, we're onto Batch 8."] "Also nice validation of our approach, the Ubuntu configurations are outselling the Windows ones!" That's not really surprising, for a few reasons. One, if you're buying a Framework laptop, you have a good reason to order it without an OS, even if you want Windows 11. It's easy to get it free or cheap elsewhere. (Framework says it's not counting the "None (bring your own)" option in these Ubuntu numbers.) Two, there are precious few places to order a new laptop with any kind of Linux pre-loaded - you've got Framework, a few smaller vendors like System76 and Slimbook, and a few models from Dell. Lenovo sold Ubuntu-loaded laptops at one point, but I can't find any on the site right now... Perhaps it doesn't hurt that Microsoft and Windows are currently on a bit of an apology tour. After a couple of years of pushing hard on "AI" features that no one wants - not even the people who do want "AI" want the Copilot flavor - Microsoft is pulling back its integration into everything and now promising features that Windows has been missing ever since Windows 10. Framework also reports that: More than one third of purchasers say they're replacing a MacBook Pro, "and almost all of them are switching to Linux (based on our optional post-purchase survey)." "Also in interesting sales data, the Gray/Black keyboard is vastly outselling the traditional Black one!"

Ars Technica

Prime Video drops full trailer for Spider-Noir

It's "a detective story, but the detective happens to also have spider powers."-EP Chris Miller

26 Apr 2026 5:20pm GMT

New robotic control software avoids jamming their joints

Software lets robots learn from each other even if they have different hardware.

26 Apr 2026 11:09am GMT

24 Apr 2026

OSnews

If 64bit Windows 11 contains a copy of 32bit explorer.exe, could you run it as its shell?

Raymond Chen published a blog post about how a crappy uninstaller on Windows caused a mysterious spike in the number of Explorer (Windows' graphical shell) crashes. It turns out the buggy uninstaller caused repeated crashes in the 32bit version of Explorer on 64bit systems, and - hold on a minute. The how many bits on the what now? The 32-bit version of Explorer exists for backward compatibility with 32-bit programs. This is not the copy of Explorer that is handling your taskbar or desktop or File Explorer windows. So if the 32-bit Explorer is running on a 64-bit system, it's because some other program is using it to do some dirty work. ↫ Raymond Chen at The Old New Thing So I had no idea that 64bit Windows included a copy of the 32bit Explorer for backwards compatibility. It obviously makes sense, but I just never stopped to think about it. This made me wonder though if you could go nuts and do something really dumb: could you somehow trick 64bit Windows into running this 32bit copy of Explorer as its shell? You'd be running 32bit Explorer on 64bit Windows using the 32bit WoW64 binaries where you just pulled the 32bit Explorer binary from, which seems like a really nonsensical thing to do. Since there's no longer any 32bit builds of Windows 11, you also can't just copy over the 32bit Explorer from a 32bit Windows 11 build and achieve the same goal that way, so you'd really have to go digging around in WoW64 to get 32bit versions. I guess the answer to this question depends on just how complete this copy of 32bit Explorer really is, and if Windows has any defenses or triggers in place to prevent someone from doing something this uselessly stupid. Of course, there's no practical reason to do any of this and it makes very little sense, but it might be a fun hacking project. Most likely the Windows experts among you are wondering what kind of utterly deranged new designer drug I'm on, but I was always told that sometimes, the dumbest questions can lead to the most interesting answers, so here we are.

24 Apr 2026 11:07pm GMT

8087 emulation on 8086 systems

Not too long ago I had a need and an opportunity to re-acquaint myself with the mechanism used for software emulation of the 8087 FPU on 8086/8088 machines. ↫ Michal Necasek Look, when a Michal Necasek article starts out like this, you know you're in for a learnin' ol' time. The 8087 was a floating-point coprocessor for the 8086 and 8088 processors, since back in those early days, processors did not include an integrated floating-point unit. It wouldn't be until the release of the 486DX, in 1989, that Intel would integrate an FPU inside the processor itself, negating the need for a separate chip and socket. Interestingly enough, Intel also released a cut-down version of the 486 with the FPU removed, the 486SX, for which an optional external FPU did exist.

24 Apr 2026 10:42pm GMT

How hard is it to open a file?

Sebastian Wick has a great explanation of why opening files - programmatically - is a lot more complex and fraught with dangers than you might think it is. This issue was relevant for Wick as he is one of the lead developers of Flatpak, for which a number of security issues have recently been discovered, and it just so happens that many of these issues dealt with this very topic. The biggest security issue found was a complete sandbox escape, originating from the fact that flatpak run, the command-line tool to start a Flatpak application, accepted path strings, since flatpak run is assumed to be run by a trusted user. The problem lay in a D-Bus service sandboxed applications could use to create subsandboxes, and this service was built around, you guessed it, flatpak run. The issues in question, including this complete sandbox escape, have been addressed and fixed, but they highlight exactly the dangers that can come from opening files. This subsandboxing approach in Flatpak is built on assumptions from fifteen years ago, and times have changed since then. If you're a programmer who deals with opening files, you might want to take a look at your own code to see if similar issues exist.

24 Apr 2026 8:24pm GMT