Everywhere you look, the media is telling you that OpenAI and their ilk are the future, that they’re building “advanced artificial intelligence” that can take “human-like actions,” but when you look at any of this shit for more than two seconds it’s abundantly clear that it absolutely isn’t and absolutely can’t.

Despite the hype, the marketing, the tens of thousands of media articles, the trillions of dollars in market capitalization, none of this feels real, or at least real enough to sustain this miserable, specious bubble. People like Marc Benioff claiming that “today’s CEOs are the last to manage all-human workforces” are doing so to pump up their stocks rather than build anything approaching a real product. These men are constantly lying as a means of sustaining hype, never actually discussing the products they sell in the year 2025, because then they’d have to say “what if a chatbot, a thing you already have, was more expensive?”

↫ Edward Zitron

Looking at the data and numbers, as Zitron did for this article, the conclusions are sobering and harsh for anyone still pushing the “AI” bubble. Products aren’t really getting any better, they’re not making any money because very few people are paying for them, conversion rates are abysmal, the reported user numbers don’t add up, the projections from “AI” companies are batshit insane, new products they’re releasing are shit, and the media are eating it up because they stand to benefit from the empty promises.

Generative AI is a financial, ecological and social time bomb, and I believe that it’s fundamentally damaging the relationship between the tech industry and society, while also shining a glaring, blinding light on the disconnection between the powerful and regular people. The fact that Sam Altman can ship such mediocre software and get more coverage and attention than every meaningful scientific breakthrough of the last five years combined is a sign that our society is sick, our media is broken, and that the tech industry thinks we’re all fucking morons.

This entire bubble has been inflated by hype, and by outright lies by people like Sam Altman and Dario Amodei, their lies perpetuated by a tech media that’s incapable of writing down what’s happening in front of their faces. Altman and Amodei are raising billions and burning our planet based on the idea that their mediocre cloud software products will somehow wake up and automate our entire lives.

↫ Edward Zitron

In a just world, these 21st century snake oil salesmen would be in prison.

Broadcom has been closely examining Intel’s chip-design and marketing business, according to people familiar with the matter. It has informally discussed with its advisers making a bid but would likely only do so if it finds a partner for Intel’s manufacturing business, the people said. 

Nothing has been submitted to Intel, the people cautioned, and Broadcom could decide not to seek a deal. 

Separately, TSMC has studied controlling some or all of Intel’s chip plants, potentially as part of an investor consortium or other structure, according to people familiar with the discussions.

↫ Asa Fitch, Lauren Thomas, and Yang Jie at The WSJ

The vultures continue to circle, but considering Intel isn’t actually dead yet, it does all feel a little bit premature. The company needs time to right the ship, but with its current non-technical, finance-oriented leadership it might already be too late for such time to be given to the company. For all we know, they’re already working on a big payday through divestment or wholesale selling of the company, and they’re just waiting on the right offer.

I don’t think it’s a good idea to let Intel be stripped for parts and looted by the ultra-wealthy, but with the United States hurdling towards a massive constitutional crisis and experiencing utter destruction of government institutions, I don’t think anyone’s left to stop it or think things through properly.

AIDA64, the popular benchmarking tool for Windows, released a new version today. I don’t particularly care about benchmarking – even less so benchmarking on Windows – but this new release comes with an interesting line in the release notes.

Discontinued support for Windows 95, 98, Me

↫ AIDA64 v7.60 release notes

Seeing a widely-used, popular piece of software drop support for Windows 95, 98, and ME only in this, the year of our lord, 2025, is kind of amazing.

It’s been two years since the release of ArcaOS 5.1, which was a hugely important release because it brought UEFI support to this continuation of IBM’s OS/2, ensuring longevity for the project for years to come. Since I don’t think much is known about what, exactly, Arca Noae, and eComStation before it, has access to within the licensing agreement with IBM, it’s difficult to ascertain just how much room they actually have to make changes to the code at the core of the old OS/2. Regardless, I tested ArcaOS 5.1 before and during its release, and the support for UEFI and GPT partition layouts was excellent on my machines.

Almost 18 months later comes the next release in the 5.1 branch, ArcaOS 5.1.1, and as the version number implies, this isn’t another major release on the scale of 5.1. Looking at the list of changes, it mostly contains a ton of upgraded versions of various programs and tools included in ArcaOS. After some digging into some of those upgraded versions, I think I can safely say we’re looking at a ton of small bugfixes, but there are also a few other things that stand out to me as welcome changes.

For instance, the changelog mentions various improvements to the installer and related tools, such as an improved method of determining the right screen resolution and font scaling during the installation. Considering I had to deal with some issues there – I think the installer UI elements were grossly oversized – this is a welcome fix. There are also “refreshed” Firefox and Thunderbird builds, although I don’t know if that means an update to the latest ESR releases, or just a rebuild of what was already shipping with ArcaOS 5.1.

I never found the time around the 5.1 release to do a proper review – I was knee-deep in baby and toddler care overload at the time – but if Arca Noae is willing to provide me with a 5.1.1 copy, I should be able to actually review it now that I’m only ankle-deep in baby and toddler care overload.

One of the reactions to my discussion of why Windows 95 setup used three operating systems (and oh there were many) was my explanation that an MS-DOS based setup program would be text-mode. But c’mon, MS-DOS could do graphics! Are you just a bunch of morons?

Yes, MS-DOS could do graphics, in the sense that it didn’t actively prevent you from doing graphics. You were still responsible for everything yourself, though. There were no graphics primitives aside from a BIOS call to plot a single pixel. Everything else was on you, and you didn’t want to use the BIOS call to plot pixels anyway because it was slow. If you wanted any modicum of performance, you had to access the frame buffer directly.

↫ Raymond Chen

And with everything the Windows 95 setup program needs that you’d have to create, you’d end up just… Developing a custom operating system in the first place. Since Microsoft already had Windows 3.x lying around, why not reuse parts of that to aid in the Windows 95 installation process? Honestly, all of it makes perfect sense, and I really don’t understand why anyone would seriously advocate for building a separate, entirely custom operating system just to install Windows 95 when Windows 3.x was right there.

Of course, these days things are a little different, but Windows still loads a different operating system during its installation. It’s called the Windows Preinstallation Environment, but it’s no longer based on Windows 3.x, obviously, and instead is a cut-down version of the Windows version you’re actually installing. The latest version of Windows PE is 10.0.26100.1, and it’s built from Windows 11 24H2. Windows PE also powers the Windows Recovery Environment, the menu you can boot into to perform various analyses, maintenance, and repair of your Windows installation.

Since Microsoft does not want Windows PE to be used a general purpose operating system, it comes with a few interesting limitations you can’t really circumvent. It has a non-configurable 72-hour time bomb, after which if will just shut off, and since PE runs entirely in memory, no changes are saved – unless you make any changes during the creation of the PE image. It also makes use of FAT32, so there’s a whole host of limitations there, and there’s a few other things Microsoft disabled. Since you an add drivers to a PE image, though, I wonder if you could sneak in a file system driver and circumvent FAT32’s limitations that way?

JotaleaOS is an open source, minimalistic, experimental operating system made by Jotalea, designed for extreme low-resource environments. It does not support external programs or games, as it lacks a standard application execution environment. The system is entirely self-contained, running only its built-in commands.

↫ JotaleaOS website

Exactly what is says on the tin: a tiny operating system created entirely as a learning experience. That’s it.

Speaking of KDE, Plasma 6.3 has been released. It brings with it a ton of improvements aimed at digital artists, such as much improved management and configuration of drawing tablets. You can now map an area of the tablet’s surface to a part of the screen, change the functions of stylus buttons, customise the pressure curve and range of a stylus, and much more. The entire settings panel for drawing tablets has also been redesigned to make it easier to find what you’re looking for.

Plasma 6.3 also completely overhauls KWin’s fraction scaling. Fractional scaling in KWin will not try to snap everything to your display’s pixel grid, to reduce blurriness and make everything look sharper. KWin’s zoom effect also makes use of these improvements, making for a pixel-perfect zoom feature with a pixel grid overlay, which is great for artists and designers. This will be a very welcome improvement for people using e.g. 125% or 150% scaling on their displays.

Hardware monitoring is much improved too, with System Monitor showing more information while using fewer resources, and KDE users on FreeBSD can now see GPU statistics too. There’s also a ton of small additions that are still quite welcome, like opening the menu editor instead of a properties dialog when clicking on Edit Application in a launcher menu’s context menu, the ability to clone panels, an option to turn of symbolic icons in Kickoff, a “Show Target” option in the context menu of symbolic links, and a lot more.

KDE Plasma 6.3 will find its way to your distribution of choice soon enough.

One of the major issues with KDE’s styling system is the fact that over the year, it has accumulated four ways of styling applications – which makes themeing and changing aspects of the default theme far more cumbersome than it should be. In fact, with the current version of KDE, it’s effectively impossible to consistently theme the entire KDE desktop, as several parts of it, like Kirigami applications, only inherit parts of the theme you’re applying. It’s a bit of a mess, and KDE is well aware of this.

This problem is not new; we already identified it several years ago. Unfortunately, it also is not easy to solve. Some of the reasons it got to this state are simply inertia. Some things like Plasma’s SVG styling were developed as a way to improve styling in an era where a lot of the technologies we currently use did not exist yet. The solutions developed in those days have now existed for a pretty long time so we cannot suddenly drop them. Other reasons are more technical in nature, such as completely different rendering stacks.

↫ Arjen Hiemstra

These different rendering stacks form the core of the problem, as they can’t use the same rendering code for everything. Currently, KDE tries to address the problem through a compatibility layer to tie everything together, but it’s not perfect, it has to be maintained, and it means they’re not utilising their rendering stacks to their fullest potential. The solution KDE is working on is called Union.

However, there is another option, which is to take a step back and realise that we actually may not even want to share the rendering code, given that they are quite different. Instead, we need a description of what the element should look like, and then we can have specific rendering code that implements how to render that in the best way for a certain technology stack.

↫ Arjen Hiemstra

Basically, an input layer will interpret file formats with style descrpitions, while an intermediate layer consists of a library that converts that interpretation into a more abstract description of what needs to be rendered. The final output layer then uses the data from the intermediate layer to tell the rendering stacks what to do. By standardising on the input format, say CSS, it’ll be much easier to impement themes or make changes.

This effort is still far from done, but they’re making good progress. It ties into the Plasma Next initiative, which is, as the name implies, an effort to make changes to Plasma’s default look and feel.

The Redox project has posted its usual monthly update, and this time, we’ve got a major milestone creeping within reach.

Thanks to Anhad Singh for his amazing work on Dynamic Linking! In this southern-hemisphere-Redox-Summer-of-Code project, Anhad has implemented dynamic linking as the default build method for many recipes, and all new porting can use dynamic linking with relatively little effort.

This is a huge step forward for Redox, because relibc can now become a stable ABI. And having a stable ABI is one of the prerequisites for Redox to reach “Release 1.0”.

↫ Ribbon and Ron Williams

A major step forward for Redox, and one of those things not everyone might think about when they consider the state of an operating system. This wasn’t all of the news this month, though, as Redox also received a port of the LOVE game engine, which powers quite a few successful indie games, like the recent hit Balatro. Thanks to this port, you can now play Balatro on Redox, which is pretty cool – and highlights just how far Redox has already come. On top of these major two headlines, there’s a ton of improvements all over the operating system, mostly at the lower levels.

During a weekend of tidying up – you know, the kind of chore where you’re knee-deep in old boxes before you realize it. Digging through the dusty cables and old, outdated user manuals, I found something that I had long forgotten: an old Plan 9 distribution. Judging by the faded ink and slight warping of the disk sleeve, it had to be from around 1994 or 1995.

I couldn’t help but wonder: why had I kept this? Back then, I was curious about Plan 9. It was a forward-thinking OS that never quite reached full potential. Holding that disk, however, it felt more like a time capsule, a real reminder of computing’s advancements and adventurous spirit in the 1990s.

↫ Bill Dyer at It’s FOSS

As the article notes, 9front is the way to go if you want to try Plan 9 today. Plan 9/9front appeals to a very specific type of person, but when you dive into the excellent – and incredibly entertaining – documentation, it really seems quite easy to grasp and get started with. There’s definitely things you’ll need to unlearn and some compromises you’ll need to make, but I think you’ll be able to get a lot more work done than you might think.

Also, if you start adding software to 9front, you get to use the best GitHub alternative of all time: shithub. That alone makes it worth it to try 9front.

We had a bit of a bug caused by changes we made to make quotes look better, but we’ve fixed it now, so we’re back on track (you may need to do a force-reload in your browser). Sorry for the disruption – and if you want to stay up-to-date on such issues next time it (inevitably) happens, you should follow the OSNews Fedi account (or just bookmark it without following it, if you’re not interested in social media). Anyway, back to the news!

Fresh OS installs are bliss. But the joy fades quickly as installing and uninstalling programs leave behind a trail of digital debris. Even configuration management and declarative systems like NixOS miss crucial bits, like the contents of /var/lib or stray dotfiles. This debris isn’t just unsightly. It can be load-bearing, crucial to the functioning of your system, but outside of your control, and not preserved on rebuilds. Full system backups merely preserve this chaos. I wanted a clean slate, automatically, every boot.

“Erase your darlings” inspired an idea in the NixOS community: allowlisting files and directories that persist across reboots. Anything not on the list gets wiped. The simplest implementation involves mounting / as a tmpfs (i.e. in RAM), and then bind-mounting or symlinking the allowlisted items to a disk-backed filesystem.

↫ Tuxes.uk

I dabbled in NixOS over the past week or so, and while I find it intriguing and can definitely see a use for it, I also found it rather needlessly cumbersome and over-engineered for something as simple as a desktop system. I felt like I was taking a whole bunch of additional steps to do basic things, without needing any of the benefits Nix and NixOS bring. This doesn’t mean Nix and NixOS are bad – just that for me, personally, it doesn’t fill any need I have.

Taking the Nix concept as far as starting with a completely fresh installation on every boot sounds absolutely insane to me. Of course, it’s not entirely fresh on every reboot, as several applications and important configuration elements do survive the reboot, but it’s still quite drastic compared to what everyone else is doing. Unsurprisingly, there are a few issues; it’s hard to know what really needs and doesn’t need saving, there might be some unexpected issues because software doesn’t expect to be wiped, and so on.

Overall though, it seems to work susprisingly well, and for a specific type of person, this is definitely bliss.

Cassette is a GUI application framework written in C11, with a UI inspired by the cassette-futurism aesthetic. Built for modern POSIX systems, it’s made out of three libraries: CGUI, CCFG and COBJ. Cassette is free and open-source software, licensed under the LGPL-3.0.

↫ Cassette GitHub page

Upon first reading this description, you might wonder what a “cassette-futurism aesthetic” really is, but once you take a look at the screenshots of what Cassette can do, you immediately understand what it means. It’s still in the alpha stage and there’s lot still to do, but what it has now is already something quite unique I don’t think the major toolkits really cater to or can even pull off.

There’s an example application that’s focused on showing some system stats, and that’s exactly the kind of stuff this seems a great fit for: good-looking, small widget-like applications showing glanceable information.

Late last year, the MaXX Interactive Desktop, the Linux (and BSD) version of the IRIX desktop, sprung back to life with a new release and a detailed roadmap. Thanks to a unique licensing agreement with SGI, MaXX’ developer, Eric Masson, has been able to bring a lot of the SGI user experience over to Linux and BSD, and as promised, we have a new release: the final version of MaXX Interactive Desktop 2.2.0. It’s codenamed Octane, and anyone who knows their SGI history will chuckle at this and other codenames MaXX uses.

Like last year’s alpha release, 2.2.0 brings an Exposé-like overview features, initial freedesktop.org integration, tons of performance improvements and bug fixes, desktop notifications, and much more. For the next release, 2.3.0 they’re planning a new file manager, support for .desktop files, a ton of new preference panes, a quick search feature, and a whole bunch of lower-level stuff. With how serious the renewed development effort seems, I hope that some day, the project will consider building MaXX out to a full Linux distribution, to gain more control over the experience and ensure normal users don’t have to perform a manual installation.

Upstart was an event-based replacement for the traditional System V init (sysvinit) system on Ubuntu, introduced to bring a modern and more flexible way of handling system startup and service management. It emerged in the mid-2000s, during a period when sysvinit’s age and limitations were becoming more apparent, especially with regard to concurrency and dependency handling. Upstart was developed by Canonical, the company behind Ubuntu, with the aim of reducing boot times, improving reliability, and making the system initialization process more dynamic. Though at first it seemed likely to become a standard across many distributions, Upstart eventually lost mindshare to systemd and ceased to be Ubuntu’s default init system.

↫ André Machado

I think it’s safe to say systemd won the competition to become the definitive successor to sysvinit on Linux, but Canonical’s Upstart made a valiant effort, too. However, with a troublesome license, it was doomed from the start, and it didn’t help that virtually every other major distribution eventually adopted systemd. These days, systemd is the Linux init system, and I personally quite like it (and the crowd turns violent). I find it easy to use and it’s never given me any issues, but I’m not a system administrator dealing with complex setups, so my experience with systemd is probably rather limited. It just does its thing in the background on my machines.

None of this means there aren’t any other init systems still being actively developed. There’s GNU Shepard we talked about recently, runit, OpenRC, and many more. If you don’t like systemd, there’s enough alternatives out there.