OSnews

It's only been in the last couple of years that I've begun to dig deep into the inner workings of how terminal emulators, and the applications that run inside of them, really work. I've learned that there is a lot of innovation and creative problem solving happening in this space, even though the underlying technology is over half a century old. I've also found that many people who use terminal based tools (including shells like Bash and editors like Vim) know very little about terminals themselves, or some of the modern features and capabilities they can support. In this article, we'll discuss some of the problems that terminal based applications have historically had to deal with (and what the modern solutions are) as well as some features that modern terminal emulators support that you may not be aware of. Gregory Anders I don't use the terminal much - usually just to update my systems - but on occasion I've had to really sit down and explore them more than usual, especially now that my workstation runs OpenBSD, and the depth and breadth of features, options, and clever tricks they possess is amazing. Over the past half century they've accumulated a lot of features along the way, and even though its unlikely to ever be for me, I can somewhat begin to appreciate why some people just tile a bunch of terminals on their screens and do all their computing that way. I grew up with MS-DOS and Windows 3.x and later, so I'm just too attached to my mouse and pretty icons to switch to a terminal lifestyle, but over the years I've seen some pretty amazing terminal applications, from Mastodon clients to complex mail applications and web browsers, and you can be sure none of them steal your data or show you ads. Maybe the terminal people are right after all.

Nearly 30 years after the launch of the Virtual Boy, not much is publicly known about how, exactly, Nintendo came to be interested in developing what would ultimately become its ill-fated console. Was Nintendo committed to VR as a future for video games and looking for technological solutions that made business sense? Or was the Virtual Boy primarily the result of Nintendo going off script" and seizing a unique, and possibly risky, opportunity that presented itself? The answer is probably a little bit of both. As it turns out, the Virtual Boy was not an anomaly in Nintendo's history with video game platforms. Rather, it was the result of a deliberate strategy that was consistent with Nintendo's way of doing things and informed by its lead creator Gunpei Yokoi's design philosophy. Benj Edwards and Jose Zagal at Ars Technica I've never used a Virtual Boy, and in fact, I've never even seen one in real life. It was mythical object when I was not even a teenager yet, something we read about in gaming magazines in The Netherlands. We didn't really know what it was or how it worked, and it wasn't until much later, in the early YouTube age, that I got to see what using one was actually like in the countless YouTube videos made about the device. It seems it caused quite a few headaches, was cumbersome to use, had very few games, and those that were sold ended up collecting dust pretty quickly. In that sense, it seems not a lot has changed over the past thirty years.

Winamp has announced that on 24 September 2024, the application's source code will be open to developers worldwide. Winamp will open up its code for the player used on Windows, enabling the entire community to participate in its development. This is an invitation to global collaboration, where developers worldwide can contribute their expertise, ideas, and passion to help this iconic software evolve. Winamp press release Nice, I guess, but twenty years to late to be of any relevance. At least it'll be great for software preservation. But what's up with the odd language used in the press release, and the weirdly specific date that's month from now? They really seem to want to avoid the term open source", which makes me think this is going to be one of those cases where they hope the community will work for them for free without actually using a real open source license. You know, those schemes that always - no exception - fail.

Ordinary modifiers are normally straightforward, in that they are additional keys that are held down as you type the main key. Control, Shift, and Alt all work this way (by default). However, some modifiers are sticky', where you tap their key once to turn them on and then tap their key again to turn them off. The obvious example of this is Caps Lock (unless you turn its effects off, remapping its physical key to be, say, another Ctrl key). Another example, one that many X users have historically wound up quietly cursing, is NumLock. Why people wind up cursing NumLock, and why I have a program to control its state, is because of how X programs (such as window managers) often do their key and mouse button bindings. Chris Siebenmann I always have an applet in my KDE panel that shows me if I have any sticky modifiers enabled without realising it. On some of my keyboards, this isn't always easily noticable, especially when you're focused on what's happening on your display. A little icon that only shows up when a sticky modifier is engaged solves this problem, as it immediately stands out in your peripheral vision.

With Qualcomm and Microsoft about to flood the market with devices using the new Snapdragon X Elite, those of us who don't want to use Windows felt a bit uneasy - what's Linux support going to look like for this new generation of ARM devices? Well, it seems Qualcomm's been busy, and they've published a blog post detailing their work on Linux support for the X Elite. It's been our priority not only to support Linux on our premium-tier SoCs, but to support it pronto. In fact, within one or two days of publicly announcing each generation of Snapdragon 8, we've posted the initial patchset for Linux kernel support. Snapdragon X Elite was no exception: we announced on October 23 of last year and posted the patchset the next day. That was the result of a lot of pre-announcement work to get everything up and running on Linux and Debian. Qualcomm's developer blog In the blog post, the company details exactly which X Elite features have already been merged into mainline with Linux 6.8 and 6.9, as well as which features will be merged into mainline in Linux 6.10 and 6.11, and to be quite frank - it's looking really solid, especially considering this is Qualcomm we're talking about. Over the coming six months, they're going to focus on getting end-to-end hardware video decoding working, including in Firefox and Chrome, as well as various CPU and GPU optimisations, adding the required firmware to the linux-firmware package, and providing access to easy installers. All in all, it's looking like the X Elite will be exceptionally well supported by Linux before the year's over. The blog post also details the boot path for Linux on the X Elite, and that, too, is looking good. It's using a standard UEFI boot process, and supports GRUB and systemd-boot out of the box. Linux boots up using devicetrees, though, and apparently, there's a known problem with using those that Qualcomm and the community are working on. We're working closely with upstream communities on an open problem with the UEFI-based BIOS while booting with devicetrees. The problem is that, when you have more than one devicetree blob (DTB) packed into the firmware package flashed on the device, there is no standard way of selecting a devicetree to pass on to the kernel. OEMs commonly put multiple DTBs into the firmware package so it will support devices with slightly different SKUs, so we're keen to solve this problem. Qualcomm's developer blog I am pleasantly surprised by the openness and straightforwardness Qualcomm is showing the Linux community here, and I really hope this is a sign of how the company will keep supporting its laptop and possibly desktop-oriented SoCs from here on out. It seems like next year we will finally be getting competitive ARM laptops that can run Linux in a fully supported fashion.

Google released Android 15 beta 2 today, and with it, they unveiled some more of the new features coming to Android later this year when the final release lands. Android 15 comes with something called a private space, an area with an extra layer of authentication where you can keep applications and data hidden away, such as banking applications or health data. It's effectively a separate user profile, and shows up as a separate area in the application drawer when unlocked. When locked, it disappears entirely from sight, share sheets, and so on. Another awesome new feature is Theft Detection Lock, which uses Google AI" to detect when a phone is snatched out of your hands by someone running, biking, or driving away, and instantly locks it. Theft like this is quite common in certain areas, and this seems like an excellent use of AI" (i.e., accelerometer data) to discourage thieves from trying this. There's also a bunch of smaller stuff, like custom vibration patterns per notification, giving applications partial access to only your most recent photos and videos, system-wide preferences for which gender you'd like to be addressed as in gendered languages (French gets this feature first), and a whole lot more. Developers also get a lot to play with here, from safer intents to something like ANGLE: Vulkan is Android's preferred interface to the GPU. Therefore, Android 15 includes ANGLE as an optional layer for running OpenGL ES on top of Vulkan. Moving to ANGLE will standardize the Android OpenGL implementation for improved compatibility, and, in some cases, improved performance. You can test out your OpenGL ES app stability and performance with ANGLE by enabling the developer option in Settings -> System -> Developer Options -> Experimental: Enable ANGLE on Android 15. Android developer blog You can install Android 15 beta 2 on a number f Pixel devices and devices from other OEMs starting today. I installed it on my Pixel 8 Pro, and after a few hours I haven't really noticed anything breaking, but that's really not enough time to make any meaningful observations. Google also detailed Wear OS 5. Later this year, battery life optimizations are coming to watches with Wear OS 5. For example, running an outdoor marathon will consume up to 20% less power when compared to watches with Wear OS 4. And your fitness apps will be able to help improve your performance with the option to support more data types like ground contact time, stride length and vertical oscillation. Android developer blog Wear OS 5 will also improve the Watch Face Format with more complications, which is very welcome, because the selection of complications is currently rather meager. Wear OS 5 will also ship later this year.

As expected earlier this year, Raspberry Pi is going public on the stock exchange in London. Back then, CEO Eben Upton said he did not expect the IPO to change how Raspberry Pi did things, but history tells us that initial public offerings tend to, well, change how companies do things. In their official announcement that they intend to hold an IPO, there's an incredibly interesting and telling contradiction, as noted by @yassie_j on MastoAkkoma: Raspberry Pi, in their listing press release, says: The Enthusiast and Education market is the heart" of the Raspberry Pi movement. But also says: Industrial and Embedded market accounts over 72 per cent So the heart seems to be going neglected, it seems, because there's no way you're going to not cash in on industrial applications. Especially when you've just done a big IPO. @yassie_j on Akkoma This exactly illustrates the fears we all have about what an IPO is going to mean for Raspberry Pi. It's already become increasingly more difficult for enthusiasts to get their hands on the latest Raspberry Pi models, but once the IPO's done and there's shareholders breathing down their neck, that will most likely only get worse. If the industrial and embedded market is where you're making most of your money, where do you think Raspberry Pi devices are going to end up? Luckily the market's a lot bigger and more varied now than it was back when Raspberry Pi was new, so we have a wide variety of options to choose from. Still, I'm definitely worried about what Raspberry Pi, as a company, will look like five, ten years from now.

The NetBSD project seems to agree with me that code generated by AI" like Copilot is tainted, and cannot be used safely. The project's added a new guideline banning the use of code generated by such tools from being added to NetBSD unless explicitly permitted by core, NetBSD's equivalent, roughly, of technical management". Code generated by a large language model or similar technology, such as such as GitHub/Microsoft's Copilot, OpenAI's ChatGPT, or Facebook/Meta's Code Llama, is presumed to be tainted code, and must not be committed without prior written approval by core. NetBSD Commit Guidelines GitHub Copilot is copyright infringement and open source license violation at an industrial scale, and as I keep reiterating - the fact Microsoft is not training Copilot on its own closed-source code tells you all you need to know about what Microsoft thinks about the legality of Copilot.

I'm pretty sure most of you are familiar with KDE Neon, the distribution KDE maintains to provide easy access to the latest KDE technologies. However, did you know GNOME has something similar, called GNOME OS? It's been around for a while, but has a far lower profile than KDE Neon does, and it seems they want to change that and put more of a spotlight on GNOME OS. GNOME OS is an immutable distribution using OSTree, the same technology used by the various popular immutable versions from the Fedora family. It seems GNOME OS is working to leave OSTree behind, and move to systemd-sysupdate instead, which has been available since systemd 251, released in May 2022. The developers claim this will bring the following benefits: To complete the move from OSTree to systemd-sysupdate, a few things need to be completed. First, the boot process and root filesystem had to be migrated, which was done last year. Second, sysupdate needs to integrated into GNOME, as for now, you can only use it via the command line. This work is ongoing, and requires a new D-Bus service and polkit integration to allow GNOME Software to manage the update process. Of course, there's more work that needs to be done to complete this migration, but these are the main tasks. All of this work is part of the project's goal to make GNOME OS nightlies viable for daily-driving for quality assurance purposes, and I'm sure all this work will also make GNOME OS more attractive to people outside of the developer community. It's basically GNOME/systemd taken to the extreme, and while that will surely make quite a few people groan, I personally find it great that this will make GNOME OS a more capable choice for everyone. That's what open source is all about, in the end.

This is not a joke: Google will now let you perform a web" search. It's rolling out web" searches now, and in my early tests on desktop, it's looking like it could be an incredibly popular change to Google's search engine. The optional setting filters out almost all the other blocks of content that Google crams into a search results page, leaving you with links and text - and Google confirms to The Verge that it will block the company's new AI Overviews as well. Sean Hollister at The Verge I hate what the web has become.

A crucial but often entirely transparent feature of a modern package management system like Debian's APT is its solver - basically the set of rules and instruction on how to handle dependencies when installing a package. APT is currently in the process of radically changing its solver, the first bits of which can be found in APT 2.9.3, referred to as solver3. Many of the changes and improvements get a little into the weeds and will mostly be transparent to users, but there is one feature the new solver will enable that many of you will be incredibly excited about. One of the core new capabilities of solver3 is the implication graph. As part of the solving phase, we also construct an implication graph, albeit a partial one: The first package installing another package is marked as the reason (A -> B), the same thing for conflicts (not A -> not B). Julian Andres Klode Seems rather innocuous at first sight, but here's what the implication graph will make possible: The implication graph building allows us to implement an apt why command, that while not as nicely detailed as aptitude, at least tells you the exact reason why a package is installed. It will only show the strongest dependency chain at first of course, since that is what we record. Julian Andres Klode If you've ever dealt with packaging issues - probably when running -testing or similar unstable distributions that use APT, a command that tells you exactly why a package is installed is an absolute godsend. Sure, aptitude exists, but aptitude takes you out of your current CLI workflow, whereas this will be much easier to quickly run. There's more features solver3 will enable, but this one is definitely one of my favourite low-level additions to APT in a long, long time.

Google I/O, the company's developer conference, started today, but for the first time since I can remember, Android and Chrome OS have been relegated to day two of the conference. The first day was all about AI", most of which I'm not even remotely interested in, except of course where it related to Google's operating system offerings. And the company did have a few things to say about AI" on Android, and the general gist is that yeah, they're going to be stuffing it into every corner of the operating system. Google's AI" tool Gemini will be integrated deeply into Android, and you'll be able to call up an overlay wherever you are in the operating system, and do things like summarise a PDF that's on screen, summarise a YouTube video, generate images on the fly and drop them into emails and conversations, and so on. A more interesting and helpful AI" addition is using it to improve TalkBack, so that people with impaired vision can let the device describe images on the screen for them. Google claims TalkBack users come across about 90 images without description every day (!), so this is a massive improvement for people with impaired vision, and a genuinely helpful and worthwhile AI" feature. Creepier is that Google's AI" will also be able to listen along with your phone calls, and warn you if an ongoing conversation is a scamming attempt. If the person on the other end of the line claiming to be your bank asks you to move a bunch of money around to keep it safe, Gemini will pop up and warn you it's a scam, since banks don't ask you such things. Clever, sure, but also absolutely terrifying and definitely not something I'll be turning on. Google claims all of these features take place on-device, so privacy should be respected, but I'm always a bit unsure about such things staying that way in the future. Regardless, AI" is coming to Android in a big way, but I'm just here wondering how much of it I'll be able to turn off.

After Broadcom acquired VMware, there's been a steady stream of worrying or outright bad news for people using VMware products at home, for personal use, as enthusiasts. The biggest blow to the enthusiast market was the end of perpetual licensing, forcing people into subscriptions instead. Finally, though it seems we're getting some good news. The most exciting part is that Fusion Pro and Workstation Pro will now have two license models. We now provide a Free Personal Use or a Paid Commercial Use subscription for our Pro apps. Users will decide based on their use case whether a commercial subscription is required. This means that everyday users who want a virtual lab on their Mac, Windows or Linux computer can do so for free simply by registering and downloading the bits from the new download portal located at support.broadcom.com. Michael Roy on the VMware blog This is definitely good news for us enthusiasts, and it means I won't have to buy a cheap VMware license off eBay every few years anymore, so I'm quite satisfied here. However, with VMware under Broadcom focusing more and more on the enterprise and squeezing every last penny out of those customers, one has to wonder if this free for personal use' is just a prelude to winding down the development of enthusiasts' tools altogether. It wouldn't be the first time that a product going free for personal use was a harbinger of worse things yet to come.

Now that Android - since version 13 - ships with the Android Virtualisation Framework, Google can start doing interesting things with it. It turns out the first interesting thing Google wants do with it is run Chrome OS inside of it. Even though AVF was initially designed around running small workloads in a highly stripped-down build of Android loaded in an isolated virtual machine, there's technically no reason it can't be used to run other operating systems. As a matter of fact, this was demonstrated already when developer Danny Lin got Windows 11 running on an Android phone back in 2022. Google itself never officially provided support for running anything other than its custom build of Android called microdroid" in AVF, but that's no longer the case. The company has started to offer official support for running Chromium OS, the open-source version of Chrome OS, on Android phones through AVF, and it has even been privately demoing this to other companies. At a privately held event, Google recently demonstrated a special build of Chromium OS - code-named ferrochrome" - running in a virtual machine on a Pixel 8. However, Chromium OS wasn't shown running on the phone's screen itself. Rather, it was projected to an external display, which is possible because Google recently enabled display output on its Pixel 8 series. Time will tell if Google is thinking of positioning Chrome OS as a platform for its desktop mode ambitions and Samsung DeX rival. Mishaal Rahman at Android Authority It seems that Google is in the phase of exploring if there are any OEMs interested in allowing users to plug their Android phone into an external display and input devices and run Chrome OS on it. This sounds like an interesting approach to the longstanding dream of convergence - one device for all your computing needs - but at the same time, it feels quite convoluted to have your Android device emulate an entire Chrome OS installation. What a damning condemnation of Android as a platform that despite years of trying, Google just can't seem to make Android and its applications work in a desktop form factor. I've tried to shoehorn Android into a desktop workflow, and it's quite hard, despite third parties having made some interesting tools to help you along. It really seems Android just does not want to be anywhere else but on a mobile touch display.

As Nintendo Switch unlocks and homebrew software develops, people are inclined to explore the possibilities and whether or not they actually provide a good experience. Our new prime example seems to be a full install of Windows 11 Arm on the Switch. As noted by @PatRyk on Twitter, who actually set this up, the experience is pretty grueling! The initial installation took three hours, and even basic system tasks were unresponsive. Christopher Harper at Tom's Hardware Silly, sure, but efforts like these all contribute to emulation efforts, which will eventually be important once Nintendo drops support for this machine and they become increasingly harder to get. Give it a decade or so and we'll need the Switch emulators to keep playing Switch games.

Electronic Arts has a long, storied history of trying to wring more money out of gamers after they've purchased a game - now, it appears, the company's hard at work on its next generation of in-game ads. EA CEO Andrew Wilson admitted as much on the company's Q4 earnings call: when an analyst asked about the market opportunity for more dynamic ad insertion across more traditional AAA games," he said the company's already working on it. We have teams internally in the company right now looking at how do we do very thoughtful implementations inside of our game experiences," said Wilson. Sean Hollister at The Verge Ads in games are definitely not new - we've seen countless games built entirely around brands, like Tapper for Budweiser, Pepsiman, or Cool Spot for 7-Up - and banner ads and product placement in various games has been a thing for decades, too. It seems like EA wants to take this several steps further and use things like dynamic ad insertion in games, so that when you're playing some racing game, you'll get an ad for your local Hyundai dealer, or an ad for a gun store when you're playing GTA in the US. Either way, it's going to make games worse, which is perfectly in line with EA's mission.

Snikket is a FOSS project for creating private chat spaces for small groups, such as families, friends, or clubs. It doesn't depend on a phone number, doesn't upload address books anywhere, and doesn't sell data to advertisers. It supports all the features you expect, including media and voice messages, audio and video calls, end-to-end encryption, group messaging, and more. Use it from multiple devices at once with the official apps, or even with unofficial, third-party apps. Snikket is easy to self-host, and professional managed hosting is also available. Our previous sponsor, JMP, opted to donate a free week's sponsorship to Snikket, which any paying OSNews sponsor can opt to do. This is our very small way of giving something back to the countless open source and/or smaller projects out there. Thank you Snikket for sponsoring OSNews!

Each S1012 node has a single Power10 processor, which can have 1, 4, or 8 cores activated, which suggests that it is the same single chip module (SCM) implementation of the Power10 processor that was used in the Power S1022s entry machine. The Power S1012 node has four ISDIMM memory slots (using the differential signaling created by Big Blue for its Power10 memory) with a maximum capacity of 256 GB. The node has four half-height, half-length PCI-Express 5.0 slots and room for four NVM-Express U.2 drive bays that come in a maximum 1.6 TB capacity each for a total of 6.4 TB of storage. The eight-core version of the Power10 SCM is only available in the rack configuration, while the one-core and four-core versions are available in rack or tower configurations. The four-core and eight-core versions can run IBM i, AIX, or Linux, but the one-core version can only run IBM i and it has its main memory capped at the same 64 GB that other single-core Power Systems machines have been subjected to. We have suggested that 128 GB or even 256 GB is more appropriate given modern workloads, but Big Blue is standing its ground here. If you need more memory than 64 GB, then this machine is not for you. Timothy Prickett Morgan at IT Jungle I understand full well that these machines are by no means meant for people like you and I, sitting at home playing with our toys. That being said, I still wish there was some way for IBM to offer unique hardware like this - perhaps in a more standard, paired-down configuration - so more people than just enterprises could explore and use them. It wouldn't make any economic sense for IBM to do so, and even in a more standard, paired-down configuration they'd probably still be ungodly expensive, but when I look at this unique tower, with its POWER10 hardware and the ability to run AIX, desires are stirred within me that are banned in at least 46 countries. Such a machine would surely be wasted on someone like me, who would just be shoehorning whatever desktop tasks he could into it, but what a grand ol' time we would have. There is absolutely, positively, unequivocally zero percent chance IBM would ever send one of these over for review to someone like me, but I wonder if I should try anyway. I've got nothing to lose. Does anyone here work at IBM? Perhaps IBM wants to sponsor OSNews? How about like 12 weeks of free sponsorships in exchange for a tower model of the Power S1012? I also have two POWER9 machines to compare it to! It's the only way you'll ever get a Power S1012 screenfetch screenshot go viral on nerd social media, and we all know that deep down, that's all you IBM folks really want.

Apple has released the latest updates for virtually all of its actively supported devices today. Most include a couple handfuls of security updates, some new features for Apple News+ subscribers, and something called Cross-Platform Tracking Protection for Bluetooth devices. The iOS 17.5, iPadOS 17.5, macOS 4.5, watchOS 10.5, tvOS 17.5, and HomePod Software 17.5 updates are all available to download now. Andrew Cunningham at Ars Technica You know where to get them.

MacRelix is a Unix-like environment that runs in classic Mac OS. MacRelix natively supports classic 68K and PPC Mac OS, as well as Mac OS X on PPC via Carbon. MacRelix website The creator of MacRelix, Josh Juran, published an article in 2019 detailing the origins of the project. As a Mac OS developer, he was so unhappy with both CodeWarrior and Apple's Macintosh Programmer's Workshop (MPW), that he set out to create what would become MacRelix in 1999. Reading through the limitations and roadblocks he experienced with CodeWarrior and MPW, it's not hard to see why he got frustrated - CodeWarrior's targets were apparently a mess and a half to deal with. Then came target multiplication. Whereas the initial CodeWarrior developer releases shipped with each combination of language (C and Pascal) and architecture (68K and PPC) supported in a separate application, a later version of the IDE unified these, allowing the developer to have a single project file per project. To allow the same project to be built for both 68K and PPC architectures, the project data model included targets: One target would compile for 68K and link against 68K libraries, another would do the same for PPC. Targets could also be used to select an optimized build versus one for debugging. Combining both dichotomies yields four targets: 68K debug, 68K optimized, PPC debug, and PPC optimized. Then if your project involves multiple executables, like a code resource or shared library in addition to an application, you now have eight targets. Or, if you support one of, say, 68020 optimization, profiling, or a third executable, make that twelve. Or, for all of them, twenty-seven. Josh Juran Changing an option in your application required you to change it in every single target, too, which I can easily see is incredibly frustrating. MPW, for its part, was a massive improvement, he argues, but while it was clearly inspired by UNIX, it didn't seem to actually implement any of the features and characteristics of UNIX. However, very much unlike Unix, the MPW Shell had only a single thread of execution - only one program could be running at once. Not only that, but there was no way for MPW's compiled plugins (called tools) to invoke other tools or scripts - not even via system() (which blocks the calling program until the called program exits). Therefore, Make couldn't actually do anything, but only printed out the commands for the user to run manually. You could code in Perl instead of the built-in language, but then your scripts couldn't run other programs - only MPW shell scripts could do that. Josh Juran The limitations Juran was experiencing with these two tools pushed him to create his own solution, which went well beyond what MPW offered, even in 2019 when this article was published. Nowadays, MacRelix has pipes, signals, system calls, TCP sockets, and more. It works on both 68K and PowerPC Mac systems and builds as Carbon to run natively in OS X. It can be used on any Mac OS version from System 7 to Mac OS X 10.6 Snow Leopard" (after which Apple removed the Rosetta PowerPC emulator). I haven't implemented fork() yet, but I know how to do it. In addition to a Unix-like file system interface (which even handles long names by storing them in Desktop database comment fields)), MacRelix has a /proc filesystem (with human readable stack crawls) and also maps various parts of Mac OS (e.g. the ROM image in /sys/mac/rom). Josh Juran I had never heard of MacRelix, but it seems like an amazing tool Juran put a lot of thought, effort, and love into. Sadly, with the number of PowerPC Mac OS X users being vanishingly small, and the number of classic Mac OS users even smaller so, the future of MacRelix seems uncertain. I wonder what parts of it can be salvaged and upgraded to work on ARM macOS or even Intel macOS, because I think the ideas and concepts are incredibly cool. A related project by Juran is something called FORGE, a portable windowing API that used a virtual file system, meaning that instead of using functions as objects, it uses files. Juran mentions the example of a window title - which is a file, and if you want to change the title of that window you just change the file, which will be instantly reflected in the GUI. Here's a Hello World example: Even though I'm not a programmer, this little tidbit of code makes perfect sense to me, and I understood it instantly. Of course, anything more complex will quickly leave my wheelhouse, but intuitively, I really like this. FORGE exists as a prototype inside MacRelix, so you can play with this concept while using MacRelix.

This article is a partial-rebuttal/partial-confirmation to KGOnTech's Apple Vision Pro's Optics Blurrier & Lower Contrast than Meta Quest 3, prompted by RoadToVR's Quest 3 Has Higher Effective Resolution, So Why Does Everyone Think Vision Pro Looks Best? which cites KGOnTech. I suppose it's a bit late, but it's taken me a while to really get a good intuition for how visionOS renders frames, because there is a metric shitton of nuance and it's unfortunately very, very easy to make mistakes when trying to quantify things. This post is divided into two parts: Variable Rasterization Rate (VRR) and how visionOS renders frames (including hard numbers for internal render resolutions and such), and a testbench demonstrating why photographing the visual clarity of Vision Pro (and probably future eye tracked headsets) may be more difficult than a DSLR pointed into the lenses (and how to detect the pitfalls if you try!). Shiny Quagsire I did it. I think I managed to find an article that isn't just over my head, but also over most of your heads. How's that feel?

Window management in Emacs gets a bad rap. Some of this is deserved, but mostly this is a consequence of combining a very flexible and granular layout system with rather coarse controls. This leaves the door open to creating and using tools for handling windows that employ and provide better metaphors and affordances. As someone who's spent an unnecessary amount of time trying different approaches to window management in Emacs over the decades, I decided to summarize them here. Almanac might be overstating it a bit - this is a primer to and a collection of window management resources and tips. Karthik Chikmagalur I honestly had no idea Emacs was this... Advanced, complex, and feature-laden. I mean, I thought Emacs' complexity was just a meme, but reading this article it seems the memes don't do it justice.

Disassembly and enhancements for Apple II DeskTop (a.k.a. Mouse Desk), a Finder"-like GUI application for 8-bit Apples and clones with 128k of memory, utilizing double hi-res monochrome graphics (560*192), an optional mouse, and the ProDOS 8 operating system. Apple II DeskTop GitHub page The goal of this project is to reverse-engineer Apple II DeskTop, and fix bugs and enhance it in the process. I didn't actually know that the Apple IIgs initially shipped with this instead of the 16 bit GS/OS, which is the operating system I personally associate with the IIgs. Apple II DeskTop was largely 8 bit, and built on top of ProDOS 16, and didn't really take full advantage of the IIgs hardware. It wasn't until version 4.0 of the system software that the IIgs switched over to GS/OS. The latest release is v1.4-alpha9, released a few days ago. Apple II DeskTop is still entirely compatible with Apple II machines and clones from before the IIgs, as well, and it runs in emulators, too. We actually already covered this project a few years ago, but a reminder that this exists never hurt anyone.

If you remember a time when using floppy disks didn't seem weird, you're probably at least 30 years old. Floppy disks or diskettes emerged around 1970 and, for a good three decades or so, they were the main way many people stored and backed up their computer data. All the software and programmes they bought came loaded onto clusters of these disks. They are a technology from a different era of computing, but for various reasons floppy disks have an enduring appeal for some which mean they are from dead. Chris Baraniuk at the BBC Articles such as these in more mainstream media are always incredibly odd to me. Nobody bats an eye at someone lovingly maintaining a classic car, or restoring an old house, or a group of people petitioning a local government to not demolish a beloved old building or whatever, but as soon as computer technology is involved, so many people find it incredibly weird that classic computer technology, too, can be worth saving. It highlights how society views technology - disposable, replaceable, worthless, to be dumped and forgotten about as soon as something newer comes along. Even after at least two decades of articles like this, they keep being essentially republished with the same words, the same storylines about these weird people who keep using - get this! Look at these idiots! - older technology when faster, newer, shinier stuff is readily available. I'm glad the retrocomputing community seems to be growing by the day, and there's now definitely a large enough internationally connected group of people and organisations to maintain our old computers and related hardware and software.

Starting in the release 560 series, it will be recommended to use the open flavor of NVIDIA Linux Kernel Modules 119 wherever possible (Turing or later GPUs, or Ada or later when using GPU virtualization). NVIDIA developer forums Slowly but surely, NVIDIA is taking a more favourable position towards open source. It still feels surreal.

So I got accepted into GSoC again! I'm going to be working on WebKit2. But what is WebKit2, or even WebKit, for that matter? Well, WebPositive uses WebKit to render its web pages. Currently, we use the WebKitLegacy API to communicate with WebKit. It would be nice to switch to the newer version: WebKit2. However, our port of WebKit2 still needs work. At present, it has lost its ability to even render any webpage at all! So, getting WebKit2 to work will be the primary goal of my GSoC project. If there's time left, I might be able to integrate it into WebPositive. The advantages WebKit2 has for WebPositive will be mostly invisible to end-users. The code will hopefully be more maintainable than the deprecated WebKitLegacy and we'll get access to several newer APIs such as the ad-blocking API. Perhaps the most visible change: problems in one part of the code should be less likely to crash the whole browser. Zardshard on the Haiku website The current state of WebPositive, the only native Haiku web browser, is emblematic of why I have personally lost all interest in the successor to what is still my favourite operating system of all time. Haiku OS supports several browsers, and if you read any forum post about which browser to use, or watch any of the enthusiastic Haiku videos by the insanely awesome Action Retro, they'll all advise you to use any of the non-native Qt or GTK browsers instead - because WebPositive just can't compete with the ported, non-native browsers. Since everybody using Haiku is opting to use the better ported browsers, WebPositive has fallen even more by the wayside; now it has to play catch-up, and by the time WebKit2 has been properly ported and bug-tested, and has been integrated into WebPositive, which then has to be bug-tested as well, we're going to be months, if not years, down the line. In the meantime, the ported browsers will have been regularly updated with newer, better versions. Unless the focus for the single most important application of any general purpose desktop operating system is placed solely on WebPositive, it simply won't be able to keep up with the ported browsers. Why even work on WebPositive at all at that point? It's not like anyone is using it, so why bother? And this highlights a problem for people like me, who prefer to have native Haiku applications instead of ports of software I can already run elsewhere. As a former BeOS user, I am not interested in a vessel for running Qt applications that I can, in all likelihood, run better on Linux. Why would I go through the trouble of assembling a machine with hardware Haiku supports, only to then run the same applications I'm already running on Fedora or OpenBSD, but worse? If you browse through Haiku Depot today, it feels like the vast majority of modern, maintained, and working software are ports of Qt (and GTK) software we already know and love from other, more mature, more stable, more usable, and more feature-rich platforms. Haiku has chosen to pour a lot of energy and manpower into becoming an operating system designed to run ported, often Qt, applications, but the downside to that is that new and maintained native Haiku applications, that play to the strengths of the platform, are few and far between. A Haiku developer once told me that real people use Haiku every day, and they need real applications, and ported applications make it possible for not only Haiku developers themselves, but also normal users, to run and use Haiku every day. This is a valid argument that I fully understand and agree with - it just means Haiku isn't for me. And while that's sad for me, it's entirely fine. Haiku's developers have chosen to focus on building a daily-drivable operating system with tons of ported applications, instead of an ideologically pure operating system you can't really use because it only has like 4 native applications and nothing else. And that's a valid, smart, and practical choice that I fully respect and understand, even if it means Haiku isn't really a BeOS successor anymore.

As its first alpha release is closing in, we have another monthly update about COSMIC, System76's new Linux desktop environment written in Rust. This month, they've further polished and shored up their application store, imaginatively named COSMIC App Store, and it's supposedly incredibly fast - something I can't say for its GNOME and KDE counterparts, which tend to be so slow I've always just defaulted to updating through the command line, mostly. The file manager now has support for GVfs (GNOME Virtual file system) for making external storage like USB drives work properly, and Greeter login screen, Edit text editor, drag and drop, and copy/paste have been improved in various ways as well. Theming has seen a lot of work this month, with support for icon themes added to the App Library, fixed applet sizes, and more tweaks, while light themes have been disabled for now to fix a number of issues with colour selection being too dark. There's also display mirroring now, which even works when the individual displays have different resolutions, orientations, and refresh rates. Pop!_OS is now also being built for ARM64, which makes sense because System76 is now also selling ARM servers. There's also a bunch of work being done by the community as the alpha release nears.

X Server is slowly being deprecated in the Linux world and being replaced Wayland. Still X11 is an interesting protocol to look at from the perspective of binary communication and management of resource which require fast speeds. In this post I tried to cover basic information and create a simple but working app that is simple, defined in single file and easily compiles. No external code except libc was used. I find it fascinating when you can open black boxes and see how gears move each other. Hereket As much as the time of X has come and is now finally in the process of going, it's still an incredibly powerful set of tools that even in a bare state can do way, way more than you think. X has come with its own window manager - twm - for decades, and it includes several basic applications like xedit, xclock, xterm, xeyes. Twm is actually pretty cool, and includes some features, like iconify to desktop, that I wish still existed in modern desktop environments. It's quite bare-bones, though, and I doubt there's anyone out there unironically using it today. As the linked article notes, even without advanced, complex libraries, toolkits, desktop environments, and so on, it's entirely possible to create fully functional windows and applications with X. Of course, this makes perfect sense and shouldn't be surprising - it's the X Window System, after all - but you so rarely hear or read about it that you'd almost forget and just assume something like GNOME or KDE is an absolute requirement to use X.

We've been on the lookout for the arrival of the ChromeOS App Mall for a few months now. First discovered back in March, the new App Mall is arriving to do one, simple task: put the apps users want in one place to be found a Chromebook. While we have access to web apps, PWAs, Android apps and Linux apps on Chromebooks, it's not always clear how to go about finding them. Should you install the web version or the Play Store version? Which Play Store apps install a PWA versus an Android app? Where should you go to find the right one for you? Robby Payne at Chrome Unboxed ChromeOS definitely needs a more unified, single place to find applications, and this seems like exactly what's happening here.

Yuxuan Shui, the developer behind the X11 compositor picom (a fork of Compton) published a blog post detailing their experiences with using GitHub Copilot for a year. I had free access to GitHub Copilot for about a year, I used it, got used to it, and slowly started to take it for granted, until one day it was taken away. I had to re-adapt to a life without Copilot, but it also gave me a chance to look back at how I used Copilot, and reflect - had Copilot actually been helpful to me? Copilot definitely feels a little bit magical when it works. It's like it plucked code straight from my brain and put it on the screen for me to accept. Without it, I find myself getting grumpy a lot more often when I need to write boilerplate code - Ugh, Copilot would have done it for me!", and now I have to type it all out myself. That being said, the answer to my question above is a very definite no, I am more productive without it". Let me explain. Yuxuan Shui The two main reasons why Shui eventually realised Copilot was slowing them down were its unpredictability, and its slowness. It's very difficult to understand when, exactly, Copilot will get things right, which is not a great thing to have to deal with when you're writing code. They also found Copilot incredibly slow, with its suggestions often taking 2-3 seconds or longer to appear - much slower than the suggestions from the clangd language server they use. Of course, everybody's situation will be different, and I have a suspicion that if you're writing code in incredibly popular languages, say, Python or JavaScript, you're going to get more accurate and possibly faster suggestions from Copilot. As Shui notes, it probably also doesn't help that they're writing an independent X11 compositor, something very few people are doing, meaning Copilot hasn't been trained on it, which in turn means the tool probably has no clue what's going on when Shui is writing their code. As an aside, my opinion on GitHub Copilot is clear - it's quite possibly the largest case of copyright infringement in human history, and in its current incarnation it should not be allowed to continue to operate. As I wrote over a year ago: If Microsoft or whoever else wants to train a coding AI" or whatever, they should either be using code they own the copyright to, get explicit permission from the rightsholders for AI" training use (difficult for code from larger projects), or properly comply with the terms of the licenses and automatically add the terms and copyright notices during autocomplete and/or properly apply copyleft to the newly generated code. Anything else is a massive copyright violation and a direct assault on open source. Let me put it this way - the code to various versions of Windows has leaked numerous times. What if we train an AI" on that leaked code and let everyone use it? Do you honestly think Microsoft would not sue you into the stone age? Thom Holwerda It's curious that as far as I know, Copilot has not been trained on Microsoft's own closed-source code, say, to Windows or Office, while at the same time the company claims Copilot is not copyright infringement or a massive open source license violation machine. If what Copilot does is truly fair use, as Microsoft claims, why won't Microsoft use its own closed-source code for training? We all know the answer. Deeply questionable legality aside, do any of you use Copilot? Has it had any material impact on your programming work? Is its use allowed by your employer, or do you only use it for personal projects at home?

Today we're pleased to announce the beta release of Raspberry Pi Connect: a secure and easy-to-use way to access your Raspberry Pi remotely, from anywhere on the planet, using just a web browser. It's often extremely useful to be able to access your Raspberry Pi's desktop remotely. There are a number of technologies which can be used to do this, including VNC, and of course the X protocol itself. But they can be hard to configure, particularly when you are attempting to access a machine on a different local network; and of course with the transition to Wayland in Raspberry Pi OS Bookworm, classic X remote desktop support is no longer available. We wanted to be able to provide you with this functionality with our usual it just works" approach. Enter Raspberry Pi Connect. Gordon Hollingworth Pi Connect uses WebRTC, and a daemon running on your Pi listens for incoming screensharing requests from the Raspberry Pi website to connect the VNC server on your Pi to the VNC client running in your browser. The service is in beta, it's free, but the one major downside is that for now, there's only one TURN server for this service, located in the UK, but they might set up more of them if demand is high enough. If you want to try this service on your own Pi running Raspberry Pi OS, you're going to need to be using a Raspberry Pi 5, 4, or 400, using the latest version of the operating system running Wayland. Update your operating system, install the rpi-connect package, reboot, and you're good to go.

The U.S. has revoked licenses that allowed companies including Intel and Qualcomm to ship chips used for laptops and handsets to sanctioned Chinese telecoms equipment maker Huawei Technologies, three people familiar with the matter said. Alexandra Alper, Fanny Potkin, David Shepardson The timing of this news is very interesting, as despite the massive sanctions the United States levied against Huawei, the company seems to be doing really well, with its smartphone business seeing massive gains in the Chinese market, at the expense of everyone else. This proves that Huawei does not need access to western chips and technologies to be successful, which must definitely sting in the US and Europe. Strong financial results, using hardware and chips designed not by western companies but by Chinese ones, combined with the only mobile operating system that has any serious potential to at least somewhat threaten Android and iOS. The various sanctions were clearly intended to hurt Huawei and possibly contain it to just China, but it seems they're not having their desired effect at all.

NetBSD 10 and NetBSD 9.4 were only recently released, leaving one final branch to receive what will be its last update: NetBSD 8.3. NetBSD 8.0 was originally released in 2018, so this final release marks six years of updates, which is a good track record, especially now that two newer main releases are available to choose from. With 8.3 being the final release, this means no more regular or security updates, pkgsrc no longer supports the 8.0 branch either - so yeah, time to upgrade. NetBSD 8.3 brings various updates and bug fixes for libX11, xterm, tmux, and httpd, and the root name servers and time zone data have been updated to their latest iterations as well. There's of course a full list of changes to peruse through if you want to know every little detail that's changed. You can update your installation in-place, of course, or download the installation media for 8.3 from one of the many mirrors.

This is the story on how I spent far too much money and time getting a scanner to work over iSCSI so that I could prove Chris O" wrong on StackExchange. The TL;DR is that yes scanners work fine over iSCSI. xssfox The next step is connecting a bunch of flatbed scanners to a disk array enclosure, but that turns out to be quite an expensive little exercise. Regardless, this is absolutely wild, and I love it when people go to great lengths just to prove that something pointless can actually be done. Bravo.

Jolie crystallises the programming concepts of service-oriented computing as linguistic constructs. The basic building blocks of software are not objects or functions, but rather services that can be relocated and replicated as needed. A composition of services is a service. Jolie website Jolie is open source and available on GitHub.

But today we got our hands on LPCAMM2 for the first time, and this looks like the future to us. LPCAMM2 is a totally modular, repairable, upgradeable memory standard for laptops, using the latest LPDDR chips for maximum speed and efficiency. So instead of overpaying (or under-speccing) based on guesswork about your future memory needs, you'll hopefully be able to buy your next laptop and then install more RAM as needed. Imagine that! Carsten Frauenheim LPDDR memory, used in modern laptops, has been difficult - or impossible - to upgrade because its low power nature means it needs to be located as close to the processor as possible with short traces, since the longer the traces, the more power is needed to maintain signal integrity between the processor and RAM. This would defeat the entire purpose of low-power DDR memory to begin with. Originally developed by Dell and eventually adopted by JEDEC and the wider industry, LPCAMM2 solves this problem by using screw-down RAM modules located right next to the processor. These modules can, like regular memory modules, be replaced and upgraded when needed or desired. This is a great leap forward, and I really, really hope we're going to see quick, widespread adoption.

GCC 14.1 has been released, and it should come as no surprise that the new features are not exactly something I, someone who doesn't program, can properly parse. So, here's the three items GCC itself thought were important to list first. The C frontend when targeting standards newer than C89 now considers many non-standard constructs as errors that were previously only warnings. See https://gcc.gnu.org/gcc-14/porting_to.html#warnings-as-errors for more details. C23 _BitInt Bit-precise integer types are now supported, for now only on IA-32, x86-64 and AArch64. The C++ frontend now implements several C++26 features, some missing C++23 bits and defect report resolutions. Diagnostics involving C++ templates now quote source from the instantiation context. The libstdc++exp.a library now includes all symbols for the Filesystem TS and the experimental symbols for the C++23 std::stacktrace class, so -lstdc++exp can be used instead of -lstdc++fs. The libstdc++_libbacktrace.a library is not longer installed. Improved experimental support for C++20, C++23, and C++26. Updated parallel algorithms that are compatible with oneTBB. GCC 14.1 release announcement GCC 14.1 is available for download, of course, but most of us will get it once it hits our distribution's package repositories.

We're all aware of Stack Overflow - it's a place where programmers and regular users can ask technical questions, and get answers from anyone who thinks they know the answer. Stack Overflow has become so ubiquitous among programmers and developers, the concept of I just copied the code off Stack Overflow" has become a consistent meme to indicate you don't fully grasp how something works, but at least it works. If you've ever contributed answers to Stack Overflow, you might want to consider deleting them, altering them, or perhaps even go as far as request a GDPR removal if you're in the European Union, because Stack Overflow has just announced a close partnership with AI" company OpenAI (or, more accurately, Open" AI"). Stripped of marketing speak, the gist is exactly as you'd expect: OpenAI will absorb the questions and answers on Stack Overflow into its models, whether their respective authors like it or not. As much as you may want to try and delete your answers if you're not interesting in having your work generate profit for OpenAI, deleting popular questions and answers is not possible on Stack Overflow. The other option is altering your answers to render them useless, but it seems Stack Overflow is not going to allow you to do this, either. Ben Humphreys tried to alter his highest-rated answers, and Stack Overflow just reverted them back, and proceeded to ban him from the platform. Stack Overflow does not let you delete questions that have accepted answers and many upvotes because it would remove knowledge from the community. So instead I changed my highest-rated answers to a protest message. Within an hour mods had changed the questions back and suspended my account for 7 days. Ben Humphreys Now that they've made what is most likely an incredibly lucrative deal with OpenAI that's going to net Stack Overflow's owners boatloads of money, they obviously can't let users delete or alter their answers to lower the monetary value of Stack Overflow's content. Measures to prevent deletion or alteration are probably one of the clauses in the agreement between Stack Overflow and OpenAI. So there's likely not much you can do to not have your answers sucked into OpenAI, but you should at least be aware it's happening in case of future answers you might want to contribute.

I want to run GoToSocial on some *BSD system. Because I am who I am, I went for using NetBSD 10.0 . And because my hypervisor is running bhyve on OmniOS , you get the title of this blog post. Don't get too anxious, it is quite straightforward. So let the journey begin. Joel Carnat Bhyve is a hypervisor originating from FreeBSD, while OmniOS is a distribution of illumos, a continuation of the last open source Solaris release from Oracle. GoToSocial, meanwhile, is an ActivityPub social network server, so it belongs in the same family as Mastodon, Glitch, Akkoma, and countless others. This guide makes this whole process look like a piece of cake, so if you've ever been interested in running your own ActivityPub server - read on. On a slightly related sidenote, there's no OSNews AT instance, partly because I don't want to deal with the moderation and costs, and partly because I'm incredibly happy being a member of Exquisite, a Glitch instance running on OpenBSD, managed by OpenBSD enthusiasts. Never say never, of course, but the odds of seeing an OSNews AT instance in the future are very slim.

The grabber in Windows 3.1 was improved to save and restore the index register as well, but it does not attempt to restore the flip-flop state, which is significant. The problem with the VGA emulation was that it erroneously applied the flip-flop state to reads from port 3C0h, and Windows 3.1 would save the wrong index register value... but only the second time through, because the flip-flop state was different at that point. That is to say, the Windows 3.1 standard mode grabber read from port 3C0h to query the attribute controller index register state, but the emulation returned the currently selected data register contents instead. And then, when restoring the attribute controller index register the next time around, the register would be restored to the wrong value which didn't have bit 5 set, causing the screen to go blank. Michal Necasek It's not every day that you learn how an aspect of the workings of VGA causes a blank screen under very specific circumstances when running Windows 3.1 in Standard mode under emulation, and that this specific aspect of the workings of VGA was implemented to maintain backwards compatibility with EGA. Absolutely bonkers.

In addition to Linux 6.10 expected to drop support for very old DEC Alpha processors (EV5 and earlier), it looks like the PowerPC 40x (early PowerPC 400 series) processor and platform support will be retired too. Back in 2020 was a proposal for dropping PowerPC 40x support from the Linux kernel given that the code was orphaned for a long time with no apparent users. The PowerPC 40x processors were found in thin clients, set-top boxes, and other devices during the 90's. Finally now it looks like that the PowerPC 40x removal is set to happen. Michael Larabel Spring cleaning in the hardware support department. I wonder what has more users - Windows on ARM, or Linux on PowerPC 40x.

Windows 11 supports a variety of ARM processors from Qualcomm. According to the official documentation, you need a computer with the Snapdragon 850 processor inside or newer to run the current operating system officially. However, customers with PCs powered by the Snapdragon 835, the original Windows on ARM chip from 2016, can bypass hardware requirements and install Windows 11 at their own risk. Sadly, those days will be ending soon. Starting with Windows 11 version 24H2, Microsoft's operating system requires ARM v8.1 to run. An attempt to boot it from a device with an ARM v8.0-based processor results in system crashes. For reference, the Snapdragon 835 from 2016 is a chip with Kryo 280 cores, which are derivative of ARM's Cortex-A73 cores. Taras Buria at Neowin I'm sure all three Windows on ARM users are devastated.

Snikket is a FOSS project for creating private chat spaces for small groups, such as families, friends, or clubs. It doesn't depend on a phone number, doesn't upload address books anywhere, and doesn't sell data to advertisers. It supports all the features you expect, including media and voice messages, audio and video calls, end-to-end encryption, group messaging, and more. Use it from multiple devices at once with the official apps, or even with unofficial, third-party apps. Snikket is easy to self-host, and professional managed hosting is also available. Our previous sponsor, JMP, opted to donate a free week's sponsorship to Snikket, which any paying OSNews sponsor can opt to do. This is our very small way of giving something back to the countless open source and/or smaller projects out there. Thank you Snikket for sponsoring OSNews!

That's right: it's PowerPC, the most unloved of the architectures CE ever ran on - in fact, this is the first PowerPC Windows CE device I've ever found, and I'm the self-described biggest pro-PowerPC bigot in the world. Here's an unusual form factor Windows CE device, running on the operating system's least used CPU, from a storied computer company near the end of its run, intended for medical applications, produced in very small numbers and cancelled within months. What are we going to do with it? Well, what do you think we're gonna do with it? We're going to program it, so that we can finally have some software! And, of course, since this wacky thing was there at the bitter end, we'll talk more about the last days of Data General and what happened next. Cameron Kaiser I knew Windows CE supported PowerPC, but I never knew any PowerPC-based Windows CE devices ever actually shipped and made it to market. Only Windows CE 2.0 seems to have supported the architecture, and it seems to have been eliminated in 3.0 and 4.0, so it's not surprising there weren't many PowerPC Windows CE devices out there. The device that's the subject of this article, too, only lasted on the market for a few months, so it's definitely a rarity.

Still rocking your Palm OS device, but mutter under your breath every time you need to log into a website or service with two-factor authentication? Sick of carrying around an Android or iOS device just so you can log in on your Palm PDA? Worry no more, your prayers have been answered, you can finally throw that Android or iOS garbage into the sun. Get your 2-factor codes on your Palm, just like Google Authenticator. Unlike Hotpants (an old port of a J2ME phone app), this version takes up much less space and supports all Palm OS versions. Nathan Korth You can now generate 2FA codes on your Palm device. This is wild, and I absolutely love it. I might if set it up on one of my dozens of Palm OS devices and just put it next to my keyboard for easy access. There's no cooler way to handle 2FA than this.

We'd like to thank this past week's sponsor JMP for sponsoring OSNews. As a reminder, JMP is a fully FOSS service providing a way to get a real phone number that operates over the internet using XMPP. They provide numbers in the USA and Canada with everything you need to access SMS/MMS/etc. and voice calls using your XMPP (or SIP) clients of choice across all your devices. They are committed to growing the use of open communications technology such as XMPP, ultimately working to help people move their communication off the unencrypted telephone network and onto the federated, encrypted, and diverse Jabber network. Once again, thanks to JMP for sponsoring OSNews!

But the biggest differential factor between BSDs and GNU/Linux is the way it is structured. In Linux, all components are designed to work together, but are completely separate. You've got the kernel, init systems, multimedia daemons, userland, bootloader, virtualization and containerization mechanisms, package managers, and so on. They are all separate projects with their own goals and are operated by separate entities. This is why we've got different Linux Distributions instead of Operating System. Everyone can take the kernel, start adding components on top of it, and a few minutes later the DistroWatch is even harder to keep up with. Each BSD on the other hand is designed as single system. All components are created and developed together. Things work together perfectly, because they are designed, coded, tested and released as one. Micha Sapka As I've mentioned here and there over the past few weeks, I've been exploring the world of BSD lately, and after bouncing of FreeBSD I've found a very happy home on OpenBSD. Now, this doesn't mean I'm now a full-time OpenBSD user or anything like that - Linux is the main operating system on my gaming PC, my laptop, and my workstation, and that's not going to be changing any time soon. However, after installing, exploring, and using OpenBSD on a machine cobbled together from spare and older parts, I can definitely see the appeal. OpenBSD feels more coherent than a Linux distribution - I use Fedora KDE, if that matters - and the various lower-level systems seem to talk to each other in ways that make more intuitive sense than the individually developed systems in a Linux distribution do. Diving into the command-line interface of a Linux distribution can sometimes feel confusing because different tools use different conventions, because they're developed by entirely different people and projects, with different ideas about how flags should work, how output should be presented, and so on. On OpenBSD, it seems much easier to carry over something you learn from one tool to the next. I simply feel more secure and knowledgeable, even if it's still the same idiot me. The documentation plays a big role here. They're in one place, written in a consistent style, and reference each other left and right, making it easy to find your way around to other commands or tools you haven't yet considered using. On Linux, you're going from one project's documentation to another project's documentation, and not only will the style change, the quality will also vary greatly. That's not to say everything's perfect on OpenBSD - it's clearly a hardened server operating system, and its focus on security will definitely throw up annoying hurdles if you're just trying to do workstation things. Firefox, for instance, is hobbled by strict security rules through unveil, which makes perfect sense for what OpenBSD is first and foremost trying to be, but if you're just a regular user like me, it's annoying that Firefox can only access ~/Downloads, or that it can't set itself as the default browser so unless you disable that check, Firefox will keep complaining about it. Diving into Firefox and unveil is on my list, though, because you should be able to fix' this. Furthermore, while every piece of software, or an equivalent, is pretty much always available for Linux, on OpenBSD it's more hit and miss, and it seems to take a bit longer for new releases of especially bigger software packages to get updated. I mean, there's obviously no Steam on OpenBSD, but smaller, less well-known projects generally also don't support OpenBSD, so you're either going to be compiling things yourself or hope someone packages it up for OpenBSD. Then there's the various vanity things we've come to expect from modern Linux distributions, like slick, fully graphical boot and shutdown sequences, detailed graphical tools for managing your packages, graphical firmware and driver managers, and so on. OpenBSD has none of these things, and while that's no issue for me, I can see how it would throw other people off. FreeBSD, OpenBSD, NetBSD, and the few others often kind of get lost in all the Linux, Windows, and macOS violence, and to be quite honest - I feel like many people in the BSD community seem mostly okay with that. If you've never spent any serious time using any of the BSDs, but you're interested in operating systems and don't mind spending a few hours learning how to manipulate your system through CLI tools - dive in. There's a ton of fun to be had, and things to learn. For now, I'm continuing my exploration of OpenBSD, and if things keep going as well as they are, I may consider at least switching over the workstation in my office from Fedora KDE to OpenBSD - but I highly doubt it'll ever make its way to my gaming desktop or my laptop.

Game of Trees (Got) is a version control system which prioritizes ease of use and simplicity over flexibility. Got is still under development; it is being developed on OpenBSD and its main target audience are OpenBSD developers. Got uses Git repositories to store versioned data. Git can be used for any functionality which has not yet been implemented in Got. It will always remain possible to work with both Got and Git on the same repository. Game of Trees website OpenBSD is developing Game of Trees because they want a version control system that adheres to OpenBSD coding conventions, implements various OpenBSD security practices, and uses nothing but BSD-licensed code. It's important to note, as its developers make very clear, that GoT is not in any way intended as a replacement for git.

The big question - does all this have a future? The good news is that all new hardware has generic support in X. Someone writes either a modesetting kernel driver or a classical wsdisplay kernel driver and they will be automatically supported by the associated drivers in X. The bad news is that to have applications running we require access to a larger open source ecosystem, and that ecosystem has a lot of churn and is easily distracted by shiny new squirrels. The process of upstreaming stuff to X.Org is an ongoing process, but it's likely we'll run into things that will never be suitable for upstream. Nia Alarie on the NetBSD blog I had no idea NetBSD did such heavy customisations of its X.Org implementation, many of which have never made their way upstream. The project also maintains support for several older GPUs, uses its own input driver, and more - it's quite impressive.

Do any of you remember the browser Dillo? The project's been through a rough few years after the main developer of the layout engine sadly passed away, the lead developer disappeared from the project, the dillo.org domain was lost and taken over by spammers - but now there's new people at the helm, and the browser just released it first new version since 2015. Dillo 3.1.0 brings a whole host of new features and improvements. Dillo is open source, uses the FLTK toolkit, and runs on Linux, BSD, MacOS, Windows (Cygwin), and more.