The original iMac entered a computing world that was in desperate need of a shake-up. After the wild early days of the personal computer revolution, things had become stagnant by the mid-1990s. Apple had spent a decade frittering away the Mac’s advantages until most of them were gone, blown out of the water by the enormous splash of Windows 95. It was the era of beige desktop computers chained to big CRT displays and other peripherals. In 1997, Steve Jobs returned to an Apple that was at death’s door, and in true Princess Bride style, he rapidly ran down a list of the company’s assets and liabilities. Apple didn’t have a wheelbarrow or a holocaust cloak, but it did have a young industrial designer who had been experimenting with colors and translucent plastic in Apple’s otherwise boring hardware designs. The original iMac is simply a delightful machine. I vividly remember that the reception and administrative workers at the orthodontic department at the hospital in Alkmaar used them, and teenage me would peek past the reception desk to catch glimpses of the colourful machines. I still love the original iMac.

FreeBSD is a compelling and cutting-edge operating system that provides a wealth of features and advantages. FreeBSD’s deep OpenZFS integration, completely customizable packaging, and the ability to manage a huge fleet with a small team make it a clear contender for consideration in your next infrastructure build. This one’s written by a company that, among other things, sells FreeBSD and OpenZFS support, so take that into account when reading the article.

A necessary correction to an earlier post: support for Haiku has not been upstreamed into GCC. From the Haiku development mailing list: It is definitely our goal to get Haiku’s GCC toolchain upstream, and that commit does indeed nudge us a little in that direction… However it’s a small portion of a larger commit adding architecture support. Good to have this cleared up.

Debate continues to rage over the federal Kids Online Safety Act (KOSA), which seeks to hold platforms liable for feeding harmful content to minors. KOSA is lawmakers’ answer to whistleblower Frances Haugen’s shocking revelations to Congress. In 2021, Haugen leaked documents and provided testimony alleging that Facebook knew that its platform was addictive and was harming teens—but blinded by its pursuit of profits, it chose to ignore the harms. But when Blumenthal introduced KOSA last year, the bill faced immediate and massive blowback from more than 90 organizations—including tech groups, digital rights advocates, legal experts, child safety organizations, and civil rights groups. These critics warned lawmakers of KOSA’s many flaws, but they were most concerned that the bill imposed a vague “duty of care” on platforms that was “effectively an instruction to employ broad content filtering to limit minors’ access to certain online content.” The fear was that the duty of care provision would likely lead platforms to over-moderate and imprecisely filter content deemed controversial—things like information on LGBTQ+ issues, drug addiction, eating disorders, mental health issues, or escape from abusive situations. Since then, Ars Technica reports in this detailed article, the law does seem to have been amended in positive, constructive ways – but not nearly far enough to make it workable and not prone to massive abuse. Sadly, it seems the bill is poised to pass, so we’ll have to see what the eventual, final version will look like.

Certain font-related CSS properties will render your site completely inaccessible if their value is declared using pixels even once. Just read it and absorb the information.

There’s no denying that the browser is the single-most important application on any operating system, whether that be on desktops and laptops or on mobile devices. Without a capable, fast, and solid browser, the usefulness of an operating system decreases exponentially, to the point where I’m quite sure virtually nobody’s going to use an operating system for regular, normal use if it doesn’t have a browser. Having an at least somewhat useable browser is what elevates an operating system from a hobby toy to something you could use for more than 10 minutes as a fun novelty. The problem here is that making a capable browser is actually incredibly hard, as the browser has become a hugely capable platform all of its own. Undertaking the mammoth task of building a browser from scratch is not something a lot of people are interested in – save for the crazy ones – made worse by the fact that competing with the three remaining browser engines is basically futile due to market consolidation and monopolisation. Chrome and its various derivatives are vastly dominant, followed by Safari on iOS, if only because you can’t use anything else on iOS. And then there’s Firefox, trailing far behind as a distant third – and falling. This is the environment desktop Linux distributions find themselves in. For the longest time now, desktop Linux has relied virtually exclusively on shipping Firefox – and the Mozilla suite before that – as their browser, with some users opting to download Chrome post-install. While both GNOME and KDE nominally invest in their own two browsers, GNOME Web and Falkon, their uptake is limited and releases few and far between. For instance, none of the major Linux distributions ship GNOME Web as their default browser, and it lacks many of the features users come to expect from a browser. Falkon, meanwhile, is updated only sporadically, often going years between releases. Worse yet, Falkon uses Chromium through QtWebEngine, and GNOME Web uses WebKit (which are updated separately from the browser, so browser releases are not always a solid metric!), so both are dependent on the goodwill of two of the most ruthless corporations in the world, Google and Apple respectively. Even Firefox itself, even though it’s clearly the browser of choice of distributions and Linux users alike, does not consider Linux a first-tier platform. Firefox is first and foremost a Windows browser, followed by macOS second, and Linux third. The love the Linux world has for Firefox is not reciprocated by Mozilla in the same way, and this shows in various places where issues fixed and addressed on the Windows side are ignored on the Linux side for years or longer. The best and most visible example of that is hardware video acceleration. This feature has been a default part of the Windows version since forever, but it wasn’t enabled by default for Linux until Firefox 115, released only in early July 2023. Even then, the feature is only enabled by default for users of Intel graphics – AMD and Nvidia users need not apply. This lack of video acceleration was – and for AMD and Nvidia users, still is – a major contributing factor to Linux battery life on laptops taking a serious hit compared to their Windows counterparts. The road to even getting here has been a long, hard, and bumpy one. For years and years now, getting video acceleration to work on Firefox for Linux was complicated and unreliable, with every release of the browser possibly changing what flags you needed to set, and sometimes it would just stop working for several releases in a row altogether, no matter what you did. There’s a venerable encyclopaedia of forum messages, blog posts, and website articles with outdated instructions and Hail Mary-like suggestions for users trying to get it to work. Conventional wisdom would change with every release, and keeping track of it all was a nightmare. It’s not just hardware accelerated video decoding. Gesture support has taken much longer to arrive on the Linux version than it did on the Windows version – things like using swipes to go back and forward, or pinch to zoom on images. Similarly, touchscreen support took a longer time to arrive on the Linux version of Firefox, too. Often, such features could be enabled with about:config incantations for years before becoming enabled by default, at least, but that’s far from an ideal situation. With desktop Linux trailing both Windows and macOS in popularity, there’s nothing unexpected or inherently malicious about this, and the point of the previous few paragraphs is not to complain about the state of Firefox for Linux or to suggest Mozilla transfers precious resources from the Windows and macOS versions to the Linux version. While I obviously wouldn’t complain if they did so, it wouldn’t make much sense. The real reason I’m highlighting these issues is that if Firefox for Linux is already treated as a third wheel today, with Mozilla’s current financial means and resources, what would happen if Mozilla saw a drastic reduction in its financial means and resources? Firefox is not doing well. Its market share has dropped radically over the years, and now sits at a meagre 3% on desktops and laptops, and a negligible 0.5% on mobile. Chrome and to a lesser extent Safari have trampled all over the venerable browser, to a point where it’s effectively an also-ran for Linux/BSD users, and a few more nerds on other platforms. I’m not saying this to disparage those who use Firefox – I’m one of them – but to underline just how dire Firefox’ current market position really is. This shrinking market share must already be harming the development and future prospects of Firefox, especially if the slide continues. The declining market share is far from the biggest problem, however. The giant sword of Damocles dangling above Firefox’ head are Mozilla’s really odd and lopsided revenue sources. As most of us are probably aware, Mozilla makes most of

Beta 5 is our third Platform Stable Android 14 release, which means that the developer APIs and all app-facing behaviors are final for you to review and integrate into your apps, and you can publish apps on Google Play targeting Android 14’s SDK version 34. It includes the latest fixes and optimizations, giving you everything you need to complete your testing. The final release is quite close now.

It’s Back to School season, so grab yourself a brand new discounted computer and let’s get back to COSMIC class! Our new, not yet released Rust-based desktop environment for Pop!_OS and other Linux distros is filling out with some essential systems that cater the DE to both users and developers alike. Customization is one of our main focuses for COSMIC, and was a huge focus for us in August, too. There’s a lot of cool stuff in this update about COSMIC. First and foremost, customisation is important, so they’ve effectively implemented something similar to Android’s Material You theming engine, where the desktop environment will automatically determine derived colours that match the colour you’ve chosen as to maintain readability, contrast, and so on. You can also set the density of the interface, and how ’rounded’ everything looks. Sadly, there’s no word on actual theming in there, but they do mention that “nothing in the components of the design system is meant to be hard-coded”, so hopefully this means custom themes that radically alter the look of the UI are possible. There’s also a new API for application developers. We added an application API to the libcosmic widget library to provide a framework for developing applications and applets in COSMIC DE. It automates integration with COSMIC theme support, along with Wayland protocols, COSMIC’s configuration back-end, and common application elements like header bars and navigation. For application developers, this means convenient development without having to worry about managing the low-level desktop and window manager integrations. For us, this ensures consistency across COSMIC applications and applets. COSMIC is shaping up nicely, and I can’t wait to try it out.

Developers of the BeOS-inspired Haiku operating system have long been carrying patches for supporting the GNU Compiler Collection (GCC) on their platform while this week the code was upstreamed for GCC 14. This commit to mainline GCC git adds support for the Haiku operating system. Excellent news, and well-deserved.

ARM Ltd has been dominating the Android world for the better part of the last decade, with their 7-series cores at the forefront of their success. Throughout the late 2010s, the Cortex A73, A75, and A76 steadily iterated on performance while maintaining excellent energy efficiency. Qualcomm, and then Samsung decided licensing ARM’s cores would be easier than trying to outdo them. Apple remained a notable rival, but their core designs were not available outside a closed-off ecosystem. By the time Cortex A78 came around, ARM had no real competition. ARM’s Cortex A710 continues that dominance. It takes A78’s successful formula and tweaks it to improve performance and efficiency. Efficiency is especially prioritized, with the core seeing cuts in some areas as ARM tries to get more done with less power. A710 claims to provide a 30% uplift in power efficiency or a 10% performance increase within a fixed power envelope when compared to a A78 core with half as much L3 cache. Alongside these improvements, A710 gains Armv9-A and SVE support. A deep dive into ARM’s latest core.

CIQ, Oracle and SUSE today announced their intent to form the Open Enterprise Linux Association (OpenELA), a collaborative trade association to encourage the development of distributions compatible with Red Hat Enterprise Linux (RHEL) by providing open and free Enterprise Linux (EL) source code. The formation of OpenELA arises from Red Hat’s recent changes to RHEL source code availability. In response, CIQ, Oracle and SUSE are collaborating to deliver source code, tools and systems through OpenELA for the community. Good initiative, except for the involvement of Oracle. I understand why they are part of this endeavour, but I see Oracle as entirely antithetical to open source and everything it stands for, so seeing them weasel their way into this debate pretending to be a good guy feels unpleasant.

I doubt there’s an operating system out there that we have more preconceived notions about than Chrome OS, and most of those notions will be quite negative. Since I had little to no experience with Chrome OS, I decided it was time to address that shortcoming, and install Chrome OS Flex on my Dell XPS 13 9370 (Core i7-8550U, 16GB of RAM, 4K display), and see if there’s any merit in running Google’s desktop operating system. Installing Chrome OS Flex is a breeze. While Google warns you to stick to explicitly supported hardware, my XPS 13 9370, although not listed as officially supported, had no issues installing the operating system. The only things not working are the same things that don’t work in other Linux distributions either – the Goodix fingerprint reader (screw Dell for choosing Goodix), and the Windows Hello-focused depth camera. The latter can be made to work in Linux, but clearly Google did not go through the trouble of making it work out of the box. Everything else just worked, as you would expect from any other Linux distribution. Using an operating system primarily designed around websites as applications is a bit weird at first, but I was surprised how quickly I got used to it. Now, it is important to note that I do not do many complicated or demanding tasks on my laptop – I write OSNews articles, watch YouTube, browse around the web, and perform similar light tasks – so I’m not exactly pushing the limits of what a website-focused operating system can do. In fact, to my utter surprise, I found myself enjoying using Chrome OS quite a bit. Running websites as applications – both PWAs and plain websites opened in their own chromeless windows – has come a long way, and in many cases I barely realised I wasn’t running “native” applications. I discovered that turning websites I use often, like the OSNews WordPress backend, Wikipedia, Google Maps, and so on, into standalone applications with entries in the applications menu and dock was actually quite pleasant. Chrome OS allows you to choose if an application should run in a browser tab, or in a separate window without any browser chrome, and you can choose to open links to those websites in either a new regular tab, or in the aforementioned separate window. It all works surprisingly well – much better than I expected. Chrome OS also has quite a few features you wouldn’t expect from something mostly aimed at budget computers. It has support for various trackpad gestures, and they are very smooth and nice to use. For instance, you can swipe up with three fingers to gain an Exposé-like overview of all your running applications, which also gives you access to the virtual desktops feature. Chrome OS also comes with a few true native applications, like a surprisingly capable file manager and text editor. Other modern staples like a night light feature to reduce late-night eye strain, system-wide search, system-wide spellcheck, and others are also present. You can go deeper, too. Chrome OS comes with a complete Linux environment to run standard Linux applications. Once turned on, you gain access to a standard terminal you can use to access it, and the Linux environment’s storage becomes available in the file manager. I used it to install the regular Linux version of Steam, as well as the Flatpak of the Steam Link remote play application. Both worked just fine, although the Steam application ran extremely slow, and the Steam Link application did not seem to have access to the network, so it couldn’t find my Steam PCs. I’m chalking that one up to odd interactions between Flatpak and Chrome OS’ Linux environment. You can also link your Android device to your Chrome OS machine, giving you access to your notifications, Chrome tabs, and various toggles on your phone, such as the hotspot toggle. Sadly, this feature seems quite limited – if I get a Discord or WhatsApp notification and click it, nothing happens – even though I have both Discord and WhatsApp installed and running on Chrome OS, the operating system doesn’t seem to be able to link the phone’s notifications to the relevant installed applications, rendering the feature kind of pointless. No follow-through Chrome OS being a Google product, I was not entirely surprised to see a serious lack of follow-through in the operating system. Take the user interface’s dark mode, for instance – it’s half-baked and grossly incomplete. Various applications running in dark mode will inexplicably have a bright white titlebar, including GMail, the quintessential and flagship Google web app. I have to use an unlisted extension to fix this, but said extension is Manifest version 2, which Chrome OS warns you is deprecated and will stop working “in 2023”. It gets worse, though. Many of the most prominent Google applications do not support dark mode at all. Google Docs, Sheets, and Slides are all only available in bright white. Google Photos, an application that would undoubtedly benefit from a dark mode, does not support it. Google Calendar, Google Drive, Google Translate, and countless others are all only available in eye-searing white. Then there’s the more esoteric issues that stem from the fact you’re effectively running web sites in browser windows. If you’re familiar with Google’s various web applications, you’ll know they have this grid icon in the top-right which opens a grid menu with the various other Google web applications. While such a menu might make sense while using a web browser on other operating systems, it’s entirely confusing on Chrome OS, and breaks the operating system’s UI in interesting ways. Aside from this menu taking up valuable real estate, it also doesn’t work in the way you expect it to, since it does not respect the window-or-tab setting from Chrome OS itself. Say I have Google Docs set to to open in a chromeless window, and I launch it from the grid menu inside Google Drive, Docs will

The UK’s elections watchdog has revealed it has been the victim of a “complex cyber-attack” potentially affecting millions of voters. The Electoral Commission said unspecified “hostile actors” had managed to gain access to copies of the electoral registers, from August 2021. Hackers also broke into its emails and “control systems” but the attack was not discovered until October last year. The watchdog has warned people to watch out for unauthorised use of their data. That seems like a state-level attack, and such data could easily be used for online influence campaigns during elections, something that is happening all over the western world right now. I wonder just how bad the hack actually was? “Millions of voters” sounds bad, but… The commission says it is difficult to predict exactly how many people could be affected, but it estimates the register for each year contains the details of around 40 million people. Holy cow.

To round out our options for supporting OSNews, we’re introducing support for Liberapay, an open source alternative to Patreon. OSNews is all about promoting choice – in operating systems, in devices, in software – so giving readers the option of donating through an open source platform, located in the European Union, fits within our values. If you want to donate this way, you can go to our Liberapay page. Liberapay joins the other ways you can support OSNews: our Patreon, our Ko-Fi, and our official merch store.