OSnews

Why do so many people keep falling for the same trick over and over again? With an over $400 billion gap between the money invested in AI data centers and the actual revenue these products generate, Silicon Valley slowly returned to the tested and trusted playbook: advertising. Now, ads are starting to appear in pull requests generated by Copilot. According to Melbourne-based software developer Zach Manson, a team member used the AI to fix a simple typo in a pull request. Copilot did the job, but it also took the liberty of editing the PR's description to include this message: Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast." David Uzondu at Neowin It turns out that Microsoft has added ads to over 1.5 million Copilot pull requests on GitHub, and they're even appearing on GitLab, one of the GitHub alternatives. The reasoning is clear, too, of course: AI" companies and investors have poured ungodly amounts of money in AI" that is impossible to recover, even with paying customers. As such, the logical next step is ads, and many AI" companies are already starting to add advertising to their pachinko machines. It was only a matter of time before Copilot would start inserting ads into the pull requests it ejaculates over all kinds of projects. This isn't the first time a once-free service turns on its users, but it's definitely one of the quickest turnarounds I've ever seen. Usually it takes much longer before companies reach the stage of putting ads in their products to plug any financial bleeding, but with the amount of money poured into this useless black hole, it really shouldn't be surprising we're already there. I'm sure Copilot's competitors, like Claude, will soon follow suit. They're enshittifying Git, and developers are just letting it happen. No wonder worker exploitation is so rampant in Silicon Valley.

By reimplementing these features using capabilities, we made the kernel simpler by moving complex scheme and namespace management out of it which improved security and stability by reducing the attack surface and possible bugs. At the same time, we gained a means to support more sandboxing features using the CWD file descriptor. This project leads the way for future sandboxing support in Redox OS. As the OS continues to move toward capability-based security, it will be able to provide more modern security features. Ibuki Omatsu Redox seems to be making the right decisions at, crucially, the right time.

Of course, it was only a matter of time before the time-honoured tradition of the demoscene also got infected by AI". For me personally, generative AI ruins much of the fun. I still enjoy creating pixel art and making little animations and demos. My own creative process remains satisfying as an isolated activity. Alas, obvious AI generated imagery - as well as middle-aged men plagiarizing other, sometimes much younger, hobbyist artists - makes me feel disappointed and empty. It's not as much about effort as it is about the loss of style and personality; soul, if you will. The result is defacement, to echo T. S. Eliot, rather than inspired improvement. Even in more elaborate AI-based works, it's hard to tell where the prompt ends and the pixelling begins. Carl Svensson A wonderful explanation of the rather unique views on originality, stealing, plagiarism, and related topics within the demoscene, which certainly diverge from many other places.

This guide describes how you can install a Plan 9 network on an OpenBSD machine (it will probably work on any unix machine though). The authentication service (called authsrv" on Plan 9) is provided by a unix version: authsrv9. The file service is provided by a program called u9fs". It comes with Plan 9. Both run from inetd. The (diskless) cpu server is provided by running qemu, booted from only a floppy (so without local storage). Finally, the terminal is provided by the program drawterm. The nice thing about this approach is that you can use all your familiar unix tools to get started with Plan 9 (e.g. you can edit the Plan 9 files with your favorite unix editor). I'm assuming you have read at least something about Plan 9, for example the introduction paper Plan 9 from Bell Labs. Mechiel Lukkien If you're running OpenBSD, you're already doing something better than everyone else, and if you want to ascend to the next level, this is a great place to start. Of course, the final level, where you leave your earthly roots behind and become a being of pure enlightened energy, is running Plan 9 on real hardware as the universe intended, but let's not put the cart before the horse. One day, all of humanity will just be an endless collection of interconnected cosmic Plan 9 servers, more plentiful than the stars in the known universe.

Towards the end of 2024, Dennis Biesma decided to check out ChatGPT. The Amsterdam-based IT consultant had just ended a contract early. I had some time, so I thought: let's have a look at this new technology everyone is talking about," he says. Very quickly, I became fascinated." Biesma has asked himself why he was vulnerable to what came next. He was nearing 50. His adult daughter had left home, his wife went out to work and, in his field, the shift since Covid to working from home had left him feeling alittle isolated". He smoked a bit of cannabis some evenings to chill", but had done so for years with no ill effects. He had never experienced a mental illness. Yet within months of downloading ChatGPT, Biesma had sunk 100,000 (about 83,000) into a business startup based on a delusion, been hospitalised three times and tried to kill himself. Anna Moore at The Guardian These stories are absolutely heart-wrenching, and it doesn't just happen to people who have had a history of mental illness or other things you might associate with priming someone for falling for" an AI" chatbot. Just a few years in, and it's already clear that these tools pose a real danger to a group of people of indeterminate size, and proper research into the causes is absolutely warranted and needed. On top of that, if there's any evidence of wrongdoing from the companies behind these chatbots - intentionally making them more addictive, luring people in, ignoring established dangers, covering up addiction cases, etc. - lawsuits and regulation are definitely in order. Only yesterday, Facebook and Google lost a landmark trial in the US, ruling the companies intentionally made social media as addictive as possible, thereby destroying a person's life in the process. Countless similar lawsuits are underway all over the world, and I have a feeling that in a few years to decades, we'll look at unregulated, rampant social media the same way we look at tobacco now. Perhaps AI" chatbots will join their ranks, too.

Today,we'reexcited to announce a significant step forward in our ongoing commitment toWindowssecurity and system reliability: theremovaloftrust for all kerneldrivers signed by thedeprecatedcross-signed root program. This update will helpprotect our customers by ensuring that onlykerneldriversthat the Windows Hardware Compatibility Program (WHCP) have passedand been signed can be loaded by default. To raise the bar for platform security, Microsoft will maintain an explicit allow list of reputable drivers signed by the cross-signed program.Theallow list ensures a secure and compatible experience for alimited number of widely used, and reputable cross-signed drivers. This new kernel trust policy appliestosystems running Windows 11 24H2, Windows 1125H2,Windows 11 26H1,and Windows Server 2025in theApril 2026Windows update. All futureversions ofWindows11and Windows Server will enforce the new kernel trust policy. Peter Waxman at the Windows IT Pro Blog The cross-signed root program was discontinued in 2021, and ran since the early 2000s, so I think it's fair to no longer automatically assume such possibly old and outdated drivers are still to be trusted.

I'll never grow tired of reading about the crazy tricks the Windows 95 development team employed to make the user experience as seamless as they could given the constraints they were dealing with. During the 16bit Windows days, application installers could replace system components with newer versions if such was necessary. Installers were supposed to do a version check, but many of them didn't follow this guidance. When moving to Windows 95, this meant installers ended up replacing Windows 95 system components with Windows 3.x versions, which wasn't exactly a goods thing. So, they came up with a solution. Windows 95 worked around this by keeping a backup copy of commonly-overwritten files in a hidden C:\Windows\SYSBCKUP directory. Whenever an installer finished, Windows went and checked whether any of these commonly-overwritten files had indeed been overwritten. If so, and the replacement has a higher version number than the one in the SYSBCKUP directory, then the replacement was copied into the SYSBCKUP directory for safekeeping. Conversely, if the replacement has a lower version number than the one in the SYSBCKUP directory, then the copy from SYSBCKUP was copied on top of the rogue replacement. Raymond Chen All of this happened entirely silently, and neither the installers nor the user had any idea this was happening. The Windows 95 team tried other solutions, like just making it impossible to replace system components with older versions entirely, but that caused many installers to break. Some installers apparently even went rogue and would create a batch file that would replace the system components upon a reboot, before Windows 95 could perform its silent fixes. Wild. I used Windows 95 extensively, and had no idea this was a thing.

The U.S. Federal Communications Commission said on Monday it was banning the import of all new foreign-made consumer routers, the latest crackdown on Chinese-made electronic gear over security concerns. China is estimated to control at least 60% of the U.S. market for home routers, boxes that connect computers, phones, and smart devices to the internet. David Shepardson at Reuters I'm sure the American public will be thrilled to find out yet another necessity has drastically increased in price.

It's the end of an era: Apple has confirmed to 9to5Mac that the Mac Pro is being discontinued. It has been removed from Apple's website as of Thursday afternoon. The buy" page on Apple's website for the Mac Pro now redirects to the Mac's homepage, where all references have been removed. Apple has also confirmed to 9to5Mac that it has no plans to offer future Mac Pro hardware. Chance Miller at 9To5Mac If a Mac Pro falls in the back of the Apple Store and there's no one around to hear it, does it make a sound?

Several US states, the country of Brazil, and I'm sure other places in the world have enacted or are planning to enact laws that would place the burden of age verification of users on the shoulders of operating system makers. The legal landscape is quite fragmented at this point, and there's no way to tell which way these laws will go, with tons of uncertainties around to whom these laws would apply, if it targets accounts for application store access or the operating system as a whole, what constitutes an operating system in the first place, and many more. Still, these laws are already forcing major players like Apple to implement sharing self-reported age brackets with application developers (at least in iOS), so there's definitely something happening here. In recent weeks, the open source world has also been confronted with the first consequences of these laws, as both systemd and xdg-desktop-portal have responded to operating system-level age verification laws in, among other places, California and Colorado, by adding birthDate to userdb (on systemd's side) and developing an age verification portal (on xdg-desktop-portal's side) for use by Flatpaks. The age verification portal would then use the value set in usrdb's birthDate as its data source. The value in birthDate would only be modifiable by an administrator, but can be read by users, applications, and so on. Crucially, this field is entirely optional, and distributions, desktop environments, and users are under zero obligation to use it or to enter a truthful value. In fact, contrary to countless news items and comments about these additions, nothing about this even remotely constitutes as age verification", as nothing - not the government, not the distribution or desktop environments, not the user - has to or even can verify anything. If these changes make it to your distribution, you don't have to suddenly show your government ID, scan your face, or link your computer to some government-run verification service, or even enter anything anywhere in the first place. Furthermore, while the xdg-desktop-portal's proposals are still fluid and subject to change, consensus seems to be to only share age brackets with applications, instead of full birth dates or specific ages - assuming anything has even been entered in the birthDate field in the first place. Even if your Linux distribution and/or desktop environment implements everything needed to support these changes and expose them to you in a nice user interface, everything about it is optional and under your full control. The field is of the same type as the existing fields emailAddress, realName, and location, which are similarly entirely optional and can be left empty if desired. Taken in isolation, then, as it currently stands, there's really not much meat to these changes at all. The primary reason to implement these changes is to minimally comply with the new laws in California, Colorado, Brazil, and other places, and it's understandable why the people involved would want to do so. If they do not, they could face lawsuits, fines, or worse, and I don't know about you, but I wouldn't want to be on the receiving end of the western world's most incompetent justice system. Aside from that, these changes make it possible to build robust parental controls, which isn't mentioned in the original commits to systemd, but is clearly the main focal point of xdg-desktop-portal's proposal. This all seems well and good, but given today's political climate in the United States, as well as the course of history, that as it currently stands" is doing a lot of heavy lifting. Rightfully so, a lot of people are worried about where this could lead. Sure, today these are just inconsequential, optional changes in response to what seems to be misguided legislation, but what happens once these laws are tightened, become more demanding, and start requiring a lot more than just a self-reported age bracket? In Texas, for instance, H.B. 1131 requires any commercial entity, including websites, that contains more than one-third sexual material harmful to minors" to implement age verification tools using things like government-issued IDs or bank transaction data to verify visitors' ages before allowing them in. The UK has a similar law on the books, too. It's not difficult to imagine how some other law will eventually shift this much stricter, actual age verification from websites and applications into operating systems instead. What will systemd's and xdg-desktop-portal's developers do, then? Will they comply as readily then as they do now? This is a genuine worry, especially if you already belong to a group targeted by the current US administration, or were face-scanned by ICE at a protest. Large groups of especially religious extremists consider anything that's LGBTQ+ to be sexual material harmful to minors", even if it's just something normal like a gay character in a TV show. It's not hard to imagine how age verification laws, especially if they force age verification at the operating system level, can become weaponised to target the LGBTQ+ community, other minorities, and people protesting the Trump regime. You may think this won't affect you, since you're using an open source operating system like desktop Linux or one of the BSDs, and surely they are principled enough to ignore such dangerous laws and simply not comply at all, right? Sadly, here's where the idealism and principles of the open source world are going to meet the harsh boot of reality; while open source software has a picturesque image of talented youngsters hacking away in their bedrooms, the reality is that most of the popular open source operating systems are actually hugely complex operations that require a ton of funding, and that funding is often managed by foundations. And guess where most popular Linux distributions' and BSD variants' foundations are located? Developers from all over the world may contribute to Debian, but all of its financials and trademarks are managed by Software in the Public Interest, domiciled in New York State. Fedora is part of Red Hat, owned by IBM, and

Usually, when developers or programmers write articles about their experiences developing for a platform they have little to no experience with, the end result usually comes down to they do things differently, therefor it is bad actually", which is deeply unhelpful. This article, though, is from a longtime Windows user and developer, but one who hasn't had to work on native Windows development for a long time now. When he decided to write his own native Windows application to scratch a personal itch, it wasn't a great experience. While I followed the Windows development ecosystem from the sidelines, my professional work never involved writing native Windows apps. (Chromium is technically a native app, but is more like its own operating system.) And for my hobby projects, the web was always a better choice. But, spurred on by fond childhood memories, I thought writing a fun little Windows utility program might be a good retirement project. Well. I am here to report that the scene is a complete mess. I totally understand why nobody writes native Windows applications these days, and instead people turn to Electron. Domenic Denicola Denicola decided to try and use the latest technologies and best practices from Microsoft regarding Windows development, and basically came away aghast at just how shot of an experience it really is. I'm not a developer, but you don't need to be to grasp the severity of the situation after following his development timeline and reading about his struggles. If this is truly representative of the Windows application development experience, it's really no surprise just how few new, quality Windows applications there are, and why even Microsoft's own Windows developers resort to things like React for the Start menu to enabler faster and easier iteration. This is a complete dumpster fire.

These were Sun microcontrollers that run Squawk Java ME directly on metal with gc and all the bells and whistles, created by Sun Microsystems in 2005. The feature mesh networking and tcp/ip and multitasking. Even the drivers are java just like Java OS. They run a command and control server by default and there's graphical network builders and deployment managers (Solarium) they also do some more esoteric stuff like process migration. Penny I have no use for these but I want them. They would've made an excellent addition to my Sun article. There's still a detailed tutorial and informational website up about these things, too.

In recent weeks, systemd has both embraced slopcoding and laid the groundwork for age verification built right into systemd-based Linux distributions, there's definitely been an uptick in people talking about alternative init systems. If you want to gain understanding in a rather classic init system, OpenBSD's is a great place to start. OpenBSD has a delightfully traditional init system, which makes it a great place to start learning about init systems. It's simple and effective. There's a bit of a counter movement in the IT and FOSS worlds rebelling against hyperscaler solutions pushing down into everyone's practices. One of the rallying cries I've been seeing is to remind people that You Can Just Do ThingsTM on the computer. The BSD init system, and especially OpenBSD's is something of a godparent to this movement. init(8) just runs a shell script to start the computer, and You Can Just Do ThingsTM in the script to get them to happen on boot. Overeducated-Redneck.net My main laptop is currently in for warranty repairs, but once it returns, I intend to set it up with either OpenBSD or a Linux distribution without systemd (most likely Void) to see how many systems I can distance from systemd without giving myself too much of a headache (I'm guessing my gaming machine will remain on systemd-based Fedora). I'm not particularly keen on slopcoding and government-mandated age verification inside my operating systems, and I'm definitely feeling a bit of a slippery slope underneath my feet. I have my limits.

Earlier this year, Microsoft openly acknowledged the sorry state of Windows 11, and made vague promises about possible improvements somewhere in the near future, but stayed away from making any concrete promises. Today, the company published a blog post with some more details, including some actual concrete, tangible changes it's going to implement over the coming two months. In coming builds, you'll be able to move the taskbar to any side of the screen, instead of it being locked to the bottom, thereby reintroducing a feature present since Windows 95. They're also scaling back their obsession with ramming AI" in every corner of Windows, and will be removing Copilot integrations from Snipping Tool, Photos, Widgets, and Notepad. Furthermore, and this is a big one among Windows users I'm sure, Windows Update will be placed under user control once again, allowing them to ignore updates, postpone them indefinitely, reboot without applying updates, and so on. These are the tangible improvements we'll be able to point to and say the company kept their word, and they all feel like welcome changes. There's also a few promises that feel far more vague and less tangible, like the ever-present, long-running promise to improve File Explorer". I feel like Microsoft's been promising to fix their horrible file manager for years now, without much to show for it, so I hope this time will be different. The company also wants to improve Widgets, the Windows Insider Program, and the Feedback Hub application. These all feel less tangible, and will be harder to quantify and benchmark. Beyond these first round of improvements that we're supposed to be seeing over the coming two months, Microsoft also promises to implement wider improvements across the board, with the usual suspects like better performance, quicker application launches, improved reliability, lower memory usage, and so on. They also promise to move more core Windows user interface components to WinUI 3, including the Start menu, which is currently written in React. Windows Search is another common pain point among Windows users, and here, Microsoft promises to improve its performance and clearly separate local from online results (but no word on making search exclusively local). There's some more details in the blog post, but overall, it sounds great. However, words without actions are about as meaningful as a White House statement on the war with Iran, so seeing is believing.

When Google said they were going to require verification from every single Android developer that would end the ability to install applications from outside of the Play Store (commonly wrongfully referred to as sideloading"), it caused quite a backlash. The company then backtracked a little bit, and said they would come up with an advanced flow" to make sure installing applications from outside of the Play Store remained possible. Well, Google has detailed this advanced flow", and as everyone expected, it's such a massive list of onerous hoops to jump through they might as well just lock Android down to the Play Store and get it over with. First, if a developer is verified, you can download their applications to your device and install them the same way you can do now. Second, developers with limited distribution accounts", such as students or hobby projects, can share their applications with up to 20 devices without verification. Third, and this is where the fun starts, we have unverified developers - basically what all Android developers sharing applications outside of the Play Store are now. Here's the full advanced flow" as described by Google to allow you to install an application from an unverified developer: Setting aside the fact that developer verification is, in and of itself, a massive problem, I'm kind of okay with a few scary warnings, a disclaimer, and perhaps a single reboot to enable installing applications outside of the Play Store - a few things to make normal people shrug their shoulders and not bother. However, adding enabling developer mode and a goddamn 24-hour waiting period is batshit insanity, and clearly has the intention of discouraging everyone, effectively locking Android to the Play Store. Android is already basically an entirely locked-down, closed-source platform, and once this advanced flow" comes into force, there's virtually no difference between iOS and Android, especially for us Europeans who get similarly onerous anti-user nonsense when trying to install alternative application stores on iOS. I see no reason to buy Android over iOS at this point - might as well get the faster phone with better update support.

What happens if you make a Linux syscall in a Windows application? So yeah, you can make Linux syscalls from Windows programs, as long as they're running under Wine. Totally useless, but the fact that such a Frankenstein monster of a program could exist is funny to me. nicebyte at gpfault.net The fact that this works is both surprising and unsurprising at the same time.

The GNOME team has released GNOME 50, the latest version of what is probably the most popular open source desktop environment. It brings fine-grained parental controls, and the groundwork for web filtering so that in future releases, parents and guardians can set content filters for children. Our own kids are still way too young to have access to computers and the internet, but I'm not sure I'll ever resort to these kinds of tools when the time comes. I didn't have any such controls imposed upon me as a child on the early internet, but then, you can't really compare the '90s internet to that of today. The Orca screen reader received a lot of attention in GNOME 50, with a new preference window, both global and per-application settings, and much more. There's also a brand new reduced motion setting, which will tame the animations in the user interface. Document annotation has been overhauled and modernised, and the file manager has been optimised across the board for better performance and lower memory usage. Remote Desktop also saw a lot of work in GNOME 50. It's now hardware-accelerated using VA-API and Vulkan, and thanks to HiDPI support, the session will properly adapt to the screen being used. Kerberos Authentication support has been added, and you can now use the remote webcam locally. There's way more here, like improved support for variable-refresh rates and fractional scaling, HDR screen sharing, fixes for weird NVIDIA driver nonsense, and much, much more. As always, GNOME 50 will find its way to your distribution soon enough.

PosrtmarketOS, the Linux distribution' for mobile devices, now also has an immutable variant, called Duranium. Duranium is an immutable variant of postmarketOS, built around the idea that your device should just work, and keep working. You shouldn't need to know what a terminal is to keep your device running. Immutable" means the core operating system is read-only and can't be modified while it's running. System updates are applied as complete, verified images rather than individual packages. Either the new image works, or the system falls back to the previous one automatically. No partially-applied state. No debugging audio when you need to make a phone call and no fussing with a broken web browser when you just want to doomscroll cat photos. It also means developers can reproduce the exact state of a user's device, making it much easier to track down and fix issues. Clayton Craft on the postmarketOS blog Duranium is built around the various functionalities and tooling provided by systemd, meaning the project didn't have to reinvent the wheel. It works similarly to other immutable distributions, in that images for the base are downloaded and installed as a whole, with the preferred application installation method being Flatpak. Security-wise, Duranium uses dm-verity to protect /usr, cryptographically verifying data as it's read. The image simply won't boot if anything's been tampered with. LUKS2 is used to encrypt mutable user and operating system data and configuration on the root file system. Duranium is still under heavy development, but it makes sense to implement something like this now, since in the world of mobile devices, this has become the norm. I'm glad postmarketOS is taking these steps, and I sincerely hope I'll eventually be able to use a postmarketOS device with KDE's Plasma mobile shell at some point in the near future in my day-to-day life. This requires both postmarketOS to improve as well as for the regulatory landscape to break the duopoly on banking and government applications held by Android and iOS, and with the state of the US government as it is, this might actually be something Europe's interested in achieving.

DOS didn't have sudo yet. This gross oversight has been addressed. SUDO examines the environment for the COMSPEC variable to find the default command interpreter, falling back to C:\COMMAND.COM if not set. The interpreter is then executed in unprotected real mode for full privileges. SUDO for DOS' Codeberg page A vital tool, for sure.

Once again, social media giants Facebook and TikTok have been caught red-handed. More than a dozen whistleblowers and insiders have laid bare how the companies took risks with safety on issues including violence, sexual blackmail and terrorism as they battled for users' attention. An engineer at Meta, which owns Facebook and Instagram, described how he had been told by senior management to allow more borderline" harmful content - which includes misogyny and conspiracy theories - in user's feeds to compete with TikTok. They sort of told us that it's because the stock price is down," the engineer said. Marianna Spring and Mike Radford at the BBC Meta, TikTok, and Twitter are criminal enterprises, and their executives should be trembling in court instead of scheming on yachts. Their role in legitimising far-right extremism will eventually catch up to them, and once that happens, no yacht is going to keep them safe.

Modern kernel anti-cheat systems are, without exaggeration, among the most sophisticated pieces of software running on consumer Windows machines. They operate at the highest privilege level available to software, they intercept kernel callbacks that were designed for legitimate security products, they scan memory structures that most programmers never touch in their entire careers, and they do all of this transparently while a game is running. If you have ever wondered how BattlEye actually catches a cheat, or why Vanguard insists on loading before Windows boots, or what it means for a PCIe DMA device to bypass every single one of these protections, this post is for you. Adrian Diaza I hate that we need proprietary rootkits just to play competitive multiplayer games - we can chalk this up to a few sad people ruining the experience for everyone else, as so often happens. I have a dedicated parts bin Windows box just to play League of Legends (my one vice alright, nobody's perfect) so I don't really care if it has a proprietary rootkit running in the background as there's not a single bit of valuable data on that machine, but for most people, that's not realistic. Virtually every League of Legends player hands over control of their entire computer to a proprietary rootkit developed and deployed by a company from China, whereas players of other popular online multiplayer games must install rootkits from companies from the United States. If anyone inside the governments of these countries ever wants to implement a backdoor in dozens (hundreds?) of millions of Windows machines, this is the way to go. It's an absolutely bizarre situation.

Tribblix, the Illumos distribution focused on giving you a classic UNIX-style experience, has released a new version. There are several noticeable version updates in this release. The graphical libraries libtiff and OpenEXR have been updated, retaining the old shared library versions for now. OpenSSL is now from the 3.5 series with the 3.0 api by default. Bind is now from the 9.20 series. OpenSSH is now 10.2, and you may get a Post-Quantum Cryptography warning if connecting to older SSH servers. Tribblix m39 release notes If you're already running Tribblix, updating is easy, and if you want to try it out, head on over to the downloads page. Rests me to say that Tribblix is a treasure, and it must be protected at all costs. It's rare to see a passion project like this maintain such a steady pace.

Java 26 delivers thousands of improvements that boost developer productivity, simplify the language, and help developers integrate AI and cryptography functionality into their applications. To help developers further streamline and enhance their development initiatives, Oracle is also announcing the new Java Verified Portfolio, which provides developers with a curated set of Oracle-supported tools, frameworks, libraries, and services, including commercial support for JavaFX, a Java-based UI framework, and Helidon, a Java framework for microservices. In addition, Oracle intends to align Helidon's release cadence with Java releases and propose Helidon as an OpenJDK project. Oracle's Java 26 press release Oracle's press releases lists the most important JDK Enhancement Proposals in this release, as do the release notes and the project page at OpenJDK. In addition, Java developer Hanno Embregts published a detailed blog post that dives deeper into this new release.

Since many of the platforms and conventions that came to dominate computing came from the western world, we never give it a second thought that virtually everything related to programming is written in English using the English alphabet. However, there's no real reason behind arriving at this point other than convention and the course of history - with the right tooling, you could program a computer in whatever language or alphabet (or other writing system!) you desire. For example, what about programming in Korean, using Hangul? Han is a statically-typed, compiled programming language where every keyword is written in Korean. It compiles to native binaries through LLVM IR and also ships with a tree-walking interpreter for instant execution. The compiler toolchain is written entirely in Rust. Han's GitHub page Han is written entirely in Korean, and uses the genius and easy-to-learn Hangul script. Hangul was developed by King Sejong the Great in the middle of the 15th century, to replace the Chinese-based characters used to write Korean up until that point. Since it was specifically designed to be easy to learn by scholars and the general public of the time alike to promote literacy, the Hangul alphabet is stupidly easy to learn; I managed to teach myself the Hangul alphabet in an single afternoon a decade or so ago. Obviously, do note that learning Hangul (an alphabet) isn't the same thing as learning Korean (a language). One of my favourite aspects of Hangul is that it combines the letters making up a syllable into single structured syllable blocks, which gives it its unique look and makes it quite easy to grasp - you'll quickly start recognising common syllables. On top of that, it's said that the individual Hangul consonants mimic the shape of speech organs (tongue, throat, etc.), which, once you see it, you can't unsee, further aiding in remembering what letters sound like. If you have an afternoon to kill, it's certainly a fun thing to learn. Regardless, it's very welcome to see efforts like this, if only to remember that programming being an Anglophone affair is but an accident, not a law of nature.

It's only a small annoyance in the grand scheme of the utter idiocy that is modern Windows, but apparently it's one enough people complained about Microsoft is finally addressing it. In all of its wisdom, Microsoft doesn't allow you to set the name of your user's home folder during the installation procedure of Windows 11. The folder's name is automatically generated based on your Microsoft account's username or email address, something I've personally really disliked since I have been using thomholwerda for as long as I can remember. Last year, they introduced an incredibly obtuse method of setting your own home folder name, but now the company is finally adding it as an optional step during the regular installation process. Expanding on our work which started rolling to Insiders last fall, you can now choose a custom name for your user folder on the Device Name page when going through Windows setup. This most recent update now makes it easier to choose a custom name. The naming option is available during setup only. If you skip this step, Windows will use the default folder name and continue setup as usual. Windows Insider Program Team This means you now have the option of defining your own home folder name, excluding CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, COM^1, COM^2, COM^3, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, LPT^1, LPT^2, and LPT^3. It's a very small change, and certainly not something that will turn Windows' ship around, but at least it's something that's being done for users who actually care. It's also such a small change, such a small addition, that one wonders why it's taken them this long. I'm assuming there's already some incredibly complex and hacky way to change your automatically assigned home folder name by diving deep into the registry, converting your root drive back to FAT16, changing some values in a DLL file through a hex editor, and then converting back to NTFS, but this is clearly a much better way of handling it.

What if you have a very modern machine that is entirely UEFI-only, meaning it has no compatibility support module and thus no way of enabling a legacy BIOS mode? Well, install a CSM as an EFI application, of course! CSMWrap is an EFI application designed to be a drop-in solution to enable legacy BIOS booting on modern UEFI-only (class 3) systems. It achieves this by wrapping a Compatibility Support Module (CSM) build of the SeaBIOS project as an out-of-firmware EFI application, effectively creating a compatibility layer for traditional PC BIOS operation. CSMWrap's GitHub page The need for this may not be immediately obvious, but here's the problem: if you want to run an older operating system that absolutely requires a traditional BIOS on a modern machine that only has UEFI without any CSM options (a class 3-machine), you won't be able to boot said operating system. CSMWrap is a possible solution, as it leverages innate EFI capabilities to run a CSM as an EFI application, thereby adding the CSM functionality back in. All you need to do is drop CSMWrap into /efi/boot on the same drive the operating system that needs BIOS to boot is on, and UEFI will list it as a bootable operating system. It does come with some limitations, however. For instance, one logical core of your processor will be taken up by CSMWrap and will be entirely unavailable to the booted BIOS-based operating system. In other words, this means you're going to need a processor with at least more than one logical processor (e.g., even a single-core machine with hyperthreading will work). It's also suggested to add a legacy-capable video card if you're using an operating system that doesn't support VESA BIOS extensions (e.g. anything older than NT). This is an incredibly neat idea, and even comes with advantages over built-in CSMs, since many of those are untested and riddled with issues. CSMWrap uses SeaBIOS, which is properly tested and generally a much better BIOS than whatever native CSMs contain. All in all, a great project.

SMF is the illumos system for managing traditional Unix services (long-lived background processes, usually). It's quite rich in order to correctly accommodate a lot of different use cases. But it sometimes exposes that complexity to users even when they're trying to do something simple. In this post, I'll walk through an example using a demo service and the svcprop(1) tool to show the details. Dave Pacheco Soalris' system management facility or SMF is effectively Solaris' systemd, and this article provides a deeper insight into one of its features: properties. While using SMF and its suite of tools and commands for basic tasks is rather elementary and easy to get into - even I can do it - once you start to dive deeper into what is can do, things get complex and capable very fast.

Google has announced that it will release Chrome for Linux on ARM64 in the second quarter of this year. Launching Chrome for ARM64 Linux devices allows more users to enjoy the seamless integration of Google's most helpful services into their browser. This move addresses the growing demand for a browsing experience that combines the benefits of the open-source Chromium project with the Google ecosystem of apps and features. This release represents a significant undertaking to ensure that ARM64 Linux users receive the same secure, stable, and rich Chrome experience found on other platforms. The Chromium Blog While the idea of running Linux on Arm, only to defile it with something as unpleasant as Chrome seem entirely foreign to me, most normal people do actually use Google's browser. Having it available on Linux for Arm makes perfect sense, and might convince a few people to buy an Arm machine for Linux, assuming the platform can get its act together.

I will not pass up an opportunity to make you talk about Plan 9, so let's focus on Acme. Acme is remarkable for what it represents: a class of application that leverages a simple, text-based GUI to create a compelling model of interacting with all of the tools available in the Unix (or Plan 9) environment. Cox calls it an integrating development environment," distinguishing it from the more hermetic integrated development environment" developers will be familiar with. The simplicity of its interface is important. It is what has allowed Acme to age gracefully over the past 30 or so years, without the constant churn of adding support for new languages, compilers, terminals, or color schemes. Daniel Moch While the article mentions you can use Acme on UNIX, to really appreciate it you have to use it on Plan 9, which today most likely means 9front. Now, I am not the kind of person who can live and breathe inside 9front - you need to be of a certain mindset to be able to do so - but even then I find that messing around with Plan 9 has given me a different outlook on UNIX. In fact, I think it has helped me understand UNIX and UNIX-like systems better and more thoroughly. If you're not sure if Plan 9 is something that suits you, the only real way to find out is to just use it. Fire up a VM, read the excellent documentation at 9front, and just dive into it. Most of you will just end up confused and disoriented, but a small few of you will magically discover you possess the right mindset. Just do it.

I'm feeling kind of nostalgic today so I thought I'd write Hello, world! in Z80 assembly for the ZX Spectrum! The last time I wrote any Z80 assembly was when I was 14 so around 36 years ago! I may be a little rusty! Old Man By the Sea It's easy to tell the world hello in BASIC, but a bit more involved in Z80 assembly.

Red Hat developer Marcin Juszkiewicz is working on the RISC-V port of Fedora Linux, and after a few months of working on it, published a blog post about just how incredibly slow RISC-V seems to be. This is a real problem, as in Fedora, build results are only released once all architectures have completed their builds. There is no point of going for inclusion with slow builders as this will make package maintainers complain. You see, in Fedora build results are released into repositories only when all architectures finish. And we had maintainers complaining about lack of speed of AArch64 builders in the past. Some developers may start excluding RISC-V architecture from their packages to not have towait. And any future builders need to be rackable and manageable like any other boring server (put in a rack, connect cables, install, do not touch any more). Because no one will go into a data centre to manually reboot an SBC-basedbuilder. Without systems fulfilling both requirements, we can not even plan for the RISC-V 64-bit architecture to became one of official, primary architectures in FedoraLinux. Marcin Juszkiewicz RISC-V really seems to have hit some sort of ceiling over the past few years, with performance improvements stalling and no real performance-oriented chips and boards becoming available. Everybody seems to want RISC-V to succeed and become an architecture that can stand its own against x86 and Arm, but the way things are going, that just doesn't seem likely any time soon. There's always some magical unicorn chip or board just around the corner, but when you actually turn that corner, it's just another slow SBC only marginally faster than the previous one. Fedora is not the first distribution struggling with bringing RISC-V online. Chimera Linux faced a similar issue about a year ago, but managed to eventually get by because someone from the Adelie Linux team granted remote access to an unused Milk-V Pioneer, which proved enough for Chimera for now. My hope is still that eventually we're going to see performant, capable RISC-V machines, because I would absolutely jump for joy if I could have a proper RISC-V workstation.

Now let's go live to Amazon for the latest updates about this developing story. Amazon's ecommerce business has summoned a large group of engineers to a meeting on Tuesday for a deep dive" into a spate of outages, including incidents tied to the use of AI coding tools. The online retail giant said there had been a trend of incidents" in recent months, characterized by a high blast radius" and Gen-AI assisted changes" among other factors, according to a briefing note for the meeting seen by the FT. Under contributing factors" the note included novel GenAI usage for which best practices and safeguards are not yet fully established." Rafe Rosner-Uddin at Ars Technica Oh boy.

Back in 2023, John Earnest created a fun drawing application called WigglyPaint. The thing that makes WigglyPaint unique is that it automatically applies what artists call the line boil effect to anything you draw, making it seem as if everything is wiggling (hence the name). Even if you're not aware of the line boil effect, you've surely encountered it several times in your life. The tool may seem simple at first glance, but as Earnest details, he's put quite a lot of thought into the little tool. WigglyPaint was well-received, but mostly remained a curiosity - that is, until artists in Asia picked up on it, and the popularity of WigglyPaint positively exploded from a few hundred into the millions. The problem, though, is that basically nobody is actually using WigglyPaint: they're all using slopcoded copycats. The sites are slop; slapdash imitations pieced together with the help of so-called Large Language Models" (LLMs). The closer you look at them, the stranger they appear, full of vague, repetitive claims, outright false information, and plenty of unattributed (stolen) art. This is what LLMs are best at: quickly fabricating plausible simulacra of real objects to mislead the unwary. It is no surprise that the same people who have total contempt for authorship find LLMs useful; every LLM and generative model today is constructed by consuming almost unimaginably massive quantities of human creative work- writing, drawings, code, music- and then regurgitating them piecemeal without attribution, just different enough to hide where it came from (usually). LLMs are sharp tools in the hands of plagiarists, con-men, spammers, and everyone who believes that creative expression is worthless. People who extract from the world instead of contributing to it. It is humiliating and infuriating to see my work stolen by slop enthusiasts, and worse, used to mislead artists into paying scammers for something that ought to be free. John Earnest There's a huge amount of slopcoded WrigglyPaint ripoffs out there, and it goes far beyond websites, too. People are putting slopcoded ripoffs in basic webviews, and uploading them en masse to the Play Store and App Store. None of these slopcoded ripoffs actually build upon WrigglyPaint with new ideas or approaches, there's no creativity or innovation; it's just trash barfed up by glorified autocomplete built upon mass plagiarism and theft, made" by bottom feeders who despise creativity, art, and originality. You know how when you go to IKEA or whatever other similar store to buy picture frames, they have these stock photos of random people in them? I wonder if AI" enthusiasts understand you're supposed to replace those with pictures that actually have meaning to you.

Redox, the rapidly improving general purpose operating system written in Rust, has amended its contribution policy to explicitly ban code regurgitated by AI". Redox OS does not accept contributions generated by LLMs (Large Language Models), sometimes also referred to as AI". This policy is not open to discussion, any content submitted that is clearly labelled as LLM-generated (including issues, merge requests, and merge request descriptions) will be immediately closed, and any attempt to bypass this policy will result in a ban from the project. Redox' contribution policy Excellent news.

While FreeBSD 15.x may be getting all the attention, the FreeBSD 14.x branch continues to be updated for the more conservative users among us. FreeBSD 14.4 has been released today, and brings with it updated versions of OpenSSH, OpenZFS, and Bhyve virtual machines can now share files with their host over 9pfs - among other things, of course.

While IBM's OS/2 technically did die, its development was picked up again much later, first through eComStation, and later, after money issues at its parent company Mensys, through ArcaOS. eComStation development stalled because of the money issues and has been dead for years; ArcaOS picked up where it left off and has been making steady progress since its first release in 2017. Regardless, the developers behind both projects develop OS/2 under license from IBM, but it's unclear just how much they can change or alter, and what the terms of the agreement are. Anyway, ArcaOS 5.1.2 has just been released, and it seems to be a rather minor release. It further refines ArcaOS' support for UEFI and GPT-based disks, the tentpole feature of ArcaOS 5.1 which allows the operating system to be installed on a much more modern systems without having to fiddle with BIOS compatibility modes. Looking at the list of changes, there's the usual list of updated components from both Arca Noae and the wider OS/2 community. You'll find the latest versions of of the Panorama graphics drivers, ACPI, USB, and NVMe drivers, improved localisation, newer versions of the VNC server and viewer, and much more. If you have an active Support & Maintenance subscription for ArcaOS 5.1, this update is free, and it's also available at discounted prices as upgrades for earlier versions. A brand new copy of ArcaOS 5.1.x will set you back $139, which isn't cheap, but considering this price is probably a consequence of what must be some onerous licensing terms and other agreements with IBM, I doubt there's much Arca Noae can do about it.

Oh boy. Wikipedia editors have implemented new policies and restricted a number of contributors who were paid to use AI to translate existing Wikipedia articles into other languages after they discovered these AI translations added AI hallucinations," or errors, to the resulting article. Emanuel Maiberg at 404 Media There seems to be this pervasive conviction among Silicon Valley techbro types, and many programmers and developers in general, that translation and localisation are nothing more than basic find/replace tasks that you can automate away. At first, we just needed to make corpora of two different languages kiss and smooch, and surely that would automate translation and localisation away if the corpora were large enough. When this didn't turn out to work very well, they figured that if we made the words in the corpora tumble down a few pachinko machines and then made them kiss and smooch, yes, then we'd surely have automated translation and localisation. Nothing could be further from the truth. As someone who has not only worked as a professional translator for over 15 years, but who also holds two university degrees in the subject, I keep reiterating that translation isn't just a dumb substitution task; it's a real craft, a real art, one you can have talent for, one you need to train for, and study for. You'd think anyone with sufficient knowledge in two languages can translate effectively between the two, but without a much deeper understanding of language in general and the languages involved in particular, as well as a deep understanding of the cultures in which the translation is going to be used, and a level of reading and text comprehension that go well beyond that of most, you're going to deliver shit translations. Trust me, I've seen them. I've been paid good money to correct, fix, and mangle something usable out of other people's translations. You wouldn't believe the shit I've seen. Translation involves the kinds of intricacies, nuances, and context AI" isn't just bad at, but simply cannot work with in any way, shape, or form. I've said it before, but it won't be long before people start getting seriously injured - or worse - because of the cost-cutting in the translation industry, and the effects that's going to have on, I don't know, the instruction manuals for complex tools, or the leaflet in your grandmother's medications. Because some dumbass bean counter kills the budget for proper, qualified, trained, and experienced translators, people are going to die.

Every modifier key starts simple and humble, with a specific task and a nice matching name. This never lasts. The tasks become larger and more convoluted, and the labels grow obsolete. Shift no longer shifts a carriage, Control doesn't send control codes, Alt isn't for alternate nerdy terminal functions. Fn is the newest popular modifier key, and it feels we're speedrunning it through all the challenges without having learned any of the lessons. Marcin Wichary Grab a blanket, curl up on the couch with some coffee or tea, and enjoy.

MenuetOS, the operating system written in x86-64 assembly, has released two new versions since we last talked about it roughly two months ago. In fact, I'm not actually sure it's just two, or more, or fewer, since it seems sometimes releases disappear entirely from the changelog, making things a bit unclear. Anyway, since the last time we talked about MenuetOS, it got improvements to videocalling, networking, and HDA audio drivers, and a few other small tidbits.

And when a Redox monthly progress report is here, Haiku's monthly report is never far behind (or vice versa, depending on the month). Haiku's February was definitely a busy month, but there's no major tentpole changes or new features, highlighting just how close Haiku is to a new regular beta release. The OpenBSD drivers have been synchronised wit upstream to draw in some bugfixes, there's a ton of smaller fixes to various applications like StyledEdit, Mail, and many more, as well a surprisingly long list of various file system fixes, improving the drivers for file systems like NTFS, Btrfs, XFS, and others. There's more, of course, so just like with Redox, head on over to pore over the list of smaller changes, fixes, and improvements. Just like last month, I'd like to mention once again that you really don't need to wait for the beta release to try out Haiku. The operating system has been in a fairly stable and solid condition for a long time now, and whatever's the latest nightly will generally work just fine, and can be updated without reinstallation.

February has been a busy month for Redox, the general purpose operating system written in Rust. For instance, the COSMIC compositor can now run on Redox as a winit window, the first step towards fully porting the compositor from COSMIC to Redox. Similarly, COSMIC Settings now also runs on Redox, albeit with only a very small number of available settings as Redox-specific settings panels haven't been made yet. It's clear the effort to get the new COSMIC desktop environment from System76 running on Redox is in full swing. Furthermore, Vulkan software can now run on Redox, thanks to enabling Lavapipe in Mesa3D. There's also a ton of fixes related to the boot process, the reliability of multithreading has been improved, and there's the usual long list of kernel, driver, and Relibc improvements as well. A major port comes in the form of NodeJS, which now runs on Redox, and helped in uncovering a number of bugs that needed to be fixed. Of course, there's way more in this month's progress report, so be sure to head on over and read the whole thing.

One day, I suddenly wondered how to detect when a USB device is plugged or unplugged from a computer running Linux. For most users, this would be solved by relying on libusb. However, the use case I was investigating might not actually want to do so, and so this led me down a poorly-documented rabbit hole. ArcaneNibble (or R) And ArcaneNibble (or R) is taking you down with them.

Oracle's Solaris 11 basically comes in two different flavours: the SRU (Support Repository Update) releases for commercial Oracle customers, and the CBE (Common Build Environment) releases, available to everyone. We've covered the last few SRU releases, and now it's time for a new CBE release. We first introduced the Oracle Solaris CBE in March 2022 and we released an updated version in May 2025. Now, as Oracle Solaris keeps on evolving, we've released the latest version of our CBE. With the previous release Alan and Jan had compiled a list to cover all the changes in the three years since the first CBE release. This time, because it's relatively soon after the last release we are opting to just point you to the what's new blogs on the feature release SRUs Oracle Solaris 11.4 SRU 84, Oracle Solaris 11.4 SRU 87, and Oracle Solaris 11.4 SRU 90. And of course you can always go to the blogs by Joerg Moellenkamp and Marcel Hofstetter who have excellent series of articles that show how you can use the Oracle Solaris features. Joost Pronk van Hoogeveen at the Oracle Solaris Blog You can update your existing installation with a pkg update, or do a fresh insrtall with the new CBE images.

In the world of open source, relicensing is notoriously difficult. It usually requires the unanimous consent of every person who has ever contributed a line of code, a feat nearly impossible for legacy projects. chardet, a Python character encoding detector used by requests and many others, has sat in that tension for years: as a port of Mozilla's C++ code it was bound to the LGPL, making it a gray area for corporate users and a headache for its most famous consumer. Recently the maintainers used Claude Code to rewrite the whole codebase and release v7.0.0, relicensing from LGPL to MIT in the process. The original author, a2mark, saw this as a potential GPL violation. Tuan-Anh Tran Everything about this feels like a license violation, and in general a really shit thing to do. At the same time, though, the actual legal situation, what lawyers and judges care about, is entirely unsettled and incredibly unclear. I've been reading a ton of takes on what happened here, and it seems nobody has any conclusive answers, with seemingly valid arguments on both sides. Intuitively, this feels deeply and wholly wrong. This is the license-washing AI" seems to be designed for, so that proprietary vendors can take code under copyleft licenses, feed it into their AI" model, and tell it to regurgitate something that looks just different enough so a new, different license can be applied. Tim takes Jim's homework. How many individual words does Tim need to change - without adding anything to Jim's work - before it's no longer plagiarism? I would argue that no matter how many synonyms and slight sentence structure changes Tim employs, it's still a plagiarised work. However, what it feels like to me is entirely irrelevant when laws are involved, and even those laws are effectively irrelevant when so much money is riding on the answers to questions like these. The companies who desperately want this to be possible and legal are so wealthy, so powerful, and sucked up to the US government so hard, that whatever they say might very well just become law. AI" is the single-greatest coordinated attack on open source in history, and the open source world would do well to realise that.

The memory management in DOS is simple, but that simplicity may be deceptive. There are several rather interesting pitfalls that programming documentation often does not mention. Michal Necasek at the OS/2 Museum A must-read for people writing software for earlier DOS versions.

What's the scroll lock key actually for? Scroll Lock was reportedly specifically added for spreadsheets, and it solved a very specific problem: before mice and trackpads, and before fast graphic cards, moving through a spreadsheet was a nightmare. Just like Caps Lock flipped the meaning of letter keys, and Num Lock that of the numeric keypad keys, Scroll Lock attempted to fix scrolling by changing the nature of the arrow keys. Marcin Wichary I never really put much thought into the scroll lock key, and I always just assumed that it would, you know, lock scrolling. I figured that in the DOS era, wherein the key originated, it stopped DOS from scrolling, keeping the current output of your DOS commands on the screen until you unlocked scrolling again. In graphical operating systems, I assumed it would stop any window with scrollable content from scrolling, or something - I just never thought about it, and never bothered to try. Well, its original function was a bit different: with scroll lock disabled, hitting the arrow keys would move the selection cursor. With scroll lock enabled, hitting the arrow keys would move the content instead. After reading this, it makes perfect sense, and my original assumption seems rather silly. It also seems some modern programs, like Excel, Calc, some text editors, and others, still exhibit this same behaviour when the scroll lock key is used today. The more you know.

Apple today announced the MacBook Neo," an all-new kind of low-cost Mac featuring the A18 Pro chip for $599. The MacBook Neo is the first Mac to be powered by an iPhone chip; the A18 Pro debuted in 2024's iPhone 16 Pro models. Apple says it is up to 50% faster for everyday tasks than the bestselling PC with the latest shipping Intel Core Ultra 5, up to 3x faster for on-device AI workloads, and up to 2x faster for tasks like photo editing. The MacBook Neo features a 13-inch Liquid Retina display with a 2408-by-1506 resolution, 500 nits of brightness, and an anti-reflective coating. The display does not have a notch, instead featuring uniform, iPad-style bezels. Hartley Charlton at MacRumors There's no denying this is a great offering from Apple, and it's going to sell really well, especially in the US. I can't think of any other laptop on the market that offers this kind of complete package at such an attractive price point - on the Windows side, you're going to get plastic laptops with worse displays, worse battery life, and, well, Windows. For education buyers, the price drops from $599 to $499, making it a no-brainer choice for families sending their kids off to high school or university. In the US, at least. Here in Europe, or at least in Sweden where I checked the price of the base model, it's going for almost 800 ($930), at which point the cost-cutting measures Apple has taken are a bit harder to swallow. At that kind of price point, I'm not going to accept a mere 8GB of RAM, 256GB of storage, and a paltry 60Hz display. When I saw the announcement of this new MacBook earlier today, I wondered if this could be my way of finally getting a macOS review on OSNews after well over a decade, but at 800 for something I won't be using after I'm done with the review? I can't justify that. Regardless, you're going to see tons of these in schools and in wrapping paper for the holiday season and birthdays, and at least at American pricing, it's definitely a great deal.

Chips and Cheese has an excellent deep dive into Arm's latest core design, and I have thoughts. Arm now has a core with enough performance to take on not only laptop, but also desktop use cases. They've also shown it's possible to deliver that performance at a modest 4 GHz clock speed. Arm achieved that by executing well on the fundamentals throughout the core pipeline. X925's branch predictor is fast and state-of-the-art. Its out-of-order execution engine is truly gargantuan. Penalties are few, and tradeoffs appear well considered. There aren't a lot of companies out there capable of building a core with this level of performance, so Arm has plenty to be proud of. That said, getting a high performance core is only one piece of the puzzle. Gaming workloads are very important in the consumer space, and benefit more from a strong memory subsystem than high core throughput. A DSU variant with L3 capacity options greater than 32 MB could help in that area. X86-64's strong software ecosystem is another challenge to tackle. And finally, Arm still relies on its partners to carry out its vision. I look forward to seeing Arm take on all of these challenges, while also iterating on their core line to keep pace as AMD and Intel improve their cores. Hopefully, extra competition will make better, more affordable CPUs for all of us. Chester Lam at Chips and Cheese The problem with Arm processors in the desktop (and laptop) space certainly isn't one of performance - as this latest design by Arm once again shows. No, the real problem is a complete and utter lack of standardisation, with every chip and every device in the Arm space needing dedicated, specific operating system images people need to create, maintain, and update. This isn't just a Linux or BSD problem, as even Microsoft has had numerous problems with this, despite Windows on Arm only supporting a very small number of Qualcomm processors. A law or rule that has held fast since the original 8086: never bet against x86. The number of competing architectures that were all surely going to kill x86 is staggeringly big - PowerPC, Alpha, PA-RISC, Sparc, Itanium, and many more - and even when those chips were either cheaper, faster, or both, they just couldn't compete with x86's unique strength: its ecosystem. When I buy an x86 computer, either in parts or from an OEM, either Intel or AMD, I don't have to worry for one second if Windows, Linux, one of the BSDs, or goddamn FreeDOS, and all of their applications, are going to run on it. They just will. Everything is standardised, for better or worse, from peripheral interconnects to the extremely crucial boot process. On the Arm side, though? It's a crapshoot. That's why whenever anyone recommends a certain cool Arm motherboard or mini PC, the first thing you have to figure out is what its software support situation is like. Does the OEM provide blessed Linux images? If so, do they offer more than an outdated Ubuntu build? Have they made any update promises? Will Windows boot on this thing? Does it work with any GPUs I might already own? There's so many unknowns and uncertainties you just don't have to deal with when opting for x86. For its big splashy foray into general purpose laptops with its Snapdragon Elite chips, Qualcomm promised Linux support on par with Windows from day one. We're several years down the line, and it's still a complete mess. And that's just one chip line, of one generation! As long as every individual Arm SoC and Arm board are little isolated islands with unknown software and hardware support status, x86 will continue to survive, even if x86 laptops use more power, even if x86 chips end up being slower. Without the incredible ecosystem x86 has, Arm will never achieve its full potential, and eventually, as has happened to every single other x86 competitor, x86 will eventually catch up to and surpass Arm's strong points, at lower prices. Never bet against x86.

Fifteen months have passed since our last Guix/Hurd on a Thinkpad X60 post and a lot has happened with respect to the Hurd. And most of you will have guessed, unless you skipped the title of this post, the rumored x86_64 support has landed in Guix! Janneke Nieuwenhuizen and Yelninei at the Guix blog A huge amount of work has gone into this effort over the past 18 months, but you can now download Guix and alongside the Linux kernel, you can now opt for the Hurd as well, in eother 32bit or 64 bit flavour. Do note that while Debian GNU/Hurd offers about 75% of Debian packages, Guix/Hurd only offers about 1.7% (32-bit) and 0.9% (64-bit) of packages for now. These percentages are always growing, of course, and now that Guix/Hurd can be installed in virtual machines and even on bare metal relatively easily like this, things might speed up a bit.

Have you bought and set up a new phone for someone else lately, especially someone less technologically savvy? It's a bit of a nightmare, with an endless list of confusing steps and dark patterns trying to trick you into signing up for all kinds of services. Joel Chrono (he took his username from the best game ever made) just went through this experience, with new Samsung phones for his parents, and it wasn't great. Without me, my parents would have ended up creating at least one extra Samsung account. Cloud services like OneDrive or Google Photos would be sucking up files and copying them to their servers, getting filled up with the data and then asking them to subscribe to unlock more storage a couple of months down the line. Left on their own, my parents may be seeing ads popping up constantly in OneUI, as well as browsing the web without an adblocker, they would be using default applications that don't work as reliably, that track whatever they do to a certain degree. And of course, all of those AI assistants would be listening in in the background. It really is a nightmare out there, and it's not only affecting my parents, it affects all of those unaware of the dangers that these practices bring. It's a mess all around. Joel Chrono In this particular case it involves Samsung phones, but the same applies to phones from other brands and even with other operating systems. Do you want to login with these accounts? Please add your credit card and all your personal information! Set up tap-to-pay so we can see where you buy what! Do you want to subscribe to our music service? Do you want access to our streaming service? What about the premium versions? Need more online storage? You're only getting 5GB for free, so if you don't want to lose those priceless pictures of your grand kids you should really upgrade to 1TB! Have you checked out our application store yet? And don't worry, if you say no to any of these questions we'll keep pestering you about them with notifications, fullscreen interstitials and banners in the settings application until your brain dissolves to mush! I have a collection of about a million PDAs, from the early days up until the very fanciest models from right around when the iPhone and Android started taking off. Of course, they're in storage so virtually always out of battery, but when I do turn any of them on, their onboarding process couldn't be simpler. Tap a few locations on the screen to calibrate the touch layer, set the date and time, and that's it - you're at the home screen ready to go. I wish modern smartphones were similar. I wish the greedy bean counters were told to pound sand and the user interface specialists took over again. My wife and I have two young boys, 3 and almost 5. One day, I'll be the out-of-touch dad or grandpa and I'll need their help to set up my brain implant chip or whatever. I hope it won't involve upsells for streaming services.