OSnews

There's been endless talk online about just how bad Apple's graphical user interface design has become over the years, culminating in the introduction of Liquid Glass across all of the company's operating systems this year. Despite all the gnawing of teeth and scathing think pieces before the final rollout, it seems the average Apple user simply doesn't care as much about GUI design as Apple bloggers thought they did, as there hasn't been any uproar or stories in local media about how you should hold off on updating your iPhone. The examples of just how bad Apple's GUI design has become keep on coming, though. This time it's Howard Oakley showing once again how baffling the macOS UI is these days. If someone had told me 12 months ago what was going to happen this past year, I wouldn't have believed them. Skipping swiftly past all the political, economic and social turmoil, I come to the interface changes brought in macOS Tahoe with Liquid Glass. After three months of strong feedback during beta-testing, I was disappointed when Tahoe was released on 15 September to see how little had been addressed. When 26.1 followed on 3 November it had only regressed, and 26.2 has done nothing. Here I summarise my opinions on where Tahoe's overhaul has gone wrong. Howard Oakley at The Eclectic Light Company Apple bloggers and podcasters are hell-bent on blaming Apple's terrible GUI design over the past 10 years on one man. Their first target was Jony Ive, who was handed control over not just hardware design, but also software design in 2012. When he left Apple, GUI design at Apple would finally surely improve again, and the Apple bloggers and podcasters let out a sigh of relief. History would turn out different, though - under Ive's successor, Alan Dye, Apple's downward trajectory in this area would continue unabated, culminating in the Liquid Glass abomination. Now that Alan Dye has left Apple, history is repeating itself: the very same Apple bloggers and podcasters are repeating themselves - surely now that Alan Dye is gone, GUI design at Apple will finally surely improve again. The possibility that GUI design at Apple does not hinge on the whims of just one person, but that instead the entire company has lost all sense of taste and craftmanship in this area does not cross their minds. Everyone around Jony Ive and Alan Dye, both below, alongside, and above them, had to sign off on Apple's recent direction in GUI design, and the idea that the entire company would blindly follow whatever one person says, quality be damned, would have me far more worried as an Apple fan. At this point, it's clear that Apple's inability to design and build quality user interfaces is not the fault of just one fall guy, but an institutional problem. Anyone expecting a turnaround just because Ive Dye is gone isn't seeing the burning forest through the trees.

We're all familiar with things like marquee and blink, relics of HTML of the past, but there are far more weird and obscure HTML tags you may not be aware of. Luckily, Declan Chidlow at HTMLHell details a few of them so we can all scratch shake our heads in disbelief. But there are far more obscure tags which are perhaps less visually dazzling but equally or even more interesting. If you're younger, this might very well be your introduction to them. If you're older, this still might be an introduction, but also possibly a trip down memory lane or a flashback to the horrors of the first browser war. It depends. Declan Chidlow at HTMLHell I think my favourite is the dir tag, intended to be used to display lists of files and directories. We're supposed to use list tags now to achieve the same result, but I do kind of like the idea of having a dedicated tag to indicate files, and perhaps have browsers render these lists in the same way the file manager of the platform it's running on does. I don't know if that was possible, but it seems like the logical continuation of a hypothetical dir tag. Anyway, should we implement bgsound on OSNews?

If you're building a package manager and git-as-index seems appealing, look at Cargo, Homebrew, CocoaPods, vcpkg, Go. They all had to build workarounds as they grew, causing pain for users and maintainers. The pull request workflow is nice. The version history is nice. You will hit the same walls they did. Andrew Nesbitt It's wild to read some of these stories. I can't believe CocoaPods had 16000 directories contained in a single directory, which is absolutely bananas when you know how git actually works. Then there's the issue that git is case-sensitive, as any proper file system should be, which causes major headaches on Windows and macOS, which are dumb and are case-insensitive. Even Windows' path length limits, inherited from DOS, cause problems with git. There just so many problems with using git for a package managers' database. The basic gist is that git is not a database, and shouldn't be used as such. It's incredulous to me that seasoned developers would opt for solutions" like this.

Christmas is already behind us, but since this is an announcement from 11 December - that I missed - I'm calling this a very interesting and surprising Christmas present. The team and I are beyond excited to share what we've been cooking up over the last little while: a full desktop environment running on QNX 8.0, with support for self-hosted compilation! This environment both makes it easier for newly-minted QNX developers to get started with building for QNX, but it also vastly simplifies the process of porting Linux applications and libraries to QNX 8.0. John Hanam at the QNX Developer Blog What we have here is QNX 8.0 running the Xfce desktop environment on Wayland, a whole slew of build and development tools like clang, gcc, git, etc.), a ton of popular code editors and IDEs, a web browser (looks like GNOME Web?), access to all the ports on the QNX Open-Source Dashboard, and more. For now, it's only available as a Qemu image to run on top of Ubuntu, but the plan is to also release an x86 image in the coming months so you can run this directly on real hardware. This isn't quite the same as the QNX of old with its unique Photon microGUI, but it's been known for a while now that Photon hasn't been actively developed in a long time and is basically abandoned. Running Xfce on Wayland is obviously a much more sensible solution, and one that's quite future-proof, too. As a certified QNX desktop enthusiast of yore, I can't wait for the x86 image to arrive so I can try this out properly. There are downsides. This image, too, is encumbered by annoying non-commercial license requirements and sign-ups, and this also wouldn't be the first time QNX starts an enthusiast effort, only to abandon it shortly after. Buyer beware, then, but I'm cautiously optimistic.

We've got more X11-related news this day, the day of Xmas. Phoenix is a new X server, written from scratch in Zig (not a fork of Xorg server). This X server is designed to be a modern alternative to the Xorg server. Phoenix' readme page Phoenix will only support a modern subset of the X11 protocol, focusing on making sure modern applications from roughly the last 20 years or so work. It also takes quite a few pages out of the Wayland playbook by not having a server driver interface and by having a compositor included. On top of that, it will isolate applications from each other, and won't have a single framebuffer for all displays, instead allowing different refresh rates for individual displays. The project also intends to develop new standards to support things like per-monitor DPI, among many other features. That's a lot of features and capabilities to promise for an X server, and much like Wayland, the way they aim to get there is by effectively gutting traditional X and leaving a ton of cruft behind. The use of Zig is also interesting, as it can catch some issues before they affect any users thanks to Zig's runtime safety option. At least it's not yet another thing written in Rust like every other project competing with an established project. I think this look like an incredibly interesting project to keep an eye on, and I hope more people join the effort. Competition and fresh, new ideas are good, especially now that everything is gravitating towards Wayland - we need alternatives to promote the sharing of ideas.

Wayback, the tool that will allow you to run a legacy X11 desktop environment on top of Wayland, released a new version just before the Christmas. Wayback 0.3 overhauls its custom command line option parser to allow for more X.org options to be supported, and its manual pages have been cleaned up. Other fixes merely include fixing some small typos and similar small changes. Wayback is now also part of Alpine Linux' stable releases, and has been made available in Fedora 42 and 43. Wayback remains alpha software and is still under major development - it's not yet ready for primetime.

Can you use a cheap FPGA board as a base for a new computer inspired by the original IBM PC? Well, yes, of course, so that's what Yuri Zaporozhets has set out to do just that. Based on the GateMateA1-EVB, the project's got some of the basics worked out already - video output, keyboard support, etc. - and work is underway on a DOS-like operating system. A ton of work is still ahead, of course, but it's definitely an interesting project.

Elementary OS, the user-friendly Linux distribution with its own unique desktop environment and applications, just released elementary OS 8.1. Its minor version number belies just how big of a punch this update packs, so don't be fooled here. We released elementary OS 8 last November with a new Secure Session-powered by Wayland-that ensures applications respect your privacy and consent, a brand new Dock with productive multitasking and window management features, expanded access to cross-platform apps, a revamped updates experience, and new features and settings that empower our diverse community through Inclusive Design. Over the last year we've continued to build upon that work to deliver new features and fix issues based on your feedback, plus we've improved support for a range of devices including HiDPI and Multi-touch devices. Danielle Fore at the elementary OS blog The biggest change from a lower-level perspective is that elementary OS 8.1 changes the default session to Wayland, leaving the X11 session as a fallback in case of issues. Since the release of elementary OS 8, a ton of progress has been made in improving the Wayland session, fixing remaining issues, and so on, and the team now feels it's ready to serve as the default session. Related to this is a new security feature in the Wayland session where the rest of the screen gets dimmed when a password dialog pops up, and other windows can't steal focus. The switch to Wayland also allowed the team to bring fractional scaling to elementary OS with 8.1. Elementary OS is based on Ubuntu, and this new release brings an updated Hardware Enablement stack, which brings things like Linux 6.14 and Mesa 25. This is also the first release with support for ARM64 devices that can use UEFI, which includes quite a few popular ARM devices. Of course, the ARM64 version comes as a separate ISO. Furthermore, there's a ton of improvements to the dock - which was released with 8 as a brand-new replacement for the venerable Plank - including bringing back some features that were lost in the transition from Plank to the new dock. Animations are smoother, elementary OS' application store has seen a slew of improvements from clearer licensing information, to a controller icon for games that support them, to a label identifying applications that offer in-app purchases, and more. There's a lot more here, like the accessibility improvements we talked about a few months ago, and tons more.

Mount Amiga filesystem images on macOS/Linux using native AmigaOS filesystem handlers via FUSE. amifuse runs actual Amiga filesystem drivers (like PFS3) through m68k CPU emulation, allowing you to read Amiga hard disk images without relying on reverse-engineered implementations. Amifuse GitHub page Absolutely wild.

Almost two months ago, a tape containing UNIX v4 was found. It was sent off to the Computer History Museum where bitsavers.org would handle the further handling of the tape, and this process has now completed. You can download the contents of the tape from Archive.org - which is sadly down at the moment - while squoze.net has a readme with instructions on how to actually run the copy of UNIX v4 recovered from the tape.

If you've been waiting for the right moment to try FreeBSD on a laptop, take note - 2025 has brought transformative changes. The Foundation's ambitious Laptop Support & Usability Project is systematically addressing the gaps that have held FreeBSD back on modern laptop hardware. The project started in 2024 Q4 and covers areas including Wi-Fi, graphics, audio, installer, and sleep states. 2025 has been its first full year, and with a financial commitment of over $750k to date there has been substantial progress. Alice Sowerby for the FreeBSD Foundation I think that's an understatement. As part of this effort, FreeBSD introduced support for Wi-Fi 4 and 5 in 2025, with 6 being worked on, and sound support has been greatly improved as well, with new tools and better support for automatic sound redirection for HDA cards. Another major area of improvement is support for various forms of sleep and wake, with modern standby coming in FreeBSD 15.1, and possibly hibernate in 15.2. On top of all this, there's the usual graphics drivers updates, as well as changes to the installer to make it a bit more friendly to desktop use cases. The FreeBSD project is clearly taking desktop and especially laptop seriously lately, and they're putting their money and developers where their mouth is. Add in the fact that FreeBSD already has pretty decent Wayland support, and it the platform will be able to continue to offer the latest KDE releases (and GNOME, if they figure out replacements for its systemd dependencies). With progress like this, we're definitely going to see more and more people making the move to FreeBSD for desktop and laptop use over the coming years.

If Excel rules the world, Word rules the legal profession. Jordan Bryan published a great article explaining why this is the case, and why this is unlikely to change any time soon, no matter how many people from the technology world think they can change this reality. Microsoft Word can never be replaced. OpenAI could build superintelligence surpassing human cognition in every conceivable dimension, rendering all human labor obsolete, and Microsoft Word will survive. Future contracts defining the land rights to distant galaxies will undoubtedly be drafted in Microsoft Word. Microsoft Word is immortal. Jordan Bryan at The Redline by Version Story Bryan cites two main reasons underpinning Microsoft Word's immortality in the legal profession. First, lawyers need the various formatting options Word provides, and alternatives often suggested by outsiders, like Markdown, don't come close to offering even 5% of the various formatting features lawyers and other writers of legal documents require. By the time you add all those features back to Markdown, you've recreated Word, but infinitely worse and more obtuse. Also, and this is entirely my personal opinion, Markdown sucks. Second, and this one you've surely heard before: Word's .docx format is effectively a network protocol. Everyone in the legal profession uses it, can read it, work with it, mark it up, apply corrections, and so on - from judges to lawyers to clients. If you try to work with, say, Google Docs, instead, you create a ton of friction in every interaction you have with other people in the legal profession. I vividly remember this from my 15 years as a translator - every single document you ever worked with was a Microsoft Office document. Sure, the translation agency standing between the end client and the translator might have abstracted the document into a computer-aided translation tool like Trados, but you're still working with .docx, and the translated document sent to the client is still .docx, and needs to look identical to the source, just in a different language. In the technology world, there's a lot of people who come barging into some other profession or field, claiming to know everything, and suggest to just do x", without any deference to how said profession or field actually operates. Just use Markdown and git" even if the people involved have no clue what a markup language even is let alone what git is; just use LibreOffice" even if the people involved will skewer you for altering the formatting of a document even ever so slightly; we all know examples of this. An industry tends to work a certain way not because they're stupid or haven't seen the light - it tends to work that way because there's a thousand little reasons you're not aware of that make that way the best way.

In 1979, VisiCalc was released for the Apple II, and to this day, many consider it the very first spreadsheet program. Considering just how important spreadsheets have become since then - Excel rules the world - the first spreadsheet program is definitely an interesting topic to dive into. It turns out that while VisiCalc was the first spreadsheet program for home computers, it's not actually the first spreadsheet program, period. That honour goes to LANPAR, created ten years before VisiCalc. Ten years before VisiCalc, two engineers at Bell Canada came up with a pretty neat idea. At the time, organizational budgets were created using a program that ran on a mainframe system. If a manager wanted to make a change to the budget model, that might take programmers months to create an updated version. Rene Pardo and Remy Landau discussed the problem and asked what if the managers could make their own budget forms as they would normally write them?" And with that, a new idea was created: the spreadsheet program. The new spreadsheet was called LANPAR, for LANguage for Programming Arrays at Random" (but really it was a mash-up of their last names: LANdau and PARdo). Jim Hall at Technically We Write While there wasn't a graphical user interface on the screen with a grid and icons and everything else we associate with a spreadsheet today, it was still very much a spreadsheet. Individual cells were delinianated with semicolons, you could write down formulas to manipulate these cells, and the program could do forward referencing. The idea was to make it so easy to use, managers at Dell Canada could make budgeting changes overnight, instead of having programmers take weeks or months to do so. I'm not particularly well-versed in Excel and spreadsheets in general, but I can definitely imagine advanced users no longer really seeing the grids and numbers as individual entities, instead visualising everything much more closely to what LANPAR did. Like Neo when he finally peers through the Matrix.

Jamie Zawinski, one of the founders of Netscape and later Mozilla, has dug up the original versions of the iconic Mozilla dinosaur logos, and posted them online in all their glory. While he strongly believes Mozilla owned these logos outright, and that they were released as open source in 1998 or 1999, he can't technically prove that. It has come to my attention that the artwork for the original mozilla.org dinosaur" logo is not widely available online. So, here it is. As I explained in some detail in my 2016 article They Live and the secret history of the Mozilla logo", I commissioned this artwork from Shepard Fairey to use as the branding of the newly-founded mozilla.org and our open source release of the Netscape source code, which eventually became Firefox. This happened in March 1998. Jamie Zawinski The original Mozilla dinosaur logos are works of pure art. They sure don't make logos like this anymore.

Mark Weiser has written a really interesting article about just how desirable new computing environments, like VR, AI" agents, and so on, really are. On the topic of AI" agents, he writes: Take intelligent agents. The idea, as near as I can tell, is that the ideal computer should be like a human being, only more obedient. Anything so insidiously appealing should immediately give pause. Why should a computer be anything like a human being? Are airplanes like birds, typewriters like pens, alphabets like mouths, cars like horses? Are human interactions so free of trouble, misunderstandings, and ambiguity that they represent a desirable computer interface goal? Further, it takes a lot of time and attention to build and maintain a smoothly running team of people, even a pair of people. A computer that I must talk to, give commands to, or have a relationship with (much less be intimate with), is a computer that is too much the center of attention. Mark Weiser That's one hell of a laser-focused takedown of AI" tools in modern computing. When it comes to voice input, he argues that it's too intrusive, too attention-grabbing, and a good tool is supposed to be the exact opposite of that. Voice input, especially when there's other people around, puts the interface at the center of everyones attention, and that's not what you should want. With regards to virtual reality, he notes that it replaces your entire perception with nothing but interface, all around you, making it as much the center of attention as it could be. What's most fascinating about this article and its focus on AI" agents, virtual reality, and more, is that it was published in January 1994. All the same questions, worries, and problems in computing we deal with today, were just as much topics of debate over thirty years ago. It's remarkable how you could copy and paste many of the paragraphs written by Weiser in 1994 into the modern day, and they'd be just applicable now as they were then. I bet many of you had no idea the quoted paragraph was over thirty years old. Mark Weiser was a visionary computer scientist, and had a long career at Xerox PARC, eventually landing him the role of Chief Technology Officer at PARC in 1996. He coined the term ubiquitous computing" in 1988, the idea that computers are everywhere, in the form of wearables, handhelds, and larger displays - very prescient for 1988. He argued that computers should be unobtrusive, get out of your way, help you get things done that aren't managing and shepherding the computer itself, and most of all, that computers should make users feel calm. Sadly, he passed away in 1999, at the age of 46, clearly way too early for someone with such astonishing forward-looking insight into computing. Looking at what computers have become today, and what kinds of interfaces the major technology companies are trying to shove down our throats, we clearly strayed far from Weiser's vision. Modern computers and interfaces are the exact opposite of unobtrusive and calming, and often hinder the things you're trying to get done more than they should. I wonder what Weiser would think about computing in 2025.

In recent years, things have not been going well for Mozilla. Firefox's market share is a rounding error, and financially, the company is effectively entirely dependent on free money from Google for making it the default search engine in Firefox. Mozilla's tried to stem the bleeding with deeply unpopular efforts like focusing on online advertising and cramming more and more AI" into Firefox, but so far, nothing has worked, and more and more of the remaining small group of Firefox users are moving to modded versions of Firefox without the AI" nonsense and other anti-features. The task of turning the tide is now up to Mozilla's new CEO, Anthony Enzor-DeMeo, who took up the role starting today. In his first message to the public in his new role as CEO of Mozilla, he lays out his vision for the future of the company. What are his plans for Mozilla's most important product, the Firefox web browser? Firefox will grow from a browser into a broader ecosystem of trusted software. Firefox will remain our anchor. It will evolve into a modern AI browser and support a portfolio of new and trusted software additions. Anthony Enzor-DeMeo So far, the AI" additions to Firefox have not exactly been met with thunderous applause - to put it mildly - and I don't see how increasing these efforts is going to magically turn that sentiment around. I'd hazard a guess that Firefox users, in particular, are probably quite averse to AI" and what it stands for, further strengthening the feeling that the people leading Mozilla seem a little bit out of touch with their own users. Add to this the obvious fact that AI" is a bubble waiting to pop, and I'm left wondering how investing in AI" now is going to do anything but make Mozilla waste even more money. I don't want Firefox to fail, as it is currently the only browser that isn't Chrome, Chrome in a trench coat, or Safari, but it seems Mozilla is trying to do everything to chase away what few users Firefox had left. In the short term, we can at least use modified versions of Firefox that have the AI" nonsense and other anti-features removed, but for the long term, we're going to need something else if Mozilla keeps going down the same path it's been going in recent years. The only viable long-term alternative is Servo, but that's still a long way off from being a usable day-to-day browser. The browser landscape ain't looking so hot, and this new Mozilla CEO is not making me feel any better.

Back in 2017 I wrote about a technique for creating closures in C using JIT-compiled wrapper. It's neat, though rarely necessary in real programs, so I don't think about it often. I applied it to qsort, which sadly accepts no context pointer. More practical would be working around insufficient custom allocator interfaces, to create allocation functions at run-time bound to a particular allocation region. I've learned a lot since I last wrote about this subject, and a recent article had me thinking about it again, and how I could do better than before. In this article I will enhance Win32 window procedure callbacks with a fifth argument, allowing us to more directly pass extra context. I'm using w64devkit on x64, but the everything here should work out-of-the-box with any x64 toolchain that speaks GNU assembly. Chris Wellons Sometimes, people get upset when I mention something is out of my wheelhouse, so just for those people, here's an article well outside of my wheelhouse. I choose honesty over faking confidence.

Any computing device will inevitably get a custom operating system - whether based on an existing operating system or something entirely custom - and of course, Kobo e-readers are no exception. QuillOS is an Alpine Linux-based distribution specifically developed for the unique challenges of e-readers, and comes with a custom Qt-based user interface, support for a whole slew of e-book formats, NetSurf as a web browser, encrypted storage, a VNC viewer, and a ton more. Basic hardware capabilities like Wi-Fi and power management are also supported, and it has online update support, too. The current release is already two years old, sadly, so I'm not sure how active the project is at this point. I wanted to highlight it here since something like this is a great way to liberate your Kobo device if, for some reason, Kobo ever started making their devices worse through updates, or the company shutters its services. You know, something that seems rather relevant today. Sadly, my own Kobo does not seem to be supported.

There's a new Haiku monthly activity report, and this one's a true doozy. Let's start with the biggest news. The most notable development in November was the introduction of a port of the Go programming language, version 1.18. This is still a few years old (from 2022; the current is Go 1.25), but it's far newer than the previous Go port to Haiku (1.4 from 2014); and unlike the previous port which was never in the package repositories, this one is now already available there (for x86_64 at least) and can be installed via pkgman. Haiku activity report As the project notes, they're still a few versions behind, but at least it's a lot more modern of an implementation than they had before. Now that it's in the repositories for Haiku, it might also attract more people to work on the port, potentially bringing even newer versions to the BeOS-inspired operating system. Welcome as it may be, this new Go port isn't the only big ticket item this month. Haiku can now gracefully recover from an app_server crash, something it used to be able to do a long time ago, but which was broken for a long time. The app_server is Haiku's display server and window manager, so the ability to restart it at runtime after a crash, and have it reconnect with still-running applications, is incredibly welcome. As far as I can tell, all modern operating systems can do this by now, so it's great to have this functionality restored in Haiku. Of course, aside from these two big improvements, there's the usual load of fixes and changes in applications, drivers, and other components of the operating system.

Alpine Linux maintainer Ariadne Conill has published a very interesting blog post about the shortcomings of both sudo and doas, and offers a potential different way of achieving the same goals as those tools. Systems built around identity-based access control tend to rely on ambient authority: policy is centralized and errors in the policy configuration or bugs in the policy engine can allow attackers to make full use of that ambient authority. In the case of a SUID binary like doas or sudo, that means an attacker can obtain root access in the event of a bug or misconfiguration. What if there was a better way? Instead of thinking about privilege escalation as becoming root for a moment, what if it meant being handed a narrowly scoped capability, one with just enough authority to perform a specific action and nothing more? Enter the object-capability model. Ariadne Conill To bring this approach to life, they created a tool called capsudo. Instead of temporarily changing your identity, capsudo can grant far more fine-grained capabilities that match the exact task you're trying to accomplish. As an example, Conill details mounting and unmounting - with capsudo, you can not only grant the ability for a user to mount and unmount whatever device, but also allow the user to only mount or unmount just one specific device. Another example given is how capsudo can be used to give a service account user to only those resources the account needs to perform its tasks. Of course, Conill explains all of this way better than I ever could, with actual example commands and more details. Conill happens to be the same person who created Wayback, illustrating that they have a tendency to look at problems in a unique and interesting way. I'm not smart enough to determine if this approach makes sense compared to sudo or doas, but the way it's described it does feel like a superior, more secure solution.

Unix has been enormously successful over the past 55 years. It started out as a small experiment to develop a time-sharing system (i.e., a multi-user operating system) at AT&T Bell Labs. The goal was to take a few core principles to their logical conclusion. The OS bundled many small tools that were easy to combine, as it was illustrated by a famous exchange between Donald Knuth and Douglas McIlroy in 1986. Today, Unix lives on mostly as a spiritual predecessor to Linux, Net/Free/OpenBSD, macOS, and arguably, ChromeOS and Android. Usenet tells us about the height of its early popularity. Gabor Nyeki There are so many amazing stories in this article, I honestly have no idea what to highlight. So first and foremost, I want you to read the whole thing yourself, as everyone's bound to have their own personal favourite section that resonates the most. My personal favourite story from the article - which is just an aside, to illustrate that even the asides are great - is that when Australia joined Usenet in 1983, new posts to Usenet were delivered to the country by airmail. On magnetic tape. Once per week. The overarching theme here is that the early days of UNIX, as documented on Usenet, were a fascinating wild west of implementations, hacks, and personalities, which, yes, clashed with each other, but also spread untold amounts of information, knowledge, and experience to every corner of the world. I hope Nyeki will write more of these articles.

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.

IBM owns Red Hat which in turn runs Fedora, the popular desktop Linux distribution. Sadly, shit rolls downhill, so we're starting to see some worrying signs that Fedora is going to be used a means to push AI". Case in point, this article in the Fedora Magazine: Generative AI systems are changing the way people interact with computers. MCP (model context protocol) is a way that enables generate AI systems to run commands and use tools to enable live, conversational interaction with systems. Using the new linux-mcp-server, let's walk through how you can talk with your Fedora system for understanding your system and getting help troubleshooting it! Mairin Duffy and Brian Smith at Fedora Magazine This linux-mcp-server" tool is developed by IBM's Red Hat, and of course, IBM has a vested interest in further increasing the size of the AI" bubble. As such, it makes sense from their perspective to start pushing AI" services and tools all the way down to the Fedora community, ending up with articles like this one. What's sad is that even in this article, which surely uses the best possible examples, it's hard to see how any of it could possibly be any faster than doing the example tasks without the help" of an AI". In the first example, the AI" is supposed to figure out why the computer is having Wi-Fi connection issues, and while it does figure that out, the solutions it presents are really dumb and utterly wrong. Most notably, even though this is an article about running these tools on a Fedora system, written for Fedora Magazine, the AI" stubbornly insists on using apt for every solution, which is a basic, stupid mistake that doesn't exactly instill confidence in any of its other findings being accurate. The second example involves asking the AI" to explain how much disk space the system is using, and why. The prompt" (the human-created question" the AI" is supposed to answer") is bonkers long - it's a 117 words long monstrosity, formatted into several individual questions - and the output is so verbose and it takes such a scattershot approach that following-up on everything is going to take a huge amount of time. Within that same time frame, it would've been not only much faster, but also much more user-friendly to just open Filelight (installed by default as part of KDE), which creates a nice diagram which instantly shows you what is taking up space, and why. The third example is about creating an update readiness report for upgrading from Fedora 42 to Fedora 43, and its prompt" is even longer at 190 words, and writing that up with all those individual questions must've taken more time than to just... Do a simple dry-run of a dnf system upgrade which gets you like 90% of the way there. Here, too, the AI" blurts out so much information, much of which entirely useless, that going through it all takes more time than just manually checking up on a dnf dry run and peaking at your disk space usage. All this effort to set all of this up, and so much effort to carefully craft complex prompts", only to end up with clearly wrong information, and way too much superfluous information that just ends up distracting you from the task you set out to accmplish. Is this really the kind of future of computing we're supposed to be rooting for? Is this the kind of stuff Fedora's new AI" policy is supposed to enable? If so, I'm afraid the disconnect between Fedora's leadership and whatever its users actually use Fedora for is far, far wider than I imagined.

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

If you're old enough, you no doubt remember that up until the 2.6.0 release of the Linux kernel, an odd number after the first version number indicated a pre-release, development version of the kernel. Even though this scheme was abandoned with the 2.6.0 release in 2003 and since then every single release has been a stable release, it seems the ghosts of this old versioning scheme still roam the halls, because prominent Linux kernel developer Greg Kroah-Hartman just published an explainer about Linux kernel versions. Despite having a stable release model and cadence since December 2003, Linux kernel version numbers seem to baffle and confuse those that run across them, causing numerous groups to mistakenly make versioning statements that are flat out false. So let's go into how this all works in detail. Greg Kroah-Hartman I genuinely find it difficult to imagine what could possibly be unclear about Linux kernel version numbers. The Linux kernel uses a very generic major.minor scheme, but that's not where the problems lie - it's the actual development process of each of these numbered release that's a bit more complex. This is where we have to talk about things like the roughly 10-week release cycle, containing a 2-week merge window, as well as Torvalds handing off the stable branch to the stable kernel maintainers. The other oddity is when the major version number gets incremented - the first number in the version number. There's no real method to this, as Kroah-Hartman admits Torvalds increments this number whenever the remaining numbers get too high and unwieldy to deal with. Very practical, but it does mean that going from, say, 5.x to 6.x doesn't really imply there's any changes in there that are any bigger or more disruptive than when going from 6.8.x to 6.9.x or whatever. There's a few more important details in here, of course, like where LTS releases come from, but that's really it - nothing particularly groundbreaking or confusing.

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?

The end of an era, perhaps. Applets are officially, completely removed from Java 26, coming in March of 2026. This brings to an official end the era of applets, which began in 1996. However, for years it has been possible to build modern, interactive web pages in Java without needing applets or plugins. TeaVM provides fast, performant, and lightweight tooling to transpile Java to run natively in the browser. And for a full front-end toolkit with templates, routing, components, and more, Flavour lets you build your modern single-page app using 100% Java. Andrew Oliver As consumers, we don't really encounter Java that much anymore unless we play Minecraft, but that doesn't mean Java no longer has a place in this world. In fact, it still consistently ranks in the top three of most popular programming languages, so any tools to make using Java easier, both for programmers and users, are welcome.

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. 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.

Now this is a great initiative by the Haiku team: highlight a number of stale commits that've been without interaction for years, explain why they've stalled, and then hope renewed interest might grow (part 1 and part 2). Recently some discussions on the forum led to asking about the status of our Gerrit code review. There are a lot of changes there that have been inactive for several years, with no apparent interest from anyone. To be precise, there are currently 358 commits waiting for review (note that Gerrit, unlike Github and other popular code review tools, works on a commit-by-commit basis, so each commit from a multiple-commit change is counted separately). The oldest one has not seen any comments since 2018. Today, let's have a look at some of these changes and see why they are stalled. Hopefully it will inspire someone to pick up the work and help finishing them up. Pulkomandy at the Haiku website Browsing through the highlighted stalled commits, there's a few that seem quite interesting and relatively easy for a (new?) contributor to seek their teeth into. For instance, there's a stalled commit to remove GCC from Haiku images built with clang/llvm, which stalled mostly because there are still other issues when building Haiku with clang/llvm. For a more complex problem, there's the issue of how every menu in BeOS/Haiku is also a window, including its own thread, which means navigating deeply nested menus creates and destroys a lot of threads, that all need to be synchronised, too. If you want to get really ambitious, there's the stalled commit to add initial 64bit PowerPC support. There's more of these, of course, so if you have the skills and will to contribute to a project like Haiku, this might be a great place to start and get your feet wet. Now that these commits are back in the spotlight, there's sure to be team members and regular contributors lined up to lend an extra hand, as well.

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) likeDyalog 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.

Microsoft has lowered sales growth targets for its AI agent products after many salespeople missed their quotas in the fiscal year ending in June, according to areportWednesday from The Information. The adjustment is reportedly unusual for Microsoft, and it comes after the company missed a number of ambitious sales goals for its AI offerings. Benj Edwards at Ars Technica I'm sure this is fine and not a sign of anything at all.

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 aclean-roomhomebrew 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 thatBG3players exploit children? Are you aware thatQi2 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!

You may have noticed that due to AI" companies buying up all literally all the RAM in the world, prices for consumer RAM and SSDs have gone completely batshit insane. Well, it's only going to get worse, since Micron has announced it's going to exit the market for consumer RAM and is, therefore, retiring its Crucial brand. The reason? You know the reason. The AI-driven growth in the data center has led to a surge in demand for memory and storage. Micron has made the difficult decision to exit the Crucial consumer business in order to improve supply and support for our larger, strategic customers in faster-growing segments," said Sumit Sadana, EVP and Chief Business Officer at Micron Technology. Micron's press release First it was the crypto pyramid scheme, and now it's the AI" pyramid scheme. These MLMs for unimpressive white males who couldn't imagine themselves out of a wet paper bag are ruining not just the environment, software, and soon the world's economy when the bubble pops, but are now also making it extraordinarily expensive to buy some RAM or a bit of storage. Literally nothing good is coming from these techbro equivalents of Harlequin romance novels, and yet, we're forced to pretend they're the next coming of the railroads every time some guy who was voted most likely to die a middle manager at Albertsons in Casper, Wyoming, farts his idea out on a napkin. I am so tired.

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 beendiscovering problemsthat 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.

What if you have a Risc PC, but aside from RISC OS, you also want to run Linux? Well, then you have to jump through a lot of hoops, especially in 2025. Well, this was a mess. I don't know why Potato is so crashy when I install it. I don't know why the busybox binary in the Woody initrd is so broken. But I've got it installed, and now I can do circa-2004 UNIX things with a machine from 1994. Jonathan Pallant The journey is definitely the most rewarding experience here for us readers, but I'm fairly sure Pallant is just happy to have a working Linux installation on his Risc PC and wants to mostly forget about that journey. Still, reading about the Risc PC is very welcome, since it's one of those platforms you just don't hear about very often between everyone talking about classic Macs and Commodore 64s all the time.

OK I promised computers, so let's move to the Tek 4051 I got! Released in 1975, this was based on the 4010 series of terminals, but with a Motorola 6800 computer inside. This machine ran, like so many at the time, BASIC, but with extra subroutines for drawing and manipulating vector graphics. 8KB RAM was standard, but up to 32KB RAM could be installed. Extra software was installed via ROM modules in the back, for example to add DSP routines. Data could be saved on tape, and via RS232 and GBIP external devices could be attached! All in all, a pretty capable machine, especially in 1975. BASIC computers where getting common, but graphics was pretty new. According to Tektronix the 4051 was ideal for researches, analysts and physicians, and this could be yours for the low low price of 6 grand, or around $36.000 in 2025. I could not find sales figures, but it seems that this was a decently successful machine. Tektronix also made the 4052, with a faster CPU, and the 4054, a 19'' 4K resolution behemoth! Tektronix continued making workstations until the 90s but like almost all workstations of the era, x86/Linux eventually took over the entire workstation market. Rik te Winkel at Just another electronics blog Now that's a retro computer you don't see very often.

The FreeBSD team has released FreeBSD 15.0, and with it come several major changes, one of which you will surely want to know more about if you're a FreeBSD user. Since this change will eventually drastically change the way you use FreeBSD, we should get right into it. Up until now, a full, system-wide update for FreeBSD - as in, updating both the base operating system as well as any packages you have installed on top of it - would use two separate tools: freebsd-update and the pkg package manager. You used the former to update the base operating system, which was installed as file sets, and the latter to update everything you had installed on top of it in the form of packages. With FreeBSD 15.0, this is starting to change. Instead of using two separate tools, in 15.0 you can opt to deprecate freebsd-update and file sets, and rely entirely on pkg for updating both the base operating system as well as any packages you have installed, because with this new method, the base system moves from file sets to packages. When installing FreeBSD 15.0, the installer will ask you to choose between the old method, or the new pkg-only method. Packages (pkgbase / New Method): The base system is installed as a set of packages from the FreeBSD-base" repository. Systems installed this way are managed entirely using the pkg(8) tool. This method is used by default for all VM images and images published in public clouds. In FreeBSD 15.0, pkgbase is offered as a technology preview, but it is expected to become the standard method for managing base system installations and upgrades in future releases. FreeBSD 15.0 release announcement As the release announcement notes, the net method is optional in FreeBSD 15 and will remain optional during the entire 15.x release cycle, but the plan is to deprecate freebsd-update and file sets entirely in FreeBSD 16.0. If you have an existing installation you wish to convert to using pkgbase, there's a tool called pkgbasify to do just that. It's sponsored by the FreeBSD Foundation, so it's not some random script. Of course, there's way more in this release than just pkgbase. Of note is that the 32bit platforms i386, armv6, and 32-bit powerpc have been retired, but of course, 32bit code will continue to run on their 64bit counterparts. FreeBSD 15.0 also brings a native inotify implementation, a ton of improvements to the audio components, improved Intel Wi-Fi drivers, and so, so much more.

On its own, the title of this post is just a true piece of trivia, verifiable withthe built-insubsttool(among other methods). Here's an example creating the drive+:\as an alias for a directory atC:\foo: The+:\drive then works as normal (at least in cmd.exe, this will be discussed more later): However, understandingwhyit's true elucidates a lot about how Windows works under the hood, and turns up a few curious behaviors. Ryan Liptak Fascinating doesn't even begin to describe this article, but at the same time, it also makes me wonder at what point maintaining this drive letter charade becomes too burdensome, clunky, and complex. Internally, Windows NT does not use drive letters at all, but for the sake of backwards compatibility and to give the user what they expect, a whole set of abstractions has been crafted to create the illusion that modern versions of Windows still use the same basic drive letter conventions as DOS did 40 years ago. I wonder if we'll ever reach a point where Windows no longer uses drive letters, or if it's possible today to somehow remove or disable these abstractions entirely, and run Windows NT without drive letters, as Cutler surely intended. Vast swaths of Windows programs would surely curl up in fetal position and die, including many core components of the operating system itself - as this article demonstrates, very few parts of Windows can handle even something as mundane as a drive letter outside of A-Z - but it'd make for a great experiment. Someone with just the right set of Windows NT skills must've tried something like this at some point, either publicly or inside of Microsoft.

What do you do if you develop a lightweight browser that doesn't support JavaScript, but you once chose GitHub as the home for your code? You're now in the unenviable position that your own browser can no longer access your own online source repository because it requires JavaScript, which is both annoying and, well, a little awkward. The solution is, of course, obvious: you move somewhere else. That's exactly what the Dillo browser did. They set up a small VPS, opted for cgit as the git frontend for its performance and small size, and for the bug tracker, they created a brand new, very simple bug tracker. To avoid this problem, I created my own bug tracker software,buggy, which is a very simple C tool that parses plain Markdown files and creates a single HTML page for each bug. All bugs are stored in agit repositoryand a git hook regenerates the bug pages and the index on each new commit. As it is simply plain text, I can edit the bugs locally and only push them to the remote when I have Internet back, so it works nice offline. Also, as the output is just an static HTML site, I don't need to worry about having any vulnerabilities in my code, as it will only run at build time. Rodrigo Arias Mallo There's more considerations detailed in the article about Dillo's migration, and it can serve as inspiration for anyone else running a small open source project who wishes to leave GitHub behind. With GitHub's continuing to add more and more complexity and AI" to separate open source code from its licensing terms, we may see more and more projects giving GitHub the finger.

Landlock is a Linux API that lets applications explicitly declare which resources they are allowed to access. Its philosophy is similar to OpenBSD'sunveil()and (less so)pledge(): programs can make a contract with the kernel stating, I only need these files or resources - deny me everything else if I'm compromised." It provides a simple, developer-friendly way to add defense-in-depth to applications. Compared to traditional Linux security mechanisms, Landlock is vastly easier to understand and integrate. This post is meant to be an accessible introduction, and hopefully persuade you to give Landlock a try. prizrak.me blog I had no idea this existed, even though it seems to plug a hole in the security and sandboxing landscape on Linux by not requiring any privileges and by being relatively simple and straightforward to use. There's even an additional supervisor" proposal that would bring Android-like permissions not just to, say, desktop applications (see Flatpak), but to every process trying to access anything for the first time. I'm not knowledgeable enough to make any statements about Landlock compared to any other options we have for securing desktop Linux in a user-friendly, non-intrusive manner, but I definitely like its simplicity.

Only a few weeks ago, the CHRP variants of Mac OS 7.6 and 8 were discovered and uploaded to the internet for posterity, but we're already seeing the positive results of this event unfold: Mac OS 7.x can now run on the Mac Mini G4 - natively. The very short of it is as follows. First, the CHRP release of Mac OS 8 contains a ROM file that allows Mac OS 8 to boot on the G4 Mac Mini. Second, the CHRP release of 7.6 contains a System Enabler that allows 7.6 earlier versions to run by using the aforementioned ROM file. Third, the ROM has been modified to add compatibility with as many Mac models as possible. There's a lot more to it, of course, but the end result is that quite a few more older, pre-9.x versions of Mac OS can now run on G4 and G3 Macs, which is quite cool. Of course, there are limitations. Note that, although I describe many of these as stable", I mean you can use much of it normally (sound/video/networking aside) without it crashing or misbehaving, at least not too hard, but that is not to say everything works, because that is just not the case. For example, when present, avoid opening the Apple System Profiler, unless you want a massive crash as it struggles trying to profile and gather all the information about your system. Some other apps or Control Panels might either not work, or work up to a certain point, after which they might freeze, requiring you to Force Quit the Finder to keep on going. And so on. Jubadub at Mac OS 9 Lives Issues or no, this is amazing news, and great work by all involved.

The release 25.11 wraps up our year of rigidity, clarity, performance" with a bouquet of vast under-the-hood improvements. Genode's custom kernel received special tuning of its new CPU scheduler for Sculpt-OS workloads, and became much more scalable with respect to virtual-memory management. Combined, those efforts visibly boost the performance of Sculpt OS on performance-starved hardware like the PinePhone or the i.MX8-based MNT Reform laptop. On account of improving clarity, our new configuration format - now named human-inclined data (HID) - proliferates throughout Genode's tooling. We are also happy to report that almost all Genode components have become interoperable with both XML and HID by now. Genode OS Framework 25.11 release notes The Genode Framework 25.11 also brings a major change to how important shared components that aren't strictly part of the framework are handled, such as ports like libSDL, sqlite, or gnutls. Before, these could only be built with the Genode build system, which was suboptimal because this isn't designed for building individual components. Several changes have been made to now enable the use of multiple build systems and the Goa SDK, which should make it a lot easier to these crucial components to become the responsibility of wider parts of the community. There's way more, of course, such as the usual driver improvements, including the addition of support for serial-to-USB adapters.

During a Dell earnings call, the company mentioned some staggering numbers regarding the amount of PCs that will not or cannot be upgraded to Windows 11. We have about 500 million of them capable of running Windows 11 that haven't been upgraded," said Dell COO Jeffrey Clarke on aQ3 earnings callearlier this week, referring to the overall PC market, not just Dell's slice of machines. And we have another 500 million that are four years old that can't run Windows 11." He sees this as an opportunity to guide customers towards the latest Windows 11 machines and AI PCs, but warns that the PC market is going to be relatively flat next year. Tom Warren at The Verge The monumental scale of the Windows 10 install base that simply won't or cannot upgrade to Windows 11 is massive, and it's absolutely bonkers to me that we're mostly just letting them get away with leaving at least a billion users out in the cold when it comes to security updates and bug fixes. The US government (in better times) and the EU should've 100% forced Microsoft's hand, as leaving this many people on outdated, unsupported operating system installations is several disasters waiting to happen. Aside from the dangerous position Microsoft is forcing its Windows 10 users into, there's also the massive environmental and public health impact of huge swaths of machines, especially in enterprise environments, becoming obsolete overnight. Many of these will end up in landfills, often shipped to third-world countries so we in the west don't have to deal with our e-waste and its dangerous consequences directly. I can get fined for littering - rightfully so - but when a company like Microsoft makes sweeping decisions which cause untold amounts of dangerous chemicals to be dumped in countless locations all over the globe, governments shrug it off and move on. At least we will get some cheap eBay hardware out of it, I guess.