OSnews

You all donated en masse to have me use Windows 11 for a month, and so I did. What was it like for a long-time Linux user to go back and experience Windows as it exists now? Is it really as bad as we've collectively made it out to be? Did my month with Windows 11 consist of nothing but pain and misery, or are there good things to say, too? Or, was it an unexpected pleasant surprise? And ultimately, did I stay with Windows 11, or move back to the Linux world? Donate through Ko-Fi Donate through SEPA transfer* Buy merch from our store Why a fundraiser? *Name: Thom Holwerda - IBAN: SE08 8000 0820 1684 4657 8414 - BIC: SWEDSESS This year, I'm celebrating the milestone of having posted 20000 stories on OSNews during my 21 years as managing editor of OSNews. This is my full-time job, and since nobody is going to give me any bonuses, stock options, or golden pens, we're running a big fundraiser to keep OSNews going. To add some spice to the whole thing, I added some incentives, with the first being using Windows 11 for a month. We're slowly but steadily approaching the next incentive, too, which is a proper video tour of my office, (unique) computers, and massive devices collection. There's a similar incentive to this Windows 11 one, but for macOS. Yikes. The rules for the Windows 11 incentive are simple: use stock Windows 11 for a month for my computing tasks (with the exception of gaming - converting my Linux gaming PC to Windows just to play the same games seemed silly). I wasn't allowed to use any debloating tools, but as an EU citizen, I do have the ability to remove a ton of Windows stuff thanks to the success of the Digital Markets Act. I also tried to stick to Microsoft's own applications as much as possible, for that true ecosystem experience", and wasn't allowed to hack my way into a normal local user account. I was all-in. So what was it like? Setting it all up The installation process posed a number of challenges and issues. First and foremost, the Windows 11 installation process is incredibly barebones, and basically assumes no other operating system exists in the world. It has no clue anything other than Windows' filesystems exist, making it dangerously easy to accidentally damage or outright delete any other operating systems you might have installed. My laptop happens to have two M.2 SSDs in, so I could safely dedicate one of them to Windows 11 without interfering with the other SSD with Fedora installed on it, but if you're experimenting with Windows 11 on your Linux machine with just one drive, you might want to reconsider. I also had to perform the first portion of the installation process - the WinPE section - with just my keyboard, since apparently, my trackpad was not supported and did not work at all. Once the system went through its first of what would be many reboots to come and loaded into the phase of the installation where you're actually already running Windows 11, my trackpad came to life, but without any gestures support - so no scrolling. Not a gamebreaker or anything, but definitely annoying. A bigger issue was that the Wi-Fi 7 Intel BE200 chip in my laptop was not supported out of the box by Windows 11. This meant that I had to install these drivers during the installation process, which involves going to the Intel website and finding the correct drivers to use. To make this process more obtuse and less intuitive, you can't use the normal driver installer; you have to specifically opt for the Intel(R) PROSet/Wireless Software and Wi-Fi Drivers for IT Administrators, download the ZIP, unpack it on a different computer, put the unpacked drivers on a USB stick, and point the Windows 11 installer to this USB stick. Mind you, the BE200 chip was launched almost three years ago, and there's no excuse for Windows 11 not supporting this chip out of the box - like Linux does. The remainder of the installation process involved dodging a lot of tracking and telemetry prompts, reboots, a lot of waiting, setting up the dreaded online account, waiting some more, and then finally ending up at the desktop. I then set out to enjoy my EU privileges by removing whatever applications I didn't need and turning off features I didn't want, as well as making sure all the drivers were up to date. This mostly involved installing the Intel Driver & Support Assistant and the Intel graphics drivers. Curiously, this is where I hit a returning issue: after installing the Intel GPU drivers for the first time, as well as after every subsequent update, the screen would go black and stay that way, forcing a reboot. Windows' graphics stack is supposed to be able to gracefully handle driver updates, but clearly, some bug or problem was preventing the updated Intel driver from being reinitialised. Once those initial setup tasks were behind me, I experienced two more problems. First, sleep/wake was entirely broken and simply did not work. It turns out Windows 11 really doesn't like S3 sleep, and I had to specifically go into my laptop's Dasharo Coreboot firmware to switch to S0ix get sleep/wake to work on Windows 11. Windows defaults to something it calls Modern Standby", which requires the S0ix state to be enabled. You can also disable Modern Standby which would presumably make sleep/wake work with S3 (?), but this is a whole ordeal and clearly not something Microsoft wants you to do. Of course, the correct way of handling this would be for Windows 11 to adapt its sleep/wake settings to what the firmware reports, but alas. Another problem were the laptop's cooling fans seemingly leading lives of their own, spinning up loudly at entirely random times, irrespective of use. It was so bad and loud

With July being Disability Pride Month, GNOME's Sophie Herold published a blog post taking stock of where GNOME stands on this front, progress that's been made, as well as areas where the project comes short. One particular paragraph from her introduction really hits the nail on the head about accessibility discussions in tech circles: The reality of tech communities is that they are often ableist and elitist. Probably more so than the average population. If a user or contributor struggles with a tool, blame is shifted to a skill issue," if an interface is simplified to make it accessible to more people, it's dumbed down". Assistive technologies are often developed by abled people, without involving and paying disabled people. This also leads to an attitude where contributors expect gratefulness from disabled people for providing them with the most basic needs. All these issues are also not absent from the GNOME community. Sophie Herold Even as someone who isn't disabled and doesn't use any tools classically shelved under the accessibility" moniker, I encounter the attitudes she mentions in the quoted paragraph basically every day. While we can have normal, productive discussions and differences of opinion about accessibility - for instance, I strongly believe robust theming support is absolutely crucial to accessibility, while the wider GNOME community does not - the dismissive attitudes towards people with accessibility needs in the software world is shameful. Even if you don't have accessibility needs today, you will definitely be needing them at some point in your life. If accessibility isn't one of the first words you jot down on your mood board or whatever when you start a new software project, you've already done millions of people a massive disservice. Get educated, learn what you can about accessibility, listen to people with accessibility needs, and make your software better for everyone. You'll thank yourself one day.

Linux Mint's Cinnamon is one of the last desktops to still not support Wayland, and is relegated to only being compatible with legacy X11 environments. With the next release of Cinnamon, however, this is finally going to change. We worked really hard on Wayland and we got to the point where it feels solid and the experience is almost on par with X11. Wayland support will no longer be considered experimental". In the next version of Cinnamon, both X11 and Wayland will be fully supported. Clement Lefebvre on the Linux Mint blog The next release of Cinnamon, version 6.8, will be part of the next release of Linux Mint, scheduled for Christmas of this year.

About a month ago, Flathub announced a ban on slopcoded applications. Evangelos GeopJr" Paterakis, developer of a number of popular Linux applications and ton of other things, did some research into just how many applications tagged with AI slop", a tag Flathub reviewers used to keep track of slopcoded applications submitted to Flathub, actually survived the test of time. The results are exactly what you'd expect. Of the 120 unique repos, 32 were maintained and 88 were abandoned. No seriously, a big portion of them was completely deleted, nowhere to be found, others stopped 6 months ago, right after submitting to Flathub. Evangelos GeopJr" Paterakis That's absolutely soul-crushing. Why should Flathub's reviewers spend their precious, limited time talking to lazy slopcoders' AI" agents to get their slopcoded applications into Flathub, when 70% of these applications are abandoned or outright deleted from existence within mere months of being submitted? Minimal effort for the slopcoders, maximum effort for the reviewers. Just dump a bunch of shitty code over the fence, let a chatbot handle the interactions with the reviewers, and pretend you made a valuable contribution. This is the contradiction slopcode enthusiasts really don't want to talk about. If these AI" tools are so great, where is all the amazing new software? Where's the massive gains in software quality? Isn't the story that AI" tools do the menial work, giving programmers more time to focus on improving their software? Reality does not seem to match the story we're being sold. Despite these slopcode tools being out and available for years now, there's no influx of great applications and other software, there's no rise in software quality, nothing. What we mostly seem to be getting are slopcoded projects nobody, not even their creators" care about, so they just get abandoned and deleted as quickly as they were dredged up from the bottom of the programming barrel. These aren't applications created because someone wanted them to exist; these are applications created because some mid programmer got high on their AI" supply and fancied themselves better at programming than they really are - only to realise once the comedown hits they've got crappy, barely working, entirely unmaintainable gibberish vaguely looking like code nobody can make head nor tails of. And then they abandon the project, ready for the next high - leaving everyone else to clean up their mess. What a miserable workflow.

Only a few days ago we had Linux on the Mega Drive, and someone took that as a challenge, so now we have Linux on the Atari Jaguar. The Jaguar has a very different architecture than the Mega Drive, but does happen to use a processor from the same 68000-family. Interestingly enough, to this day, Linux has architecture code for the 68000-family of processors. 68040, 68030, 68010... and even the original base 68000 processor. All neatly structured under arch/m68k/. Joel Bueno And, well, that means Linux can indeed be made to work on the Jaguar, with some hacking and magic, of course.

Wherever in the world you go, the smartphone landscape is dominated by Android and iOS, and while this has always been problematic, recent events have made the dependency on two American tech giants for what is probably our most personal computing device even more problematic than it already was. We use our smartphones to keep our secrets, do our banking, interact with our governments, share our deepest thoughts with our friends and family, and a whole lot more. Having this invaluable tool the vast majority of us depend on tied entirely to Google and Apple is not just bad for the market, it's also a downright threat to the national security of anyone not living in the US. Here in Europe, there's been an awakening lately, with governments, companies, and people alike finally realising that having our entire digital infrastructure controlled by foreign, adversarial interests is a terrible idea. Sadly, breaking free from our Android and iOS chains is not so easy. The most ideal solution would be a truly open source alternative smartphone operating system, but that's a hard sell for 99.9% of smartphone users who need the applications required to do their finances, talk to their friends, or interact with their governments. The cold and harsh truth is that with very few exceptions, these applications simply do not (yet) exist for smartphone operating systems that aren't Android or iOS. The only viable alternative at this point in time is to take whatever's left of the Android Open Source Project, remove anything that ties it to Google and its services, fill in the gaps with alternative services and applications, and sell it as a Google-free or de-Googled Android platform. There's several projects in this space, and with Europe drunkenly stumbling out of the technological hole it dug itself into, it's no surprise that two of the more popular alternatives to Apple or Google-controlled smartphones come from Europe (and from the same country, no less). Today, we're taking a look at one of these: iodeOS. Iode is a company based in Toulouse, France, which focuses on offering a Google-free Android called iodeOS, either preinstalled on phones you can buy, or as a ROM you can install yourself on supported devices. As a company, iode makes its money through selling devices with iodeOS preinstalled, through an optional premium subscription (that I didn't take a look at), and through donations, and all of their code is published as open source on their Gitlab instance hosted in France. Iode loaned me a Fairphone 6 with iodeOS preinstalled, one of he many smartphones and tablets they sell through their online store for review. This isn't going to be an Android review; you already know what Android is like, and there's no need for me to rehash any of that. Instead, I want to focus on the things that make using de-Googled Android different from using Google Android. Don't be afraid of microG There are various ways to go about making a de-Googled Android variant, and iodeOS chose the LineageOS route, with microG installed on top. For those unaware, microG is a project which aims to replace the various proprietary parts of Google Play Services, required by many Android applications, with open source reimplementations. While it doesn't offer 100% compatibility, it works exceptionally well, and you'll be hard-pressed to find applications just don't work at all with microG. IodeOS updates its microG installation through a dedicated F-Droid repository that's obviously enabled by default, so you don't have to do anything yourself. Using microG instead of Google Play Services doesn't mean you have to rely solely on whatever's available in F-Droid, since there are a variety of alternative Play Store frontends available. IodeOS ships with the Aurora Store, which is an open-source frontend to the Play Store that can be used with or without a Google account. If you use it with your Google account, you'll gain access to whatever applications you already own, including paid ones, but you won't be able to buy applications inside Aurora. You can, however, buy an application on the Play Store website, after which it will show up in Aurora as well, assuming you're logged in with the same account. Aurora also comes with something something called FakeStore, which is sadly an important part of the puzzle; it's a stub application that has the same package name as the real Play Store. Some applications check whether the Play Store is available before working properly, so this is sadly needed to ensure maximum compatibility. The only issue I sometimes ran into with Aurora is that it would load up its listings, but then any application I tapped on said it was unavailable. When this happened, reloading the Aurora application always fixed the issue. Annoying, but not gamebreaking. A few things did not work for me when using microG on iodeOS, and they're exactly the things you'd expect not to work. If you have a WearOS device, you're out of luck; WearOS devices simply do not work when using microG, but there is a bounty to add support for it. If you want to use a smartwatch with iodeOS, there are various options available, such as Garmin devices, which is what I used during my testing and it worked flawlessly. Another feature from regular" Android that simply won't work is RCS. There's only one RCS client available on Android, Google Messages, and as you can imagine, Google is in no rush to allow devices without Google Play Services to register for and use RCS messaging. Tying to register with Google Messages will fail, and there are no other RCS clients available (save for a few China and India-specific clients). There's a microG bounty for this, too, but no luck so far. Of course, there are countless messaging platforms that work just fine on iodeOS - regular SMS, WhatsApp, Facebook Messenger, Signal, and so on - and especially if you're European, it's unlikely RCS support matters to you at all. I just don't

Colour me positively surprised, as I had no idea Alpha emulation had progressed this much. As you might know, I'm involved a bit in the OpenVMS community and the Alpha emulation side via AXPBox. AXPBox (github) is a fork of the es40 alpha emulator by Camiel Vanderhoeven (who is now Chief Architect at VSI, the company that makes OpenVMS, for x86 nowdays). There have been many forks of es40 in the past and recently a new one has popped up with some great new features. Like speedups via a JIT compiler, S3 graphics port from MAME and ARC support, resulting in the ability to run Windows 2000 for the DEC Alpha. Remy van Elst Not only can you run the unreleased Alpha version of Windows 2000 on this forked emulator, it's also capable of running OpenVMS and Tru64 UNIX. In fact, both OpenVMS and Tru64 can run their full X11 CDE desktops on the emulator as well, which is incredibly cool and a huge milestone. As the name of the original emulator implies, it's emulating an AlphaServer Es40 from the turn of the century, which should be fast enough for enthusiast use. The last AlphaStation ever made, the ES47, is still very high on my list of computers I desperately want but will never have - they are incredibly rare, and whenever they do come up for sale, incredibly expensive. If you have one, consider yourself lucky, and please, write about it! Tell the world!

LineageOS, the de-Googled Android ROM that serves as the backbone for pretty much the entire custom Android ROM community, has published an article about what the Android developer verification changes mean for them. I really like the factual tone of their article, especially this part: Critics such as F-Droid, EFF, and Keep Android Open" point out that this also happens to route every install path through Google-controlled infrastructure, hands Google a kill switch over any app or developer worldwide, and arrives shortly after Google's antitrust lawsuits. Both things can be true at once: real fraud is a problem and the restriction of developers is a convenient side effect of solving it this way - and we're not in a position to pretend we know Google's internal reasoning. We're just telling you what they've said and what it changes; you can weigh the why" yourself. Nolen Johnson on the LineageOS website For LineageOS, these new verification measures don't really mean much, as they don't affect the project's work or software. The developer verification infrastructure is a separate application that is part of Google Mobile Services, and LineageOS does not ship GMS nor does it ever intend to. As such, they don't have to do anything, as this won't be an issue unless LineageOS users choose to install a GApps package that happens to include the developer verification infrastructure. If Google were to move the developer verification infrastructure into Play Services in the future, LineageOS makes it clear they'll disable it globally, as they have done with a number of other annoying Play Services-provided over-the-air update implementations. There really isn't much more they can do; the rest is up to users and projects that use LineageOS as their base.

The Nintendo Entertainment System. Is it the platonic ideal of an 8-bit video game system? Well, only because it's so prominent and successful- it's actually kind of an oddball in its expandability and design. But there's something else about it. The picture is a bit... wobbly. Well, over composite video anyway. Let's dig in and learn a little big more about the nitty-gritty of composite video. Nicole Branagan As usual, the information density in this article by Branagan is kind of remarkable, especially when you consider it never overwhelms you. Such a great read.

A fairly big moment for the ReactOS project: it has just received its very first system call from NT6. The system call that has been added is NtGetCurrentProcessorNumberEx, which is used for returning the processor number of the logical processor that a caller is running on. It's unclear how long it will take ReactOS to become compatible with Windows Vista software, but it took Microsoft around half a decade to develop Vista after the release of XP and marked a major upgrade, even if it didn't land well with users at the time. Paul Hill at Neowin It's a milestone for sure, but not one that's going to make a huge difference for ReactOS at this moment in time. Still, it's a sign of things to come, even if the very nature of the ReactOS project means that whatever things are coming tend to take a while to arrive.

For how often people invoke it, the concept of hell" in Christianity is remarkably vague and nebulous, as both the Old and New Testament barely go into detail about the concept. As such, I'm glad Microsoft has now given us a clear vision of hell and what, exactly, it looks like, ending centuries of denominational disagreements. Microsoft is currently selling the idea of Windows and Copilot as two separate things: an OS and an assistant riding along on top of it. However, a leaked video shows Project Aion, an internal prototype where Copilot doesn't just sit inside Windows, it becomes Windows, swallowing the Start menu, the taskbar, and three decades of desktop conventions in the process. The footage is reportedly two years old, so Aion is most likely dead by now. But it's the clearest look yet at how far Microsoft was willing to take its agentic AI ambitions. Alfonso Maruccia at Techspot Everything about this is dreadful. Obviously replacing the entire shell with AI" nonsense is the main crime against usability here, but on top of that, this new shell is all just websites, all the way down, so everything is slow and stuttery. Since this runs on something called Win3", which appears to be a very minimal, stripped-down version of Windows intended to only run the Edge browser engine, you can't run Win32 applications. If you do try to run a Win32 application, it will load the application in a remote virtual machine running in the cloud, which I;m sure does wonder for performance, responsiveness, and latency. We can all thank the lord this project is two years old and most likely cancelled by now, but we have no way of knowing if Microsoft is still intending for this to be the future direction of Windows. Since people don't want to use AI" of their own volition, it only makes sense in the technology industry's sick, twisted mind to force people into using AI" with efforts like this. Consent has never been Silicon Valley's strength, after all. At the time of writing, Microsoft is 225 billion dollars in the red on AI", so I wouldn't be surprised if attempts to replace the regular Explorer shell with something AI"-based is still very much on the table in Redmond.

NetBSD is the only BSD without a Vulkan stack (Mesa and Lavapipe), but that's about to change. The effort to bring Vulkan to NetBSD is now in beta, with prebuilt binaries coming soon. Mesa configures, compiles, links, installs, and registers the Lavapipe software Vulkan driver on NetBSD 10.1 amd64, against LLVM 19.1.7. The driver (libvulkan_lvp.so, ~17 MB) installs into /usr/pkg/lib, and its ICD manifest (advertising Vulkan API 1.4) installs into /usr/pkg/share/vulkan/icd.d/, so a Vulkan loader on the system can discover it. ldd resolves every dependency cleanly. The entire process - environment setup, dependency builds, the Mesa build, and installation - is automated end to end and reproducible on a fresh install. vulkan-netbsd GitHub page It's important to note that the next step in the process is to port the Vulkan loader, which is required to actually run Vulkan applications. This entire effort is still ongoing and seems to be handled mostly by Dean Howell alone, so expect breakage and incomplete documentation as development progresses. Still, this is a hugely important effort, and seeing it this far along is great news.

EveryMac turned 30. On July 2, 1996, EveryMac.com launched. Thirty years is a long time - and a great deal has changed since then - but what has not changed is that EveryMac.com has been there to provide you with detailed info on every Mac from the original 128k to the current line. Thank you very much for your support through the years. EveryMac news item I thought OSNews was pretty unique with its founding in 1997, so it's great to see another enthusiast's website as old as ours. Amazing company to be in, too - EveryMac is an indispensable, tirelessly maintained, and stupidly accurate resource that I use countless times each year. Here's to another 30 years.

The clock is ticking for Android as a (somewhat) open platform. If you are running Android 8 or higher, a virus has been installed on your device and is silently awaiting remote activation. Over the past few months, devices around the world have been infected with this novel strain, with as many as 4 billion Android handsets and tablets estimated to have already been contaminated, meaning that around half of all humanity may be at risk from this threat. Disguising itself as the innocuously-titled Android Developer Verifier" (ADV) process, this trojan horse runs surreptitiously in the background as a system service with full root privileges, quietly awaiting an activation signal. The service cannot be blocked, disabled, or removed. Unlike a commonplace bit of malware, this extraordinary strain won't be detected and neutralized by Play Protect (the malware scanning and remediation service that is installed on all Android Certified devices). In fact, Play Protect is itself the vector through which this virus is transmitted and installed. That is because it is Google themselves who is propagating ADV. And once activated, this malevolent process has exactly one goal: to block you from running software by developers who haven't been approved centrally by Google. The F-Droid news website If nobody steps up, if no regulator takes on Google in this matter, we could very well be looking at the end of F-Droid and similar open source application repositories on Android. I use F-Droid, and in fact, one of the most important and most-used application on my Pixel 10 Pro comes from F-Droid: Fennec. This Firefox fork is not available through any Google-sanctioned means, and I could just wake up one day and have the browser on what is supposed to be my phone stop working. Age verification, tying crucial services to iOS and Google Android, killing the ability to install your own software on your phone, purposefully making people hopelessly addicted to and dependent on AI", and so much more - we're facing a multi-pronged attack designed to beat us into submission and give up on the idea of Free computing. I have to admit I've lost all hope we'll be able to win this battle, as the combined interests of technology megacorporations and our own governments are just too powerful to fight. I feel like we're living in the computing end times.

What if you need to do very low-level testing involving the very guts of Windows NT, but don't need most of the userland that sits on top? In fact, what if that userland only slows you down and complicates the work you're trying to do? The solution is Windows PE (Windows Preinstallation Environment). It is an official, stripped-down environment distributed with every Windows ISO image. It runs entirely in RAM, requires as little as 512 MB of memory, and lacks support for DirectX, the PowerShell subsystem, or the standard graphical shell (Explorer). Booting by default with NT AUTHORITY\\SYSTEM privileges makes it an ideal test harness for both of these tasks. The following analysis focuses on the low-level mechanisms of WinPE, as well as BCD and QEMU modifications that allow transforming this system into an ultra-fast, idempotent testing environment. Piotr Bednarski Now, the kind of work Bednarski does isn't the most common of tasks, but I've often wondered just how far you can get by bolting on whatever WinPE will allow you to. There were various unofficial third-party tools that built Windows live CDs based on WinPE, but I think most of those have died out by now. If you look hard enough, you can also find some other utilities people made for WinPE, including even some rudimentary web browsers. Regarding web browsers, modern efforts seem to run into issues. WinPE is not really meant for any advanced functionality, but I really do wonder how capable you can make it without turning it into regular Windows.

M/PC is a concatenative operating system for Varvara, inspired by Openfirmware, designed to manage files on system without a file browser. It uses the postfix notation, meaning that the function success their operands. M/PC website I'm not going to pretend to really understand what any of this means.

Recently, there has been a surge in slopcoded new/hobby operating systems". Such slopcoded projects - which, due to the nature of AI" tools, effectively consist of stolen code - will not be featured on OSNews and submitting them is fruitless. Other websites may choose to employ lower standards, as is their prerogative, but OSNews will not. I obviously cannot guarantee nothing will ever slip through the cracks, but I will take utmost care to ensure OSNews remains free of these so-called sloperating systems". Plagiarism, license-washing, and code theft have no place in the world of enthusiast and hobby operating systems.

European governments are rolling out digital identity wallets, which are to be used by citizens to access services, and to verify their age online. As reported by Follow the Money and Android Authority, there is a serious problem with this: these wallets rely on safety services of Google and Apple. These are known as Google Play Integrity API, and Apple's Managed Device Attestation. Such safety services (known as remote attestation") are used to ensure that wallet apps run on hardware that is not tampered with. In this article we explain why the EU-wallet case is part of a bigger problem: by embedding these safety services in public infrastructure, Europe risks making society dependent on private companies while serving their corporate interests. Danny Lammerhirt Setting aside the age verification nonsense, the fact that some European government are tying their identification services to iOS and Google Android is absolutely bonkers, especially in this day and age. There's endless talk about reducing European dependence on the American tech giants who seem all too eager to do roll over when the Trump regime so much as glances in their general direction, and yet, they seem to want to effectively force us citizens to use American tech products. Essential online tools, like banking, government services, communication services, digital driver's licenses, and more, should not require the use of iOS or Google Android.

There's a lot you can say about macOS, but one thing Apple used to be incredibly good at were making beautifully crafted, detailed icons. As with almost every other aspect of macOS, this deteriorated sharply over the years, with the recent macOS releases with Liquid Glass being an absolute low point. Not only have they become bland and featureless, Apple also started forcing every icons to have the exact same rounded-rectangle shape, making them even harder to distinguish from one another. Rogue Amoeba, a company with a long history of developing applications with beautiful iconography, published a blog post pleading Apple to go back to proper icon design. With last year's release of MacOS 26 (Tahoe), Apple made a mess of app icons. In the first betas of MacOS 27 (Golden Gate), however, there are signs of a turnaround. We're urging Apple to continue making improvements, by restoring the ability for MacOS app icons to have distinct shapes. Paul Kafasis at the Rogue Amoeba blog I really hope Apple will turn its icon ship around.

If you have a Sega Mega Drive, you obviously want to run Linux on it. That's something you can do now. You do need to have an EverDrive, but don't worry, the port in question contains a custom fork of Qemu for those of us that don't. I don't know what else to say, other than I wonder why nobody did this sooner.

There's something poetic about the World Cup taking place in North America while Microsoft keeps scoring own goals like this. Microsoft updated its Surface buying guide to describe 8GB RAM as great for everyday use like browsing, streaming, schoolwork, and productivity apps." A companion FAQ adds that 16GB or more is what unlocks Copilot+ PC features. No acknowledgment that, for two years, Microsoft was the loudest voice telling everyone that 16GB was non-negotiable for a good Windows 11 experience. What makes this infuriating is that Microsoft is one of the biggest reasons why the RAM situation got so bad in the first place. Abhijith M B at Windows Latest This industry is a joke.

Astral is a hobby operating system written in C for 64bit architectures, with a collection of ported software like X.org, fvwm, the xbps package manager, and tons more. I think it's quite a neat system - the code's on GitHub - made even neater by the fact it can run not only Minecraft, but now also has a working port of Wine that can run a few games. A few months ago, I posted about Astral, a hobby OS I have been working on over the years, running Minecraft. Since then, others have gotten modern versions of Minecraft to run as well as Factorio (using a glibc compatible libc). However, while these games are made or packaged in a way that makes it easier to get them to run under a new OS, most games are not. A lot of games are closed source and compiled for Windows, which makes something like Wine a necessity for playing them. One of my favorite games, Cogmind, falls under that umbrella. It is a 32-bit Windows only roguelike, and it became my goal to run it under Astral. While there was already an existing Wine port, it was extremely incomplete, as not even notepad.exe worked properly. To run Cogmind, the Wine port had to be finished, which also meant adding the ability to run 32-bit code on an otherwise 64-bit-only OS. Blog post on the Astral website This process obviously is quite involved, but in the end, they managed to get it working. Quite impressive.

Imagine your favorite team just scored an incredible, last-second goal at the World Cup. So you log online to celebrate with other fans. But, using data it's already collected on you, the social media platform you like to post on wrongly guesses that you're under 16 so it forces you to go to a third-party verification app and provide images of your face or your government-issued ID. You don't really know much about the verification app, what country it's based out of, what happens with your information, and whether you're protected from hackers or data breaches. You're not happy about it, but you hand over a photo of your passport and hope it doesn't come back to haunt you. Now imagine that instead of posting about sports, you're criticizing a powerful politician, or talking about your experiences with abuse or addiction, or discussing embarrassing medical issues you're facing. Suddenly this papers, please" approach to the internet sounds even more invasive, right? Unfortunately, that's the direction we're all headed - even here in the United States - and we have good reason to be wary of the global rush to sacrifice user privacy on the altar of age verification. Sarah McLaughlin at Expression The insane push for age verification on the internet is the biggest threat to whatever's left of the free internet. I have two young children - 3 and 5, currently - and I'm diametrically opposed to any kind of creepy verification processes that they claim are designed to keep kids like mine safe". Not only is their safety not predicated on giving up their privacy, my children are also not my or anyone else's property; they have rights, and the right to privacy is one of them. Nobody mentioned in the Epstein files has been charged, by the way.

It's been quiet for a few days since I've been sick, but I'm feeling a bit better since today marks the official end of my one month of using Windows 11 that you people donated for. An article about my experience is definitely upcoming, including whether or not I'll actually stick with Windows 11 on my laptop or go back to Linux, but before we get there, let's talk about Microsoft once again capitulating to the reality that a lot of people really don't want to let go of Windows 10. In a surprising move, Microsoft has quietly confirmed that it's extending Windows 10 support untilOctober 12, 2027, which is one full year beyond the October 2026 cutoff that home users had been planning around. Abhijith M B at Windows Latest Hundreds of millions of people are still using Windows 10, and with the AI" techbros buying up all the RAM and other chips for their pachinko machines - making this whole thing a bit of an own goal for prime AI" booster Microsoft - buying new PCs that are actually compatible with Windows 11 isn't exactly a fun prospect for the vast majority of us normal folk dealing with the cost-of-living crisis. As such, Microsoft really doesn't have any other choice but to keep extending support for Windows 10. It ain't much, but I'll take any morsel of justice I can get. While everyone else has to pay for getting access to these Windows 10 updates, users in the European Union get them entirely for free thanks to the Digital Markets Act. This additional year, too, can be partially attributed to the DMA, as the very same consumer rights organisations who pressured Microsoft into giving EU users truly free access to the Extended Security Updates also put pressure on the company to offer these for more than just one year. Basic consumer protection legislation works.

Every little thing in a graphical user interface that we take for granted today, no matter how small, was thought up by someone, at some point. Case in point: the little red squiggly lines underneath misspelled words. In one form or another, these are everywhere now, and have just become a regular staple of every single text editing field we encounter every single day and don't stop to think about. Still, they were invented by someone, and we happen to know exactly who that was: Tony Krueger. In early versions of Word, the Spell Check feature was something that you explicitly invoked, and then you had to sit and wait while the program looked for all your potentially-misspelled words, and then showed them to you one at a time for a decision on what to do for each one. Word did introduce an Auto Spell Check feature to run spell check when the user was idle, so that when you hit the Spell Check button, the results were ready to go. However, the Auto Spell Check was still a blocking operation. As a result, a lot of users turned it off because it always seemed to decide Now would be a good time to spell-check the document" just as you wanted to do something, forcing you to wait for the spell check pass to complete before you could, say, save and exit. Tony made the spell checker much more unobtrusive so that it didn't interfere with your foreground work. And when it found a problem, instead of waiting for you to trigger a spell check, it immediately drew red squiggles under potentially-misspelled words (and later green squiggles under potential grammatical errors). Raymond Chen at The Old New Thing Tony Krueger passed away recently, after, among other things, having worked on an dizzying number of Microsoft Word releases. Imagine coming up with something that seems to basic and elementary to us now, and seeing it spread pretty much everywhere. I wonder what it must feel like to have invented something that seems so simple, most people don't even realise they use it every single day.

I've had my share of issues with network shares on any operating system, but since I mostly use KDE these days I found this deep dive into how, exactly, network shares work in KDE quite interesting. It turns out that while network shares in KDE's Dolphin mostly work, it does involves a few layers that sometimes don't interact well with each other, leading to really curious and annoying problems with mounted shares not appearing, permission issues, and so on. The biggest cause of problems is when using a non-KDE application in KDE that also happens to use a non-KDE save/open dialog. Such a non-KDE save/open dialog won't be able to see any network shared mounted by KDE, and sadly, quite a few applications you're likely to use on a KDE installation use non-KDE open/save dialogs, like Blender, GIMP, LibreOffice, OnlyOffice, Inkscape, Audacity, DaVinci Resolve, and more. That's one hell of a list of applications to offer inconsistent or outright broken access to network shares you've set up and mounted in KDE. Luckily, this issue seems to be getting a ton of attention soon. All is not lost. Happily, KDE just receivedan investment of over 1.2 million from the Sovereign Tech Fund, and it includes funding for improvements to KDE's network share handling! Nate Graham The project is in the planning phases at the moment, but they're considering a whole slew of possible changes, fixes, and workarounds to make this stupid and annoying problem just go away. In 2026, nobody should be dealing with manually editing /etc/fstab or getting frustrated over supposedly disappearing network shares.

The developer working on Xfwl4, the Wayland compositor for Xfce, has published the new compositor's very first alpha release. Considering it's only been six months or so of work, it's impressive to see the effort reach this state already. The end goal of xfwl4 is to behave as closely as possible to an Xfce desktop running on an X server. Ideally a user could switch between the two without even knowing there's a difference. In reality, of course, it won't be quite that seamless, and there's still more work to be done to get as close as possible to that ideal. This is a first solid cut at it, at the very least. Brian Tarricone Being the very first alpha release, it won't surprise you there's a few things missing or broken at this point. Still, if you're brave, you can download and build the release and try it out.

Valve officially made the Steam Machine available (sort of but not really) today, and if you were hoping for the president of the Yacht Collectors' Club to have found a loophole through the RAM and storage crisis, I'll be the bearer of bad news: the base Steam Machine model with 512GB of storage and no controller costs $1049 or 1039. It's clear that this price is significantly higher than Valve had originally anticipated, as the company dedicates the first part of its press announcement to this sticker shock. Steam Machine,like our other hardware products, is made up of many components that we source from manufacturers around the world. The price at which we sell our hardware is a direct result of the cost of these components. We felt like we had a good understanding of how those costs might change over time when we first started sourcing them for Steam Machine back in 2023. That understanding was born from the many years of data we all have about the evolution of PC hardware prices - primarily, that it tends to get cheaper over time as new technology arrives. Over the past year or so, that has changed quickly and significantly, most visibly for RAM and storage components. There are a variety of reasons, all of which are affecting hardware products everywhere. The overall effect is that our original goal for the price of Steam Machine is no longer viable. So the prices we're sharing today reflect the state of the world for manufacturing; or, more accurately, it reflects the price of the components as we've secured them over the past 6 months. Price wasn't the only thing impacted by all of this: availability was as well. There were periods where we found we couldn't source some of our components at all, at any price. More than anything else, this has impacted the number of units we've been able to produce for launch. Valve press announcement As Valve mentions, availability is also going to be an issue, and thus they've had to settle on a complex reservation and lottery system. Between now and 25 June, you can sign up for a model, after which the entire pool of reservations will be randomised to determine a waitlist order. As machines become available, they will simply go down the list from first to last as determined by that randomisation. In other words, you can't just go out and buy one right away. At this price and for the hardware the Steam Machine contains - an AMD Zen 4 CPU with 6c/12t up to 4.8 Ghz, a custom RDNA3 GPU, and 16GB of DDR5 RAM and 8GB of DDR6 video RAM - you're probably better off sticking with what you already have. Until the AI" bubble pops and prices come down again, that is. Thanks, AI" techbros. Everybody despises you.

In macOS, you can apparently create files and directories in the Finder with names that include slashes. If you then go into the terminal and take a look with ls, you'll see that the slashes are actually colons. I don't understand all the nuances, but I know this is a side-effect of the fact that macOS has not one buttwopath separators: the slash (/) and the colon (:). The two separators are used in different contexts, and the system will translate between them as needed. These two separators reflect the two parent systems of modern macOS:classic Mac OSand theUnix-like NeXTSTEP. When they were joined together, Apple's engineers had to build a file system that was compatible with both the classic Mac's file system (the Mac OS Extended File System, aka HFS+), and with NeXTSTEP's file system (the Unix file system, aka UFS). Among other differences, these systems had different path separators: HFS+ used a colon, while UFS used a slash. Alex Chan (article from 2021) I had no idea macOS worked this way, but it makes sense considering the platform's dual history. What's interesting is that when Apple moved to APFS almost a decade ago, this duality in path separators remained, most likely for backwards compatibility reasons. In a sense, this is somewhat similar to Windows supporting both backward and forward slashes, with the former being a leftover from DOS, and the latter an addition (to Windows) from the UNIX world. None of that beats Windows when using the Japanese or Korean locale, though. Because Japanese and Korean Windows use different codepages than Windows in the Americas and Western Europe, these versions of Windows render the backslash as the yen sign () and and won () sign respectively. As such, something like the Program Files directory actually renders like C:Program Files and C:Program Files. Similar issues occurred in other Windows locales as well, but the impact of this in Japan and South Korea were so widespread that people just expect it to be that way, even if it's easily fixed today. I can't find if Windows 11 still uses / in Japan/South Korea, since the last references of it I can quickly uncover all point to Windows 10.

Apple's Swift has become the de-facto language for Apple's own developers for a while now, and it seems that with the new operating system releases from the company unveiled during WWDC, Switch is now also being used in the kernel. Naturally I dropped what I was doing and went grepping through the iOS 27 kernelcache. Alas, nothing came of it. All is not lost though: I found the Embedded Swift runtime in macOS 27, sitting incom.apple.kec.pthreadof all places. Then I went poking around the root filesystem and it turns out Apple gave the whole effort a name: KernelKit. Let's dissect it. Josh Maine It's still quite limited at this time, which makes sense - you don't want to be too crazy with the core of the operating system that runs on god knows how many PCs, smartphones, and other devices. It's also entirely contained within a few kexts as embedded runtimes, and the XNU kernel itself remains entirely C and C++.

Every website has a favicon. It's that little icon in your browser tab. Usually you upload it once and then never think about it again. But. A favicon is just an image. An image is just pixels. And pixels are just bytes. So of course I wondered if I could store something inside one. Tim Wehrle I love it when people do something useless just for fun.

I mean, this is preaching to the choir, but let's go anyway. I liked the UIs of the entire era from 3.0 to 2000, really. I'm mostly using Windows 2000 as an example here because it runs so well in QEMU/KVM and that allows me to easily take screenshots. Some of the following will sound absolutely trivial, but I think it's worth pointing out. movq.de blog Just a series of observations about how much better graphical user interfaces were back in the '90s and early 2000s. We've lost so many affordances based on both common sense and scientific study, and what we ended up with is a confusing, inconsistent mess. It doesn't really matter where you look - user interface design has deteriorated since the early 2000s, a decline that only accelerated thanks to the arrival of the iPhone, where consistency is a dirty word, and the web, where the advertising people took prominence over the design people. I just want my buttons to look like buttons man.

A fascinating novel approach by researchers at MIT, called Fractal, to study in-depth how processors actually work. A team at MIT's Computer Science and Artificial Intelligence Laboratory (CSAIL) decided to build something different. Fractal, an operating system kernel written from the ground up, treats the hardware itself as the object of study. Its first major use, a deep look at branch predictors - a CPU's way of guessing what code to run next, before it knows for certain, so it doesn't have to waste time waiting to find out - inside Apple's M1 processor, has already turned up findings that prior work missed, including the first evidence that a class of speculative attack known as Phantom" affects Apple Silicon. We're using hardware in ways it wasn't designed for," says Joseph Ravichandran, the MIT PhD student in electrical engineering and computer science (EECS) who led the project. It's not even obvious that this is a possible thing you could do with the hardware. But we found a way to pull all these different primitives off. It's like a microscope. If you've got a hand magnifying glass, you can see a little bit. But if you had an electron microscope, now we're really talking. That's what Fractal is. The electron microscope of operating systems." Rachel Gordon at MIT News While Fractal is small, its creators also added POSIX system calls, a C library, vim, GCC, a shell, and more. This way, it feels more familiar, and makes it easier for researchers to get started with the tool. Fractal is open source and hosted on GitHub, it has its own website, and there's a detailed research paper with more in-depth information.

Five years after releasing the Amiga 1000, Commodore was about to launch the Amiga 3000, their first real high-end Amiga. With a 68030 processor, on-board SCSI and a slightly updated graphics chipset, all in a sleek desktop case, the Amiga was truly ready for the era of professional 32-bit computing. But Moore's law wasn't the only thing thad had been pressuring Commodore since the release of the Amiga 1000: The desktop metaphor had matured even further, and the competition had been hard at work. IBM had launched OS/2, Windows 3.0 had turned Microsoft's offering from a proof of concept into something actually usable, and new players had entered the scene - among them NeXTStep, with its polished 3D look. It was time to bring AmigaOS, too, into the 1990s. Carl Svensson It's interesting - there's a lot of focus on the first version of the Amiga operating system and the third one, but you don't hear a lot about AmigaOS 2.x. It turns out this is rather odd, because as Svensson details, this version came with an absolute ton of changes and improvements, from an entirely new widget toolkit to a brand new file system, and so much more. The new widget toolkit and accompanying style guide also ensured that the operating system looked, felt, and behaved consistently. Remember when we cared about that? There's so much more cool features, though, like command history, line editing, universal clipboard support and more just for the CLI, as well as something called Commodities. These were tiny little programs managed from a central location, which didn't even need a GUI to work. Commodities included by default were things like ClickToFront, a focus-follows-mouse option, and more. Oh and of course, BASIC was replaced by ARexx. The list just keeps going, and you should really read Svensson's article.

Oracle is sticking to its promise of more regular Solaris updates with the release of Oracle Solaris 11.4 SRU93. This release, like other SRU releases, is for paying Solaris customers, as the CBE releases for enthusiasts are on a different cadence. With Solaris' focus being on enterprise server environments, it should come as no surprise that most of the changes and improvements are focused on things like enterprise networking and security, such as changes to how policy settings for the Kernel Crypto Framework (KCF) are stored, moving from using RPC over sockets instead of STREAMS, and more. Of course, there's also the long list of updated open source packages. SRU 93.221.2 updates a broad set of platform, runtime, developer, networking, desktop, and open source components. Notable updates include Apache Tomcat to 9.0.116, bash to 5.3 patch 9, BIND to 9.20.18 and 9.20.21, Django 4.2 to 4.2.30, Django 5.2 to 5.2.13, Firefox to 140.8.0esr, Golang to 1.25.8, Node.js 20 to 20.20.2, Node.js 22 to 22.22.2, Node.js 24 to 24.14.1, NSS to 3.119.1, Perl to 5.42, Python 3.11 to 3.11.15, Python 3.13 to 3.13.12, RabbitMQ to 4.2.4, Thunderbird to 140.8.0esr, vim to 9.2.0340, and zlib to 1.3.2. Additional updates include development tools, Python modules, X11 utilities, printing components, libraries, cryptographic packages, networking tools, and desktop-related packages. Colin Kavanagh at the Oracle Solaris Blog Existing Oracle Solaris customers can update to the new release through pkg update.

Yesterday, Google released Android 17 to Pixel devices, so late last night I updated my Pixel 10 Pro with the intent to write a news item about the release today. The reality is that that I totally forgot I even upgraded last night, because Android 17 is about the biggest nothingburger I've ever seen. Virtually all of the new features listed in the upgrade blurb on my phone were AI" nonsense I don't encounter, so over the course of the day, I didn't really notice anything new about my phone's operating system. The only interesting feature that I think will be particularly useful on tablets and perhaps foldable devices is something called App Bubbles". Basically, you can turn any application into an overlay that can be minimised into a bubble, which then lives anywhere on your screen. Tap it, and you can maximise the overlay again. This little multitasking bubble can contain multiple applications, effectively making it a dock or taskbar. Neat, but I didn't see much use for it on my phone. The remainder of the new non-AI" features are hard to spot, at best. I guess the ability to turn one half of a foldable display into a gamepad is neat if you can deal with gaming on glass buttons (I cannot), and the changes to location access (you can now grant it for just one time) and contacts access (it's more fine-grained and temporary now instead of granting access to everything forever) are welcome, but that's about it for user-facing features. Under the hood, the one thing that stands out is that Google is enforcing stricter memory limits for applications, based on how much RAM a device has. The idea is that this should prevent memory leaks from getting out of control and leading to crashes, which is nice, especially for devices with less RAM. Android 17 is available for Pixel devices now, and will probably find its way to non-Pixel devices over the coming months or years. With how little meat there is on Android 17's bones, this might be the first release where Android's update woes don't really matter.

The KDE team released KDE Plasma 6.7 today, and with it comes a long list of improvements, new features, bug fixes, new old themes, and so much more. A new feature that is sure to please those among us who use virtual desktops: you can now have different virtual desktop setups per display. It's been a long-requested feature, so it's great to see it makes its way to the KDE users. I despise virtual desktops, but I'm happy to see something that I assumed was already part of KDE to finally actually become available. Another major feature in KDE Plasma 6.7 is something we've already talked about: the return of the classic Oxygen and Air themes from the KDE 4.x days. These themes have seen extensive work over the past year or so to make them usable on the latest KDE release, which includes tons of bug fixes, visual nips and tucks, and countless additions to the collection of assets required to make a modern KDE theme look complete. This includes a ton of new icons in the old styles, light and dark modes, accent colour support, and much more. There's still work left here, including adding support for QtQuick/Kirigami applications - which brings us to the next major new addition to KDE 6.7 This is also something we've already talked about: Union. I won't repeat what I already explained last time Union came up, but suffice it to say that Union effectively unifies the various different ways KDE applications are themed, allowing theme designers to use relatively standard CSS to create themes that cover every aspect of the KDE user experience. Before Union, theme designers had to create individual, unique themes for a variety of parts of KDE - the Plasma desktop, QtWidgets using QStyle, QtQuick/Kirigami - which was a ton of work, and in the case of QtQuick/Kirigami, wasn't really possible at all. As such, without Union, KDE's theming is essentially broken, and Union fixes that. For now, Union is not enabled by default, and must be installed and enabled separately for testing. Of course, there's a ton of other smaller new features, changes, and bug fixes as well. KDE Plasma 6.7 will find its way to your distribution soon enough.

A week or so ago, Apple announced a bunch of features for the App Store on iOS, including personalised recommendations based on your activity and usage of iOS. It turns out this includes a keylogger (taplogger?) in the App Store, which records every single tap you make, every single letter you enter, and a lot of other information. All of this information is unencrypted and sent to Apple. Now Apple is putting the extensive identifiable analytics they collect in the App Store in action. They record every tap and there's no way to turn it off. They can even calculate your typing speed. Michael Tsai, quoting Mysk The provided screenshots of the data collected are terrifying, especially because the data is unencrypted, sent to Apple, and fully tied to your user account. Apple clearly wants a slice of that big, juicy advertising pie, and they, too, are discovering that the easiest and best way to serve targeted ads is to collect as much data as they can about you. Of course, this is something the entire internet (but not OSNews!) and several megacorporations are built on by now, but Apple has been incredibly sanctimonious about how it supposedly actually cares about user privacy, making this keylogger yet another case of Apple's hypocrisy on full display. Of course, if you care about privacy, you're entirely free to download your iOS applications from somewhere other than the App Store and install them yours... Oh, wait.

Another story from the good old days from Raymond Chen. During an exchange of war stories, a colleague of mine told one from back in the days when Windows included a processor emulator for x86-32 on systems that natively ran some other processor. (This has happened many times. And no, I don't know which processor this particular story applied to.) Raymond Chen at The Old New Thing So the core of the story comes down to this: All in all, it took this program 256 kilobytes of code to initialize 64 kilobytes of data. Raymond Chen at The Old New Thing The people working on Windows were so offended by this, they added code to the processor emulator just to fix this program.

Speaking of FreeBSD, the project released version 15.1 of their operating system today. As it's a point release, it's not full of massive changes, but it still brings the LinuxKPI-based wireless drivers up to Linux 7.0, support for the C23 version of the Chas progressed considerably, Unicode has bene updated to version 17.0.0 and CLDR 48, and more.

Expect to see more and more articles like this one, as more and more people discover that FreeBSD's desktop/laptop support keeps improving rapidly. FreeBSD 15 really feels like a breakthrough release. It's always been my favorite operating system for servers, but with the arrival ofpkgbase, massive improvements to theLinuxKPIdrivers, and the launch of theLaptop Support and Usability Project, it's become my primary desktop, too. Cullum Smith Since Smith tried FreeBSD 14.0, there's now KDE Plasma 6.x, you can leave legacy X11 behind and use Wayland on FreeBSD now, and support for Intel Wi-Fi chips has greatly expanded. Apparently, battery life has improved as well, which is one of the hardest problems to solve for an operating system, especially with the wide variety of hardware combinations in the x86 world. The rest of Smith's article is a guide to setting up FreeBSD 15 with KDE and Wayland. It's quite detailed with a ton of low-level tuning and fiddling, accompanied by clear and concise explanation of what the changes do, which I really like. Definitely a bookmark for anyone who wants to try out FreeBSD with KDE.

It's been a while since we've had a new operating system project written in Rust, so let's look at Zinnia. The kernel is written in (almost) 100% Rust and attempts to avoid unsafe code where possible. It implements a big range of POSIX APIs in system calls, but also exposes common extensions found in Linux and BSDs, like epoll and timerfd. This allows it to run a somewhat modern desktop using Wayland and X11 sessions. Most drivers are implemented as modules. These are Rust ELF dylibs which get loaded and linked during boot from an initrd, similar to Linux systems. Zinnia can boot from any UEFI based system thanks to the Limine bootloader. Zinnia OS website At least Weston and Xfce can run on Zinnia, even on real hardware, which is quite an achievement. The project was started in 2024 as a learning endeavour, but quickly grew out of control, as these projects are wont to do. The code's open source.

We're a little deep into June already, but it's only now that Haiku published its monthly progress report for May. There's a bunch of fixes for drag-and-drop behaviour in Tracker, AVX512 support can now be enabled thanks to changes to the kernel's FPU handling, some low-level changes were made for the Rust and Zig compilers, and further improvements were made to the boot process on the Raspberry Pi 5 (although a lot more work is needed on that front). There's still no sixth beta since a few more blockers remain, but don't let that stop you from installing Haiku - it's stable enough as it is, sixth beta or no.

Tribblix, the Illumos distribution focused on giving you a classic UNIX-style experience, has been updated with the release of Milestone 40. This version has some major component updates. Perl in now 5.42 instead of 5.34, and the default Python is now 3.13. The GCC suite is now version 14.2.0, go is version 1.26, Xfce has been updated to version 4.18, node is v22, with v24 added and v20 removed. Tribblix M40 release notes There's a more detailed changelog, as well as the downloads page to get started. If you're already running Tribblix, you can update in-place, of course.

An infuriating story about something most of us don't really stop to think about: e-books and the rendering engines companies and software use to display them. It's the year 2026. Thanks to the horrendous RMSDK which Kobo decided to use as their backbone for all book rendering (probably for DRM reasons), a single line of perfectly valid CSS turns a perfectly valid EPUB file into a corrupted file" on Kobo and just drops the whole book. No clear error message, no fallback. Just a massive fail. Andre Klein The level of obnoxiousness goes even deeper: Kobo devices ship with a better, actually maintained renderer for e-books as well, but in order to have a book use it, the book file in question needs to have a specific file extension. Remember that e-book files are just packaged websites; there's no reason to do any of this nonsense with two rendering engines, one of which is shit and frozen in time. I have never had to do anything related to creating an e-book - I just put books on my own Kobo and read them - and even I am getting annoyed just reading this.

How far can you get, application development-wise, by using only the original APIs from Windows 1.0, and only whatever came included by default with Windows 1.0? I finally decided to write an application for the very first version of Windows and see how different the modern WinAPI really is from its earliest versions. Windows 1.0 came out back in the mid-1980s - the era of 16-bit processors, MS-DOS, and cooperative multitasking. At first glance, you might think it has almost nothing in common with modern Windows, but when you look specifically at the application API, that's where things get interesting. I wanted to see how far it would be possible to go using only the capabilities of the first version of Windows. I didn't want to just make a minimal example with a window and a menu, but a small, complete application with graphics, keyboard input, timers, and constant redrawing. For this experiment, I chose Xonix - a simple yet surprisingly addictive game. Stanislav Safronov It turns out that surprisingly, despite the 40 years and massive changes since Windows 1.0, there's still a lot that feels recognisable. It's also remarkable that the code Safronov ended up with ran on every version of Windows from 1.0 to 10, but sine it's a 16 bit application it no longer works on Windows 11. It also had a hiccup on Windows 95, but he suspects that's an issue in the 16 bit subsystem in Windows 95, and not in his code. The code's available on GitHub.

In 1994 I got my first computer: an Intel i486 DX2-66 with 4 MB RAM and a 512MB harddisk. The software was IBMs OS/2 and Microsofts Windows 3.11. In the next four years I was upgrading this machine every few months with more RAM (up to 16MB), a CD-ROM-drive and a soundblaster card. So I learned upgrading this machine, installing new software and finally learned how to program new software using BASIC. But I never got in touch with the boot-process or the details of MS-DOS. In 2026, 32 years later, I learned from some screenshots of the DDX3216, that Behringer used a real 386 processor within this machine. Immediately, some of my neurons fired in my head and I pondered if I could boot software and even a full operating system on this device. My goal was to learn how an x86-system is booting, how DOS takes over and what is necessary to get into the shell. Christian Noding So this introduction is a bit cryptic if you're not aware of what a DDX3216 is - I sure had no idea. The Behringer DDX3216 is a digital mixing console for use in music studios, and I think it's about 25 years old or so. Apparently it's built around a 386, and as Noding details in this article, that means it can be made to run DOS. It also happens to have a small black and white LCD, so there's a place to route output to, as well. Furthermore, once you open it up, you'll find things like a BIOS chip, PCMCIA slot, a floppy controller, serial/parallel port controller, and more. Sure sounds like a PC to me. After talking to companies and individuals who might have a BIOS compatible with the AMD 386 SoC used in the device bore no fruit, Noding decided to develop his own BIOS, which involves getting all the devices, interfaces, and even the display to work properly as well. The next step was getting DOS to work, and after MS-DOS 6.22 refused to work, FreeDOS did the trick and booted just fine. There's still a ton more possible things that can be done here, but this is already quite amazing.

TrueType is a widely used vector font standard for rendering text in web pages, PDFs, operating systems, and applications. Familiar fonts like Helvetica, Garamond, and Monaco are all built on TrueType outlines. The format specifies a hinting interpreter intended to help outlines rasterize faithfully on low-resolution displays. Modern high-resolution displays enable beautiful typography from outlines alone, but TrueType fonts that need hinting to render legibly remain in use and we continue to support them. Font parsers process data from untrusted sources, making the TrueType hinting interpreter a security-critical attack surface. To make the format more resilient on Apple platforms, we rewrote its hinting interpreter from C to memory-safe Swift for the Fall 2025 releases. In addition to memory safety, we also improved performance: on average, our Swift interpreter runs 13% faster than the C interpreter it replaced. Scott Perry This article provides a deep dive into how, exactly they did that.

If you want to try out a modern Amiga operating system, your choices are severely constrained. Both MorphOS and AmigaOS 4 need PowerPC hardware, and at the moment, there's little to no modern hardware available for purchase to run these operating systems on. The only AmigaOS 4 hardware you can buy is either incredibly outdated, incredibly expensive, or both, and while MorphOS does run on readily available Apple PowerPC machines, those, too, are getting quite long in the tooth and performance simply isn't keeping up. Until the Mirari becomes available - with the project steadily progressing, I have high hopes - the reality for people wanting to try out AmigaOS or MorphOS is going to be expensive, at best. Or is it? QEMU exists, and QEMU can emulate various PowerPC systems just fine. Shouldn't it be possible to run these two unique operating systems in a virtual environment on your modern PC, thereby making it trivial for those of us interested in the world of Amiga to dip our toes into the water without having to spend inordinate sums for outdated hardware? It turns out that yes, this is entirely possible, and as I highlighted almost a year ago, George Sokianos has made this process effectively foolproof by developing a custom GUI frontend for QEMU specifically designed to make it incredibly easy to set up and run AmigaOS 4 and MorphOS in QEMU virtual machines. We're almost a year since that first version, and in that time, Sokianos has updated the tool, called Kyvos, to version 2. It costs a mere 9, and works on Linux (x86 and ARM), Windows (x86 and ARM) and macOS (x86 and ARM). You also get an incredibly detailed manual with step-by-step instructions for every supported operating system and specific emulated machine, which includes instructions for the convoluted AmigaOS 4 installation process, as well as a bunch of other information and helpful tips. In addition, the manual includes links to where you can buy AmigaOS 4 - be sure to use these specific links to buy AmigaOS 4, because Sokianos gets a commission for sales through these links. AmigaOS 4 costs like 30, so it's not a big investment. MorphOS can be downloaded for free, but after 30 minutes of use, the operating system will slow down and cripple itself, unless you pay for and register your copy for 79. I own a copy for my 17'' PowerBook G4 1.25Ghz, but I think copies are tied to hardware, so I haven't tried registering it with my key yet. The MorphOS registration tool does not accept virtual machines, so you can't use it to buy a copy for a virtual machine. Kyvos' graphical user interface mimics the UI of other virtual machine software like VirtualBox, and it will check to make sure you have all the correct dependencies and requirements installed. The guided setup processes for MorphOS and AmigaOS 4 virtual machines will tell you exactly which operating system ISOs and files you need and makes sure you have them, before setting up the QEMU virtual machines with the optimal settings. Once created, start the virtual machine, and they'll boot from the installation media. Follow the included manual as you install the operating systems, including some post-install help, and you'll end up with fully working, network-capable virtual machines running MorphOS and AmigaOS 4. Both installation and setup procedures worked without any issues on my machine, and within like half an our I had to two fully working copies of MorphOS and AmigaOS 4 running on my Linux desktop gaming PC (I exempted myself from the Windows 11 incentive for this one, since my Linux gaming PC is by far the most powerful computer I own). Networking and sound works - AmigaOS 4 requires some post-install steps for those, listed in the Kyvos manual - and I could browse the web right away with the included web browsers. The online update tool for AmigaOS 4 also works perfectly, allowing me to upgrade to the latest version of the operating system and various included components. I'm anything but a MorphOS or AmigaOS 4 expert, so I can't confidently say much about performance compared to best real compatible hardware out there, but at least for MorphOS I can say it runs considerably faster in this virtual machine than it does on my old 17'' PowerBook G4 1.25Ghz. I feel like AmigaOS 4 runs a bit smoother than MorphOS does, as with the latter I experienced the occasional hiccup and stutter which were absent on AmigaOS 4. Still, both are entirely usable and a pleasure to use. With how limited the hardware selection for these two operating systems is, using QEMU through Kyvos is by far the easiest and most straightforward way to dip your toes into the waters of the modern Amiga operating systems. For a total of around 40, you'll be running AmigaOS 4 in a very capable and straightforward way, and if and when MorphOS allows registration for virtual machines (they really should), an additional 79 will give you a fully working installation of that unique operating system, too. Kyvos is a complete no-brainer for anyone reading OSNews.

Video game consoles have a long history with web browsers. From the advent of the World Wide Web, consoles have been trying to get online. Browsers on video game consoles were initially very much an attempt to provide a cheap gateway to the web for a casual audience lacking technical expertise, though as time progressed they've become a greater and more integrated part of systems. This article takes a look at browsers on video game consoles in detail, though only covers official web browsers. Many consoles have browsers installable via custom firmware and homebrew, but they're beyond the scope of this post, as are non-web systems such as Satellaview and online services that didn't provide a browser, such as XBAND, Sega Meganet, and Sega Channel. Declan Chidlow The article starts off with the Philips CD-I, which has always been a fascinating product for technology fans in The Netherlands because that's where Philips is from. Memory that far back is untrustworthy, but I can definitely remember being inundated with commercials, advertising, magazine articles, and newspaper reports about the CD-I, all throughout its rather troubled life. Yet, I don't remember anything about it being capable of browsing a rudimentary web. Of course, we're talking 1995 here, a time when I didn't even have internet at home yet, although I did use the web at a friend's place at that time. We didn't get internet at home until I think 1997 or 1998, followed by the move to broadband cable internet just a year later, since our small rural town happened to be one of the first places to get broadband. Good times. Did anyone ever actually use browsers on consoles, though? I mean, using them always felt incredibly clunky, and by the time they were capable enough to really do anything we all had laptops and later smartphones anyway. I certainly don't remember anyone using them for anything but a gimmick, but perhaps my sample size was far too small and not diverse enough.