fidzu : Operating Systems

Volker Hilsheimer, chief maintainer of the Qt project, says he has learned lessons from the painful Qt 5 to Qt 6 transition, the importance of Qt Bridges for using Qt from any language, and the significance of the relationship with the Linux KDE desktop. ↫ Tim Anderson at Dev Class Qt plays a significant role in the open source desktop world in particular, because it's the framework KDE uses. Hilsheimer notes that KDE's role in the Qt community is actually quite important, because not only is it a source of people learning how to use Qt and who can thus make contributions to the project, KDE also tends to use the latest Qt versions, creating a lot of confidence among the wider Qt community to also adopt the latest versions. The relationship with KDE and Qt is an interesting one, and sometimes leads to questions about the future availability of the open source edition of Qt since the Qt Company licenses Qt under a dual-license structure (both open and proprietary). To avoid any uncertainty, KDE and Qt have an agreement that covers pretty much every possible scenario and which is worded to ensure the availability of Qt as an open source framework. KDE, through the KDE Free Qt Foundation, has a number rights and options to ensure the availability of Qt as an open source framework. I'm no lawyer, so I might get some of the details wrong, but the main points are that if the Qt Company ever decides to discontinue the open source edition of Qt, the KDE Free Qt Foundation has the right to release Qt under a BSD-style license within 12 months. The same applies to any addition to Qt which are not released as open source; they must be released under an open source license within 12 months of initial release. This agreement remains valid in the case of buyouts, mergers, or bankruptcies. This agreement has existed in one form or another since the late '90s, and has survived Qt being owned by Nokia and Digia, as well as various other organisational changes. Despite the issue of Qt's ownership coming up every now and then, the agreement is pretty airtight, and considering its longevity there's no reason to be worried about it at all. Still, this structure is clearly more complex and less straightforward than, say, the status of GTK and its relationship to GNOME, so it's not entirely unreasonable the issue comes up every now and then. I wonder if we'll ever see this situation become less complex, without the need for special agreements. While it wouldn't make a practical difference, it would make things less… Legalese.

20 May 2025 2:28pm GMT

Mainframes still play a vital role in today, providing extremely high uptime and low latency for financial transactions. Telum II is IBM's latest mainframe processor, and is designed unlike any other server CPU. It only has eight cores, but runs them at a very high 5.5 GHz and feeds them with 360 MB of on-chip cache. IBM also includes a DPU for accelerating IO, along with an on-board AI accelerator. Telum II is implemented on Samsung's leading edge 5 nm process node. IBM's presentation has already been covered by other outlets. Therefore I'll focus on what I feel like is Telum (II)'s most interesting features. DRAM latency and bandwidth limitations often mean good caching is critical to performance, and IBM has a often deployed interesting caching solutions. Telum II is no exception, carrying forward a virtual L3 and virtual L4 strategy from prior IBM chips. ↫ Chester Lam at Chips and Cheese If you've been keeping track, you can possibly deduce that I'm bit of a sucker for IBM's mainframes and big POWER machines. These Telum II processors are absolutely wild.

19 May 2025 10:27pm GMT

I recently learned something that blew my mind; you can run a full desktop Linux environment on your phone. That's a graphical environment via X11 with real window management and compositing, Firefox comfortably playing YouTube (including working audio), and a status bar with system stats. It launches in less than a second and feels snappy. ↫ Hold the Robot In and of itself, this is a neat trick most of us are probably aware of. Running a full Linux distribution on an Android phone using chroot is an awesome party trick, but I doubt many people take this concept to its logical conclusion by connecting it up to a display, keyboard, and mouse, and use it as their mobile workstation. Well, the author of this article did, and he took it even one step further by replacing the display part of the logical conclusion with AR glasses. The AR glasses in question were a pair of Xreal Air 2 Pro, which put a 120Hz 1080p display in front of your eyes using Sony micro-OLED panels. This will create the illusion of a 130″ screen with a 46° field of view, from a pair of glasses that honestly do not feel that much more massive than regular sunglasses or some of the thicker glasses frames some people like. I'm honestly kind of impressed this is possible these days. Add in a keyboard and mouse, and you've got a mobile workstation that takes up very little space, especially since you're carrying your phone with you at all times anyway. Of course, you have to be comfortable with using Linux - no Windows or macOS here - and the software side of the equation requires more setup and fiddling than I thought it would, but the end result is exactly like using a regular Linux desktop, but on your phone and a pair of AR glasses instead of on a laptop or desktop. If I had the cash to throw around on fun side projects like this (you can help with that, actually, through Ko-Fi donations), I would totally order a pair of these Xreal glasses to try this out.

19 May 2025 10:22pm GMT

Today we're very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo: Will this be Open Source? · Issue #1 · microsoft/WSL. That means that the code that powers WSL is now available on GitHub at Microsoft/WSL and open sourced to the community! You can download WSL and build it from source, add new fixes and features and participate in WSL's active development. ↫ Pierre Boulay at the Windows Blogs Windows Subsystem for Linux seems like a relatively popular choice for people who want a modern, Linux-based development environment but are stuck using Windows. I'm happy to see Microsoft releasing it as open source, which is no longer something to be surprised by at this point in time. It leaves one to wonder how long it's going to be before more parts of Windows will be released as open source, since it could allow Microsoft's leadership to justify some serious job cuts. I honestly have no idea how close to the real thing Windows Subsystem for Linux is, and if it can actually fully replace a proper Linux installation, with all the functionality and performance that entails. I'm no developer, have no interest in Windows, so I've never actually tried it. I'd love to hear some experiences from all of you. Aside from releasing WSL as open source, Microsoft also released a new command-line text editor - simply called Edit. It's also open source, in its early stages, and is basically the equivalent of Nano. It turns out 32bit versions of Windows up until Windows 10 still shipped with the MS-DOS Editor, but obviously that one needed a replacement. It already has support for multiple documents, mouse support, and a few more basic features.

19 May 2025 7:17pm GMT

Every so often people yearn for a lost (1980s or so) era of 'single user computers', whether these are simple personal computers or high end things like Lisp machines and Smalltalk workstations. It's my view that the whole idea of a 1980s style "single user computer" is not what we actually want and has some significant flaws in practice. ↫ Chris Siebenmann I think the premise of this entire article is flawed, and borders on being a strawman argument. I honestly don't think there's many people out there who genuinely and seriously want to use an '80s home computer for all their computing tasks, but this article seems to think that there are. Virtually every single person expressing interest in and a desire for classic computers does so from a point of nostalgia, as a learning experience, or as a hobby. They're definitely not interested in using any of those '80s machine to do their banking or to collaborate with their colleagues. Additionally, the problems and issues people have with modern computing platforms is not that they are too complex, but that they are no longer designed with the user in mind. Windows, macOS, iOS; they're all first and foremost designed to extract money from you through ads, upsells, nag screens, and similar anti-user features, and it's those things that people are sick of. Coincidentally, they are all things we didn't have to deal with back in the '80s and '90s. In other words, remove the user-hostility from modern operating systems, and people wouldn't complain about them so much. Which seems rather obvious, doesn't it? It's why using a Linux desktop like Fedora is such a breath of fresh air. There's no upsells for cloud storage or streaming services, no restrictions on what I can and cannot install to protect some multitrillion euro company's revenue streams, no ads and nag screens infesting my operating system - it's just an operating system waiting for me to tell it what it do, and then it does it. It's wild how increasingly revolutionary that's becoming. Whenever I am forced to interact with Windows 11 or whatever the current version of macOS is, I feel such a profound and deep sadness for what they've become, and it seems only natural to me that this sadness is fueling a longing for back when these systems weren't so user-hostile.

19 May 2025 2:21pm GMT

Tuxguitar is a quite powerful application written in a mixture of Java / C. It is able to render a score in real time either via Fluidsynth or via pure MIDI. The development of Tuxguitar started in 2008 on Sourceforce and after a halt in 2022, the project restarted on Github and is still actively developed. The goal of this article is to try to render a score via Tuxguitar, and various other applications connected to Tuxguitar, via Jack or Pipewire-Jack. The score used throughout this article will be The Pursuit Of Vikings by the band Amon Amarth. It has 2 guitars, a bass and a drum track. ↫ Yann Collette at Fedora Magazine If you're into audio production and are considering using Linux for your audio needs, this article is a good starting point.

19 May 2025 2:02pm GMT

Last time, we looked at the legacy icons in progman.exe. But what about moricons.dll? Here's a table of the icons that were present in the original Windows 3.1 moricons.dll file (in file order) and the programs that Windows used the icons for. As with the icons in progman.exe, these icons are mapped from executables according to the information in the APPS.INF file. ↫ Raymond Chen These icons age like a fine wine. They're clear, well-designed, easy to read, and make extraordinary good use of the limited amount of available pixels. Icons from Mac OS, BeOS, OS/2, and a few others from the same era also look timeless, and I wish modern designers learned a thing or two from these.

18 May 2025 11:40pm GMT

You may not have heard of the "Transparency & Consent Framework", but you've most likely interacted with it, probably on a daily basis. The TCF is used by 80% of the internet to obtain "consent" from users to collect their data and share it among advertisers - you know, the cookie popups. In a landmark EU ruling yesterday, the TCF has been declared to violate the GDPR, making it illegal. For seven years, the tracking industry has used the TCF as a legal cover for Real-Time Bidding (RTB), the vast advertising auction system that operates behind the scenes on websites and apps. RTB tracks what Internet users look at and where they go in the real world. It then continuously broadcasts this data to a host of companies, enabling them to keep dossiers on every Internet user. Because there is no security in the RTB system it is impossible to know what then happens to the data. As a result, it is also impossible to provide the necessary information that must accompany a consent request. ↫ Irish Council for Civil Liberties It's no secret that cookie consent popups do not actually comply with the GDPR, and that they are not even necessary if you simply don't do any cross-site sharing of personal information. It seems that this ruling confirms this in a legal sense, forcing the advertising industry to come up with a new, better system. On top of that, every individual company that participated in this scheme is now liable for fines and damages. Complaints coordinated by Johnny Ryan, Director of Enforce at the Irish Council for Civil Liberties, prompted the ruling. He said: Today's court's decision shows that the consent system used by Google, Amazon, X, Microsoft, deceives hundreds of millions of Europeans. The tech industry has sought to hide its vast data breach behind sham consent popups. Tech companies turned the GDPR into a daily nuisance rather than a shield for people. ↫ Irish Council for Civil Liberties The problem here is not so much the clarity of applicable laws and regulations, but the cost and effectiveness of enforcement. If it takes years of expensive and complex legal proceedings to bring a company that violates the GDPR to heel, is it really an effective legal framework? Especially when you take into account just how many companies, big and small, there are that violate the GDPR? OSNews uses a cookie popup and displays advertising, something we have to do to gain a little bit of extra income - but I'm not happy about it. Our ads don't provide us with much income, perhaps about €150-200, but that's still a decent enough chunk of our income pie that we need it. I would greatly prefer we turn off these ads altogether, but in order to be able to afford that, we'd need to up our Patreon income. OSNews Patreons get an ad-free version of OSNews. That's a long and slow process, especially with the current economic uncertainty making people reconsider their expenses. Disabling our ads altogether for everyone once we're fully reader-funded is still my end goal, but until the world around us settles down a bit, that's a little while off. If you want to speed this process up - you can become an OSNews Patreon and enjoy an ad-free OSNews today.

16 May 2025 11:44am GMT

I generally don't pay attention to the releases of programming languages unless they're notable for some reason or another, and I think this one qualifies. Rust is celebrating its ten year anniversary with a brand new release, Rust 1.87.0. This release adds anonymous pipes to the standard library, inline assembly can now jump to labeled blocks in Rust code, and support for the i586 Windows target has been removed. Considering Windows 7 was the last Windows version to support i586, I'd say this is fair. You can update to the new version using the rustup command, or wait until your operating system adds it to its repository if you're using a modern operating system.

16 May 2025 7:51am GMT

Accessibility in the software world is a problem in general, but it's an even bigger problem on open source desktops, as painfully highlighted by this excellent article detailing the utterly broken state of accessibility on Linux. Reading the article is soul-crushing as it starts to dawn on you just how bad the situation really is for those among us who require accessibility features, making it virtually impossible for them to switch to Linux. This obviously has to change, and it just so happens that both on the GTK/GNOME and KDE side, recent work on accessibility has delivered some valuable results. Starting with GTK and GNOME, the framework has recently merged the AccessKit backend with GTK 4.18, which enables accessibility features when running GTK applications on Windows and macOS. On Linux, GTK still defaults to at-spi, but I'm sure this will change eventually too. Another major improvement are the special keyboard shortcuts normally provided by the screen reader Orca. Support for these was in the works for a while but incomplete, but now this work has been completed, and the new shortcuts ship as part of GNOME 48. Accessibility support for GNOME Web has been greatly improved as well, and Elevado is a new tool that shows you what applications expose on the a11y bus. There's a ton additional, smaller changes too. On the KDE side, a number of accessibility improvements have been implemented as part of the project's goal to improving input handling. You can now use the numerical pad's arrow keys to move the mouse cursor, there's a new 3-finger gesture to invoke the desktop zoom accessibility feature, keyboard navigation in general has been improved in a wide variety of places in KDE, and a whole bunch more improvements. In addition, a number of financial grants have been given to developers working on accessibility in KDE, such as a project to make file management-related features - think open/save dialogs, Dolphin, and so on - fully accessibly, and projects to make touchpad and screen gestures fully customisable. Accessibility is never really "done" or "perfect", but there's definitely an increasing awareness among the two major open source desktops of just how important it is. A few confounding factors - like the switch to Wayland or the complicated history of audio on Linux - have actually hurt accessibility, and it's only now that things are starting to look up again. However, as anyone with reduced vision or auditory problems can tell you, Linux and the open source desktop still has a very long way to go.

15 May 2025 10:00pm GMT

Following rumors, Xiaomi today announced that it will launch its very own chip for smartphones later this month. The "XRING 01" is a chip that the company has apparently been working on for over 10 years now. Details about the chip are scarce so far, but GizmoChina points to recent leaks that suggest the chip is built on a 4nm process through TSMC. The chip supposedly has a 1+3+4 layout and should lag just a bit behind Snapdragon 8 Elite and Dimensity 9400 in terms of raw horsepower, sounding familiar to Google's work with Tensor chips. ↫ Ben Schoon at 9To5Google I like this. Having almost every Android device use Qualcomm's chips is not good for fostering competition, and weakens Android OEMs' bargaining position. If we have more successful SoC makers, consumers will not only gain access to a wider variety of chips that may better suit their needs, it will also force Qualcomm to lower its prices, compete better, or both. Everybody wins. Well, except Qualcomm, I guess.

15 May 2025 7:52pm GMT

You'd almost forget, but aside from the enterprise-focused variant of Solaris for which Oracle sells support contracts, the company has also nominally maintained and released a version of Solaris aimed at non-production use and enthusiasts. This version, called Solaris CBE or Common Build Environment, has always been free to download and use, but since it was last updated all the way back in early 2022, you'd be forgiven for having forgotten all about it. Today, though, Oracle has finally released a new version of Solaris CBE, after three years of silence. The Common Build Environment (CBE) release for Oracle Solaris 11.4 SRU 81 is now available via "pkg update" from the release repository or by downloading the install images from the Oracle Solaris Downloads page. As with the first Oracle Solaris 11.4 CBE, this is licensed for free/open source developers and non-production personal use, and this is not the final, supported version of the 11.4.81 SRU, but the pre-release version on which the SRU was built. It contains all of the new features and interfaces, but not all of the final rounds of bug fixes, from the 11.4.81 SRU. The previous version was the CBE for 11.4.42, so there's more than 3 years worth of changes between these two releases. If you wanted to read about the changes in every intervening SRU, you can find the monthly SRU release announcements for every SRU, and the What's New summaries for each quarterly feature release starting with SRU 63, on the Oracle Solaris blog. Some FOSS version updates are also listed in Oracle Solaris 11.4 Bundled Software Updates. You can also find posts about some of the new features from the SRUs on Joerg Moellenkamp's blog and Marcel Hofstetter's blog. ↫ Alan Coopersmith and Jan Pechanec With three years of changes, updates, and fixes to talk about, it's no surprise there's a lot of things this new release covers, and credit to Oracle: the blog post announcing this new release is incredibly detailed, lists a ton of the changes in great detail, and is definitely required reading if you're interested in trying this release out for yourself. I'm definitely tempted, even if it's Oracle. Solaris 11.4 SRU 81 CBE comes with much more recent versions of the free and open source tools and frameworks you've come to expect, like updated versions of GCC, LLVM/clang, tons of programming languages like Python, Perl, and Rust, as well as updates to all the related toolchain components. The CTF (Compact C Type Format) utilities (ctfconvert, ctfdump, and ctfmerge), used to build Solaris itself and crucial for tools like DTrace, have also been updated, and now reside in /usr/bin. These updates are joined by a massive number of other, related low-level changes. For desktop users, GNOME has been updated from the veritably ancient GNOME 3.38 to GNOME 45 (current is 48.1), which is a big jump for Solaris desktop users. Firefox and Thunderbird jump from 91 ESR to 128 ESR, which should deliver a much-improved browsing and email experience. All of this graphical desktop use is powered by version 21.1 of the X server, Mesa 21.3.8, and version 470.182 of the NVIDIA driver. Grub has been updated to version 2.12, and thanks to a new secure boot shim, users no longer have to make any changes to secure boot settings, as Solaris will always default to installing the secure boot image. This is just a small selection of all the changes, and it seems Oracle is planning on releasing these CBE versions more often from here on out, as they say this release contains a ton of preparatory work for changes in upcoming releases, "which should come more often than once every three years going forward". Do note that while Solaris CBE releases are free for non-production use, they're not open source.

14 May 2025 11:45pm GMT

I don't know anything about hiring processes in Silicon Valley, or about hiring processes in general since I've always worked for myself (and still do, running OSNews, relying on your generous Patreon and Ko-Fi support), so when I ran into this horror story of applying for a position at a Silicon Valley startup, I was horrified. Apparently it's not unheard of - it might even be common? - to ask applicants for a coding position to develop a complex application, for free, without much guidance beyond some vague, generic instructions? In this case, the applicant, Jose Vargas, was applying for a position at Kagi, the search startup with the, shall we say, somewhat evangelical fanbase. After applying, he was asked to develop a complete e-mail client, either as a TUI/CLI or a web application that can view and send emails, using a fake or a real backend, which can display at least plaintext e-mails. None of this was going to be paid labour, of course. Vargas started out by sending in a detailed proposal of what he was planning to create, ending with the obvious question what kind of response he'd get if he actually implemented the detailed proposal. He got a generic response in return, without an answer to that question, but he set out to work regardless. In the end, it took him about a week to complete the project and send it in. He eventually received a canned rejection notice in response, and after asking for clarification the hiring manager told him they wanted something "simpler and stronger", so he didn't make the cut. I'm not interested in debating whether or not Vargas was suited for the position, or if the unpaid work he sent in was any good. What I do want to talk about, though, is the insane amount of unpaid labour applicants are apparently asked to do in Silicon Valley, the utter lack of clear and detailed instructions, and how the hiring manager didn't answer the question Vargas sent in alongside his detailed proposal. After all, the hiring manager could've saved everyone a ton of time by letting Vargas know upfront the proposal wasn't what Kagi was looking for. Everything about this feels completely asinine to me. As a (former) translator, I'm no stranger to having to do some work to give a potential client an idea of what my work looks like, but more than half a page of text to translate was incredibly rare. Only on a few rare occasions did a prospective client want me to translate more than that, and in those cases it was always as paid labour, at the normal, regular rate. For context, half a page of text is less than half an hour of work - a far cry from a week's worth of unpaid labour. I've read a ton of online discourse about this particular story, and there's no clear consensus on whether or not Vargas' feelings are justified. Personally, I find the instructions given by Kagi overly broad and vague, the task of creating an email client to be overly demanding, and the canned ("AI"?) responses by the hiring manager insulting - after sending in such a detailed proposal, it should've been easy for a halfway decent hiring manager to realise Vargas might not be a good fit for the role, and tell him so before he started doing any work. Kagi is fully within its right to determine who is and is not a good fit for the company, and who they hire is entirely up to them. If such stringent, demanding hiring practices are par for the course in Silicon Valley, I also can't really fault them for toeing the industry line. The hiring manager's behaviour seems problematic, but everyone makes mistakes and nobody's perfect. In short, I'm not even really mad at Kagi specifically here. However, if such hiring practices are indeed the norm, can I, as an outsider, just state the obvious? What on earth are you people doing to each other over there in Silicon Valley? Is this really how you want to treat potential applicants, and how you, yourself, want to be treated? Imagine if a someone applies to be a retail clerk at a local supermarket, and the supermarket's hiring manager asks the applicant to work an entire week in the store, stocking shelves and helping shoppers, without paying the person any wages, only to deny their application after the week of free labour is over? You all realise how insane that sounds, right? Why not look at a person's previous work, hosted on GitHub or any of its alternatives? Why not contact their previous employers and ask about their performance there, as happens in so many other industries? Why, instead of asking someone to craft an entire email client, don't you just give them a few interesting bugs to look at that won't take an entire week of work? Why not, you know, pay for their labour if you demand a week's worth of work? I'm so utterly baffled by all of this. Y'all developers need a union.

14 May 2025 9:51pm GMT

How do you get email to the folks without computers? What if the Post Office printed out email, stamped it, dropped it in folks' mailboxes along with the rest of their mail, and saved the USPS once and for all? And so in 1982 E-COM was born-and, inadvertently, helped coin the term "e-mail." ↫ Justin Duke The implementation of E-COM was awesome. You'd enter the messages on your computer, send it to the post office using a TTY or IBM 2780/3789 terminals, to Sperry Rand Univac 1108 computer systems at one of 25 post offices. Postal staff would print the messages and send them through the regular postal system to their recipients. The USPS actually tried to get a legal monopoly on this concept, but the FCC fought them in court and won out. E-COM wasn't the breakout success the USPS had hoped for, but it did catch on in one, unpleasant way: spam. The official-looking E-COM enevelopes from the USPS were very attractive to junk mail companies, and it was estimated that about six companies made up 70% of the total E-COM volume of 15 million messages in its second year of operation. The entire article is definitely recommended reading, as it contains a ton more information about E-COM and some of the other attempts by USPS to ride the coattails of the computer and internet revolution, including the idea to give every US resident an @.us e-mail address. Wild.

14 May 2025 7:41pm GMT

At the start of this year, Microsoft announced that, alongside the end of support for Windows 10, it would also end support for Office 365 (it's called Microsoft 365 now but that makes no sense to me) on Windows 10 around the same time. The various Office applications would continue to work on Windows 10, of course, but would no longer receive bug fixes, security plugs, and so on. Well, it seems Microsoft experienced some pushback on this one, because it just extended this end-of-support deadline for Office 365 on Windows 10 by an additional three years. To help maintain security while you transition to Windows 11, Microsoft will continue providing security updates for Microsoft 365 Apps on Windows 10 for three years after Windows 10 reaches end of support. These updates will be delivered through the standard update channels, ending on October 10, 2028. ↫ Microsoft support article The reality is that the vast majority of Windows users are still using Windows 10, and despite countless shady shenanigans and promises of "AI" bliss, there's relatively little movement in the breakdown between Windows 10 and Windows 11 users. As such, the idea that Microsoft would just stop fixing security issues and bugs in Office on Windows 10 a few months from now seemed preposterous from the outset, and that seems to have penetrated the walls of Microsoft's executives, too. The real question now is: will Microsoft extend the same courtesy to Windows 10 itself? The clock is ticking, there's only a few months left to go before support for Windows 10 ends, leaving 60-70% of Windows users without security fixes and updates. If they blinked with Office, why wouldn't they blink with Windows 10, too? Who dares to place a bet?

13 May 2025 10:17pm GMT

Let's dive into a peculiar bug in iOS. And by that I mean, let's follow along as Guilherme Rambo dives into a peculiar bug in iOS. The bug is that, if you try to send an audio message using the Messages app to someone who's also using the Messages app, and that message happens to include the name "Dave and Buster's", the message will never be received. ↫ Guilherme Rambo As I read this first description of the bug, I had no idea what could possibly be causing this. However, once Rambo explained that every audio message is transcribed by Apple into a text version, I immediately assumed what was going on: that "and" is throwing up problems because the actual name of the brand is stylised with an ampersand, isn't it? It's always DNS HTML, isn't it? Yes. Yes it is. MessagesBlastDoorService uses MBDXMLParserContext (via MBDHTMLToSuperParserContext) to parse XHTML for the audio message. Ampersands have special meaning in XML/HTML and must be escaped, so the correct way to represent the transcription in HTML would have been "Dave & Buster's". Apple's transcription system is not doing that, causing the parser to attempt to detect a special code after the ampersand, and since there's no valid special code nor semicolon terminating what it thinks is an HTML entity, it detects an error and stops parsing the content. ↫ Guilherme Rambo It must be somewhat of a relief to programmers and developers the world over that even a company as large and filled with talented people as Apple can run into bugs like this.

13 May 2025 10:05pm GMT