System76, creator of Pop!_OS and prominent Linux OEM, has just announced the release of Pop!_OS 24.04 LTS – normally not something I particularly care about, but in this case, it comes with the first stable release of COSMIC Desktop. COSMIC is a brand new desktop environment by System76, written in Rust, and after quite some time in development, it’s now out in the wild as a stable release.

Today is special not only in that it’s the culmination of over three years of work, but even more so in that System76 has built a complete desktop environment for the open source community. We’re proud of this contribution to the open source ecosystem. COSMIC is built on the ethos that the best open source projects enable people to not only use them, but to build with them. COSMIC is modular and composable. It’s the flagship experience for Pop!_OS in its own way, and can be adapted by anyone that wants to build their own unique user experience for Linux.

↫ Carl Richell

You don’t need to run Pop!_OS to try out COSMIC, as it’s already available on a variety of other distributions (although it may take a bit for this stable version to land in the respective repositories).

I’m sure most of us here are aware of the bright red-and-yellow colour scheme called “Hot Dog Stand”, included in Windows 3.1. While it’s not the only truly garish colour scheme included in Windows 3.1, its name probably did a lot to make it stand out from the others. There’s been a ton of speculation about the origins of the colour scheme, and why it was included in Windows 3.1, but it seems nobody ever bothered to look for someone who actually worked on the Windows 3.1 user interface – until now.

PC Gamer’s Wes Fenlon contacted Virginia Howlett, Microsoft’s first user interface designer who joined the company in 1985, and asked her about the infamous colour scheme. It turns out that the origin story for the infamous colour scheme is rather mundane. In Howlett’s own words:

I do remember some discussion about whether we should include it, and some snarky laughter. But it was not intended as a joke. It was not inspired by any hot dog stands, and it was not included as an example of a bad interface—although it was one. It was just a garish choice, in case somebody out there liked ugly bright red and yellow.

↫ Virginia Howlett, quoted by Wes Fenlon in PC Gamer

Howlett then lists a few other included colour schemes that were just as garish, or even more so, as examples to underline her point. Personally, I’m a huge proponent of allowing users to make their interfaces as ugly and garish as they want, as the only arbiter on what’s on your screen is you, and nobody else. Hot Dog Stand and similar garish themes need to make a comeback, because there’s bound to be some people out there whose vibes align with it.

I have some potentially devastating news for POWER users interested in using FreeBSD, uncovered late last month by none other than Cameron Kaiser.

FreeBSD is considering retiring powerpc64 prior to branching 16, which would make FreeBSD 15 the last stable version to support the architecture. (32-bit PowerPC is already dropped as of FreeBSD 14, though both OpenBSD and NetBSD generally serve this use case, and myself I have a Mac mini G4 running a custom NetBSD kernel with code from FreeBSD for automatic restart.) Although the message says “powerpc64 and powerpc64le” it later on only makes specific reference to the big-endian port, whereas both endiannesses appear on the FreeBSD platform page and on the download server.

↫ Cameron Kaiser

There’s two POWER9 systems in my office, so this obviously makes me quite sad. At the same time, though, it’s hard not to understand any possible decision to drop powerpc64/powerpc64le at this point in time. Raptor’s excellent POWER9 systems – the Blackbird, which I reviewed a few years ago, and the Talos II, which I also have – are very long in the tooth at this point and still quite expensive, and thanks to IBM royally screwing up POWER10, we never got any timely successors. There were rumblings about a possible POWER11-based successor from Raptor back in July 2025, but it’s been quiet on that front since.

In other words, there are no modern powerpc64 and powerpc64le systems available. POWER10 and brand new POWER11 hardware are strictly IBM and incredibly expensive, so unless IBM makes some sort of generous donation to the FreeBSD Foundation, I honestly don’t know how FreeBSD is supposed to keep their powerpc64 and powerpc64le ports up-to-date with the latest generation of POWER hardware in the first place.

It’s important to note that no final decision has been made yet, and since that initial report by Kaiser, several people have chimed in to argue the case that at least powerpc64le (the little endian variant) should remain properly supported. In fact, Timothy Pearson from Raptor Engineering stepped up the place, and stated he’s willing to take over maintainership of the port, as Raptor has been contributing to it for years anyway.

Raptor remains committed to the architecture as a whole, and we have resources to assist with development. In fact, we sponsor several FreeBSD build machines already in our cloud environment, and have kernel developers working on expanding and maintaining the FreeBSD codebase. If there is any concern regarding hardware availability or developer resources, Raptor is willing and able to assist.

↫ Timothy Pearson

Whatever decision the FreeBSD project makes, the Linux world will be fine for a while yet as IBM contributes to its development, and popular distributions still consider POWER a primary target. However, unless either IBM moves POWER hardware downmarket (extremely unlikely) or the rumours around Raptor have merit, I think at least the FreeBSD powerpc64 (big endian) port is done for, with the powerpc64le port hopefully being saved by people hearing these alarm bells.

Secretary of State Marco Rubio waded into the surprisingly fraught politics of typefaces on Tuesday with an order halting the State Department’s official use of Calibri, reversing a 2023 Biden-era directive that Mr. Rubio called a “wasteful” sop to diversity.

While mostly framed as a matter of clarity and formality in presentation, Mr. Rubio’s directive to all diplomatic posts around the world blamed “radical” diversity, equity, inclusion and accessibility programs for what he said was a misguided and ineffective switch from the serif typeface Times New Roman to sans serif Calibri in official department paperwork.

↫ Michael Crowley and Hamed Aleaziz at The New York Times

With the current, rapidly deteriorating state of the Windows operating system, you have to take the small wins you can get: Microsoft is now offering the option of removing “AI” actions from Windows 11’s context menus. buried deep in the Windows 11 Insider Preview Build 26220.7344 release notes, there’s this nugget:

If there are no available or enabled AI Actions, this section will no longer show in the context menu.

↫ Windows Insider Preview release notes

If you then go to Settings > Apps > Actions and uncheck all the “AI” actions, the entire submenu in Windows 11’s context menus will vanish. While this is great news for those Windows users who don’t want to be bothered by all the “AI” nonsense, I wish Microsoft would just give users a proper way to edit the context menu that doesn’t involve third party hackery. KDE’s Dolphin file manager gives me full control over what does and does not appear in its context menu, and I can’t imagine living without this functionality – there’s so many file-related operations I never use, and having them clutter up the context menu is annoying and just slows me down.

There’s more substantial and important changes in this Insider Preview Build too, most notably the rollout of the Update Orchestration Platform, which should make downloading and installing application updates less cumbersome, but since it’s a new feature, application won’t support it right away. This release also brings the new Windows MIDI Services, and Microsoft hopes this will improve the experience for musicians using MIDI 1.0 or MIDI 2.0 on Windows. There’s a slew of smaller changes, too, of course.

I’m not exactly sure when these new features will make their way to production installations – who does, honestly, with Microsoft’s convoluted release processes – but I hope it’s sooner rather than later.

When Mac OS X was designed, it switched to the bundle structure inherited from NeXTSTEP. Instead of this multitude of resources, apps consisted of a hierarchy of directories containing files of executable code, and those with what had in Mac OS been supporting resources. Those app bundles came to adopt a standard form, shown below.

↫ Howard Oakley

A short, but nonetheless informative overview of the structure of a macOS application. I’m sure most people on OSNews are aware that a macOS application is a bundle, which is effectively a glorified directory containing a variety of files and subdirectories that together make up the application. I haven’t used macOS in a while, but I think you can right-click on an application and open it as a folder to dig around inside of it.

I’m trying to remember from my days as a Mac OS X user – 15-20 years ago – if there was ever a real need to do so, but I’m sure there were a few hacks you could do by messing around with the files inside of application bundles. These days, perhaps with all the code-signing, phoning-home to Apple, and other security trickery going on, such acts are quite frowned upon. Does making any otherwise harmless changes inside an application bundle set off a ton of alarm bells in macOs these days?

OSNews is funded entirely by you, our readers. There are no ads on OSNews, we are not part of a massive corporate publishing conglomerate like virtually every other technology news website, there are no wealthy (corporate) benefactors – it’s just whatever funds you, our readers, send our way. As such, I sometimes need to remind everyone about this, and December, the holiday month, seems as great a time as any to do this.

If you want to support a truly independent technology news website, free from the corrupting influences of corporate interests, advertising companies, managers pushing “AI”, and all the other nonsense destroying the web we once loved, you can do so by donating to keep OSNews alive. This gives me the time and means to write 9000 words about dead computer ecosystems, and I’m already working on an article about the next final UNIX workstation.

• If you want to make a single, non-recurring donation, you can donate to the OSNews Ko-Fi. Every amount, large or small, is deeply appreciated.
• If you want to make recurring donations, you can become an OSNews Patreon.
• You can also buy some OSNews merch! We’ve got some great shirts and mugs with awesome designs, and every individual purchase nets OSNews about $8.

Every single donation, large or small, is deeply appreciated and keeps the lights on around here. There aren’t many websites like OSNews left, especially not independent ones that answer to nobody. Your support keeps OSNews going, with June 2026 marking a special moment for me: it will mark twenty years since I took over this place. I’m not expecting a party – you’re paying me to work, not to party – but it is still a meaningful anniversary for me personally.

Some of you may be aware of rePalm, a project by Dmitry Grinberg to port the PalmOS to various devices it was never supposed to run on. We covered rePalm back in 2019 and again in 2023. His latest project involved porting PalmOS to a set of digital toys that were never intended to run PalmOS in any way.

Fisher-Price (owned by Mattel) produced some toys in the early 2000 under the Pixter brand. They were touchscreen-based drawing toys, with cartridge-based extra games one could plug in. Pixter devices of the first three generations (“classic”, “plus”, and “2.0”) featured 80×80 black-and-white screens, which makes them of no interest for rePalm. The last two generations of Pixter (“color” and “multimedia”) featured 160×160 color displays. Now, this was more like it! Pixter was quite popular, as far as kids’ toys go, in USA in the early 2000s. A friend brought it to my attention a year ago as a potential rePalm target. The screen resolution was right and looking inside a “Pixter Color” showed an ARM SoC – a Sharp LH75411. The device had sound (games made noises), and touch panel was resistive. In theory – a viable rePalm target indeed.

↫ Dmitry Grinberg

Considering the immensely limited ARMv7 implementation he had to deal with – no cache, no memory management unit, no memory protection unit – it’s a miracle Grinberg managed to succeed. To make matters even harder, the first revision boards of the “color” model only had 1MB of flash, which is incredibly small even for PalmOS 5, so he had to rewrite parts of it to make it fit. Implementing communication over infrared was also a major difficulty, but that, too he managed to get working – on a device that doesn’t have IrDA SIR modulation. Wild.

Grinberg went above and beyond, making sure the buttons on the devices work, developing and building a way to put PalmOS on a “game” cartridge, reverse-engineering the display controller to make sure things like brightness adjustment works, adding screen type detection for that one small run of Pixter Color devices that came with a TFT instead of an STN screen, and so, so much more. Until you read the article, you have no idea how much work Grinberg put into this project.

I continue to be in awe of Grinberg’s work every time I come across it.

Oracle has released Solaris 11.4 SRU 87, which brings with it a whole slew of changes, updates, and fixes. Primarily, it upgrades Firefox and Thunderbird to their latest ESR 140.3.0 releases, and adds GCC 15, alongside a ton of updated other open source packages. On more Solaris 11-specific notes, useradd’s account activation options have been changed to address some issues caused by stricter enforcement introduced in SRU 78, there’s some preparations for the upgrade to BIND 9.20 in a future Solaris 11 release, a few virtualisation improvements, and much more.

If you’re unclear about the relationship between this new release and the Common Build Environment or CBE release of Solaris 11.4 for enthusiasts, released earlier this year, the gist is that these SRU updates are only available to people with Oracle Solaris support contracts, while any updates to the CBE release are available to mere mortals like you and I. If you have a support contract and are using the CBE, you can upgrade from the CBE to the official SRU releases, but without such a contract, you’re out of luck.

A new CBE release is in the works, and is planned to arrive in 2026 – which is great news, but I would love for the enthusiast variant of Solaris 11.4 to receive more regular updates. I don’t think making these SRU updates available to enthusiasts in a non-commercial, zero-warranty kind of way would pose any kind of threat to Oracle’s bottom line, but alas, I don’t run a business like Oracle so perhaps I’m wrong.

This is the website for APL9, which is an APL implementation written in C on and for Plan 9 (9front specifically, but the other versions should work as well).

Work started in January 2022, when I wanted to do some APL programming on 9front, but no implementation existed. The focus has been on adding features and behaving (on most points) like Dyalog APL. Speed is poor, since many primitives are implemented in terms of each other, which is not optimal, but it helped me implement stuff easier.

↫ APL9 website

I honestly have no idea what to say.

I would think most of us here at OSNews are aware of VisiOn, the graphical multitasking operating system for the IBM PC which was one of the first operating systems with a graphical user interface, predating Windows, GEM, the Mac, and even the Apple Lisa. While VisiOn was technically an “open” platform anybody could develop an application for, the operating system’s SDK cost $7000 at the time and required a VAX system. This, combined with VisiOn failing in the market, means nobody knows how to develop an application for it.

Until now. Over the past few months, Nina Kalinina painstakingly unraveled VisiOn so that she she could recreate the SDK from scratch. In turn, this allowed developer Atsuko to develop a clean-room application for VisiOn – which is most likely the very first third-party application ever developed and released for VisiOn. I’ve been following along with the pains Kalinina had to go through for this endeavour over on Fedi, and it sure was a wild ride few would be willing (and capable) to undertake.

It took me a month of working 1-2 hours a day to produce a specification that allowed Atsuko to implement a clean-room homebrew application for VisiOn that is capable of bitmap display, menus and mouse handling.

If you’re wondering what it felt like: this project is the largest “Sudoku puzzle” I have ever tried to solve. In this note, I have tried to explain the process of solving this puzzle, as well as noteworthy things about VisiOn and its internals.

↫ Nina Kalinina

The article contains both a detailed look at VisiOn, as well as the full process of recreating its SDK and developing an application with it. Near the end of the article, after going over all the work that was required to get here, there’s a sobering clarification:

This reverse-engineering project ended up being much bigger than I anticipated. We have a working application, yes, but so far I’ve documented less than 10% of all the VisiHost and VisiOp calls. We still don’t know how to implement keyboard input, or how to work with timers and background processes (if it is possible).

↫ Nina Kalinina

I’d love for more people to be interested in helping this effort out, as it’s not just an extremely difficult challenge, but also a massive contribution to software preservation. VisiOn may not be more than a small footnote in computing history, but it still deserves to be remembered and understood, and Kalinina and Atsuko have done an amazing amount of legwork for whomever wants to pick this up, too.

Did you know that BG3 players exploit children? Are you aware that Qi2 slows older Pixels? If we wrote those misleading headlines, readers would rip us a new one — but Google is experimentally beginning to replace the original headlines on stories it serves with AI nonsense like that.

↫ Sean Hollister at The Verge

I’m a little teapot, short and stout. Here is my handle, here is my spout. When I get all steamed up, hear me shout. Tip me over and pour me out!

An exciting tidbit of news from Redox, the Rust-based operating system. Its founder and lead developer Jeremy Soller has merged the first changes for a modesetting driver for Intel graphics.

After a few nights of reading through thousands of pages of PRMs I have finally implemented a modesetting driver for Intel HD graphics on Redox OS. There is much more to do, but there is now a clear path to native hardware accelerated graphics!

↫ Jeremy Soller

Of course, all the usual disclaimers apply, but it’s an important first step, and once again underlines that Redox is turning into a very solid platform that might just be on the cusp of becoming something we can use every day.

It’s always a bit sad and a little awkward when reality starts hitting long-time fans and users of an operating system, isn’t it? I feel like I’m at least fifteen years ahead of everyone else when it comes to macOS, at least.

Over the last few weeks I’ve been discovering problems that have been eroding confidence in macOS. From text files that simply won’t show up in Spotlight search, to Clock timers that are blank and don’t function, there’s one common feature: macOS encounters an error or fault, but doesn’t report that to the user, instead just burying it deep in the log.

When you can spare the time, the next step is to contact Apple Support, who seem equally puzzled. You’re eventually advised to reinstall macOS or, in the worst case, to wipe a fairly new Apple silicon Mac and restore it in DFU mode, but have no reason to believe that will stop the problem from recurring. You know that Apple Support doesn’t understand what’s going wrong, and despite the involvement of support engineers, they seem as perplexed as you.

↫ Howard Oakley

I remember when Mac OS X was so far ahead of the competition it was honestly a little tragic. Around the late PowerPC and very early Intel days, when the iPhone hadn’t yet had the impact on the company it has now, the Mac and its operating system were the star of the company’s show, and you felt it when you used it. Even though the late PowerPC hardware was being outpaced left, right, and centre by Intel and AMD hardware in virtually every sense, Mac OS X more than made up for it being being a carefully and lovingly crafted operating system designed and developed by people who clearly deeply cared.

I used nothing but Macs as a result.

These days, everything’s reversed. By all accounts, Macs are doing amazing hardware-wise, with efficient, powerful processors and solid design. The operating system, however, has become a complete and utter mess, showing us that no, merely having great hardware does not make up for shit software in the same way the reverse was true two decades ago. I’d rather use a slower, hotter laptop with great software than a faster, cooler laptop with terrible software.

I’m not sure we’re going to see this trend reversed any time soon. Apple, too, is chasing the dragon, and everything the company does is designed around their cash cow, and I just don’t see how that’s going to change without a complete overhaul of the company’s leadership.