OSnews

Inkscape 1.0 has been released. A major milestone was achieved in enabling Inkscape to use a more recent version of the software used to build the editor’s user interface (namely GTK+3). Users with HiDPI (high resolution) screens can thank teamwork that took place during the 2018 Boston Hackfest for setting the updated-GTK wheels in motion. This is just the tip of the iceberg of this massive release.

We’ve already talked about snaps on Ubuntu, but it turns out it’s actually way worse than I initially thought. On the latest Ubuntu, if you try to download the .deb version of Chromium using either the Software Store or command line, it acts as an alias to installing the snap version! Essentially, Chromium snap is shoved down your throat even if you explicitly asked for the .deb version. This is not cool Ubuntu – just because Chromium may be easier to maintain as a snap app doesn’t justify this forced behavior. Snap applications auto-update and that’s fine if Ubuntu wants to keep systems secure. But it can’t even be turned off manually. Auto-updating of snaps can only be deferred at best, until at some point, like Windows, it auto-updates anyway. Even on metered connections, snaps auto-update anyway after some time. I only use Ubuntu on my laptop right now – my workstation and main PC run my distribution of choice, Linux Mint with Cinnamon – because the latest version of Ubuntu supports it better than the current Linux Mint release does. As soon as the next version of Mint is out, which will be based on the current Ubuntu version, I’m ditching Ubuntu right away. I don’t like snaps, FlatPaks, AppImage, or any of that other nonsense that do nothing but make a clean .deb/APT-based system more complicated than it needs to be. Debian’s package management system is incredibly robust and easy to fix in the unlikely event something does go wrong, so I simply do not have a need for additional application installation methods that I can’t control through APT. Ubuntu only barely just recovered from the Unity debacle, only for the project to now go down yet another route nobody is asking for.

The ReactOS Build Environment (RosBE), our curated set of compilers and build tools, has just received a major upgrade. After more than 7 years of using the same and now ancient GCC 4.7.2, ReactOS is finally going to be built with the help of a modern compiler (GCC 8.4.0). Among other things, the new version better detects programming mistakes like improperly sized buffers, and comes with improved error messages to pinpoint such mistakes to the corresponding position in code. It also adds support for the latest C and C++ standards, marking a first step towards the introduction of modern C++ concepts into ReactOS. That is one hell of an upgrade, and a much-needed one by the looks of it.

Enlightenment 0.24 Alpha 1 is shipping with an improved screenshot module, support for external monitor backlight/brightness controls, an improved restart experience, a smoother start-up thanks to using an I/O pre-fetch thread, switching over to BlueZ 5 for Bluetooth, and various other changes. Enlightenment was never a massively popular piece of software, but it seems that it has really fallen by the wayside recently. I vividly remember how 15-20 years ago, Enlightement was what you loaded up if you wanted to show off what desktop Linux could do

Valve has announced it’s ending support for macOS for SteamVR. SteamVR has ended OSX support so our team can focus on Windows and Linux. We recommend that OSX users continue to opt into the SteamVR branches for access to legacy builds. Users can opt into a branch by right-clicking on SteamVR in Steam, and selecting Properties… -> Betas. Apple announced SteamVR coming to the Mac at WWDC in 2017, so support from Valve lasted for a mere three years. This shouldn’t come as a surprise though, since the macOS ecosystem simply isn’t geared towards gaming and VR in any way, shape, or form. Most Mac users have to settle for Intel integrated graphics, and even the Mac users with a dedicated video card have to settle for subpar and overpriced AMD cards, since Apple refuses to support NVIDIA. On top of that, Apple has deprecated OpenGL and wants developers to use their proprietary Metal API instead. In a world where most game developers use DirectX or OpenGL/Vulkan, that just doesn’t make a lot of sense. And let’s not forget that the writing is on the wall for macOS as a general purpose operating system anyway, since Apple will most likely use the move to ARM processors in Macs to further lock down macOS, making it more like iOS. While macOS might be more popular than Linux in absolute numbers, the cold and harsh truth is that the Linux userbase simply has a far larger group of skilled developers, programmers, and tinkerers willing to put the effort into making non-native games work on Linux and to improve support for things like VR devices. These are exactly the kind of people Apple seems to have a deep-rooted disdain for. Expect more of these kinds of announcements over the coming years, as game companies (and other developers) have to decide whether or not to support an isolated and locked down platform like macOS on ARM – a platform without first-party OpenGL or Vulkan support, with a steward actively pushing you to use a proprietary API that you can’t use anywhere else.

The big news first: a timeline has been set for Beta 2! If all goes well, it will be released by the end of May. Of course, this means everyone has been scrambling for last minute changes this month instead of stabilizing everything. We are now in “soft freeze”, and the branch will be created on Friday. Yes, an actual almost release date for Haiku’s second beta release.

I am happy to announce the availability of GhostBSD 20.04, but first thanks to all people that gave feedback and reported issues. We fixed a couple of problems that were found in 20.03. This release comes with kernel and OS updates and numerous software applications updates and many improvements like replacing gnome-mount and hald with FreeBSD devd and Vermaden automount which make auto mounting and unmounting of external device way more stable and supports more filesystems. GhostBSD is a desktop-oriented BSD based on FreBSD, running the MATE or Xfce desktop. Linux desktops really take up all the spotlights when it comes to UNIX-like operating systems for average users, and I feel like some honest competition would be a good thing. More focus on desktop-oriented BSD distributions can help.

The Trinity Desktop Environment, a fork of the KDE 3.x series, celebrates its tenth anniversary with a new maintenance release. R14.0.8 is the eighth maintenance release of the R14.0 series, and is built on and improves the previous R14.0.7 version.. Maintenance releases are intended to promptly bring bug fixes to users, while preserving overall stability through the avoidance of both major new features and major codebase re-factoring. Packages are available for Debian and Ubuntu.

Qemu 5.0.0 has been released, with a massive laundry list of changes, fixes, and improvements for a lot of Qemu’s emulated platforms. The new version will make it your operating system’s repositories soon enough if you use Linux, but if you use a platform where you have to muddle along with and juggle your applications and updates manually like a peasant, like Windows or macOS, you’ll have to wait until someone packages it for you so you can update your binary manually. Of course, you can always build it yourself, too.

There are a lot of things that are not visible for a casual Sailfish OS user. This 3.3.0 release contains a vast number of updates for the lower level of the stack. We’ve included for example the updated toolchain, a new version of Python and many updates to core libraries such as glib2. In this blog I will go through a few of the changes and what they mean in practice for users, developers and Sailfish OS in general. You can also read the more detailed release notes. It’s nice to see my original Jolla Phone – released in late 2013 – is still supported, as is the ill-fated Jolla Tablet from late 2015. I’m probably one of the few people in the world who actually got a Jolla Tablet, delivered straight from Hong Kong in a non-descript brown packaging, but I never seriously used it.

An effort to port RPM to SGI IRIX has released beta 0.0.5: While RPM has been tested as working on IRIX (irix 32 bit – INDY, I2, O2) – there are possibly still gremlins in other packages with mis-identification due to these differences. Now that RPM itself is working, we can “hot upgrade” and fix those as we see them.

When the parts were almost in, I had decided to really start digging into NixOS. Friends on IRC and Discord had been trying to get me to use it for years, and I was really impressed with a simple setup that I had in a virtual machine. So I decided to jump head-first down that rabbit hole, and I’m honestly really glad I did. NixOS is built on a more functional approach to package management called Nix. Parts of the configuration can be easily broken off into modules that can be reused across machines in a deployment. If Ansible or other tools like it let you customize an existing Linux distribution to meet your needs, NixOS allows you to craft your own Linux distribution around your needs. Unfortunately, the Nix and NixOS documentation is a bit more dense than most other Linux programs/distributions are, and it’s a bit easy to get lost in it. I’m going to attempt to explain a lot of the guiding principles behind Nix and NixOS and how they fit into how I use NixOS on my desktop. I’m hearing more and more people talk about NixOS lately, and I’ve been wondering why. This article is an excellent overview into this unusual Linux distribution.

Friday marked the release of LXQt 0.15, the first big update to this lightweight Qt5-based desktop environment since January 2019. There comes a fair number of improvements with this desktop that was born out of the LXDE and Razor-qt initiatives. I feel like LXQt is to KDE as MATE/Cinnamon/XFCE are to GNOME 3. It’s good to have options.

Microsoft has settled the great space debate, and sided with everyone who believes one space after a period is correct, not two. The software giant has started to update Microsoft Word to highlight two spaces after a period (a full stop for you Brits) as an error, and to offer a correction to one space. Microsoft recently started testing this change with the desktop version of Word, offering suggestions through the Editor capabilities of the app. There’s normal spacing, and everything else. I’m glad Microsoft is normal.

By default, Ubuntu ships with a bunch of snap packages. If, like me, you don’t like snap and Flatpak infecting your clean deb/apt-based system, here’s how to remove them. Now this all sounds great, and it is in some ways (especially for app developers), but it comes at a cost: and that is generally performance and annoyances with application theming, access to user folders, and the like. I personally find that if I want to run a sandboxed application I lean more toward Flatpak as it is more performant and seems a bit more mature than Canonical’s snap system. In any event, I usually disable snaps entirely on a fresh install of Ubuntu, and I’ll show you how to do that in the new Ubuntu 20.04 release.

Ubuntu 20.04 LTS on the desktop is shipping with GNOME 3.36 and its plethora of improvements, improved OpenZFS support as an experimental option, the Linux 5.4 LTS kernel and the many improvements the new kernel brings, WireGuard VPN support, and a wealth of other package updates. I’ve been running it on my laptop since the beta, upgraded from 19.10, and it’s been smooth sailing.

The Cupertino, California-based technology giant is working on three of its own Mac processors, known as systems-on-a-chip, based on the A14 processor in the next iPhone. The first of these will be much faster than the processors in the iPhone and iPad, the people said. Apple is preparing to release at least one Mac with its own chip next year, according to the people. But the initiative to develop multiple chips, codenamed Kalamata, suggests the company will transition more of its Mac lineup away from current supplier Intel Corp. I wonder just how locked-down these ARM Macs will be. Will it be App Store-only? Can you change default applications on ARM macOS? Can you install a browser engine other than WebKit? Do you have access to the file system? Will it ship with a terminal? I’m not so sure macOS users should be excited about ARM Macs.

One of the key elements I’ve always found frustrating with basic software development is that it can often be quite difficult to actually get the hardware in hand you want to optimize for, and get a physical interaction that isn’t delayed by networking or logging in or anything else. Having a development platform on the desk guarantees that direct access, and for the non-x86 vendors, I’ve been asking for these for some time. Thankfully we’re now starting to see some appear, and Avantek, one of the Arm server retailers, have built an Ampere eMag workstation out of a server board, with some interesting trickery to get it to fit. They sent us one to have a look at. This is only the unboxing and short first impressions, but I am unreasonably excited about what are effectively bog-standard PCs, but with an ARM processor. I can’t wait for these machines to come down in price, because this is the first time in a long, long time that we’ve seen what could become a serious challenge to x86 in its traditional space: desktops and laptops. Once AnandTech publishes its actual review, I’ll be on top of that, too.

But in recent months, MIPS related news has not been so good. First, Wave Computing decided to end MIPS Open Initiative in November 2019, then Paul Burton and Ralf Baechle removed themselves from the Linux kernel MIPS maintainer list in February 2020, as their work with MIPS ended leaving Thomas Bogendoerfer as the only maintainer. But this month, things turned for the worse, with CIP United filing a lawsuit against MIPS LLC on April 6, before announcing the company had obtained exclusive MIPS license rights for mainland China, Hong Kong, and Macau on April 11, 2019 (Click on News in top menu of this link). In my mind, I had written off MIPS as a thing of the past anyway – but it’s still sad to see if tangled up in legal disputes and lack of attention.

We’re all aware of Haiku, the open source re-implementation of BeOS. This week, I found out a similar effort is underway to recreate OS/2 Warp 4 as an open source operating system. osFree is a Free Open Source software operating system development project, aiming to replace eventually all OS/2 subsystems with Open source analogues. It aims for OS/2 Warp 4 (Merlin) as a base compatibility system, which does not mean that we will not support features of newer (OS/2 Warp Server for e-business, eComStation and ArcaOS) OS/2 versions. This includes rewriting not only user-level code but the OS/2 kernel too. The project is very much in its early alpha stages, so don’t expect to boot into osFree any time soon. That being said, they have made progress over the years, and their current status explains how far along they are. osFree project is deep in the alpha stage. At the present time the osFree project work with low-level parts of operating system like loader and related tools. We also try to develop an experimental prototype of OS/2 personality for L4 microkernel. Also we have set of command line tools like CMD.EXE and file/disk maintenance utilities. I absolutely adore OS/2, and while I understand all too well a project like this won’t be finished overnight – look at Haiku – I do love that it’s being worked on.

The Linux kernel lockdown patches were merged into the 5.4 kernel last year, which means they’re now part of multiple distributions. For me this was a 7-year journey, which means it’s easy to forget that others aren’t as invested in the code as I am. Here’s what these patches are intended to achieve, why they’re implemented in the current form and what people should take into account when deploying the feature. Root is a user – a privileged user, but nevertheless a user. Root is not identical to the kernel. Processes running as root still can’t dereference addresses that belong to the kernel, are still subject to the whims of the scheduler and so on. But historically that boundary has been very porous. Various interfaces make it straightforward for root to modify kernel code (such as loading modules or using /dev/mem), while others make it less straightforward (being able to load new ACPI tables that can cause the ACPI interpreter to overwrite the kernel, for instance). In the past that wasn’t seen as a significant issue, since there were no widely deployed mechanisms for verifying the integrity of the kernel in the first place. But once UEFI secure boot became widely deployed, this was a problem. If you verify your boot chain but allow root to modify that kernel, the benefits of the verified boot chain are significantly reduced. Even if root can’t modify the on-disk kernel, root can just hot-patch the kernel and then make this persistent by dropping a binary that repeats the process on system boot. These patches are intended to prevent that, and this blog post goes into detail about how it all works.

You’re probably familiar with modern processors made by Advanced Micro Devices. But AMD’s processors go back to 1975, when AMD introduced the Am2901. This chip was a type of processor called a bit-slice processor: each chip processed just 4 bits, but multiple chips were combined to produce a larger word size. This approach was used in the 1970s and 1980s to create a 16-bit, 36-bit, or 64-bit processor (for example), when the whole processor couldn’t fit on a single fast chip. The Am2901 chip became very popular, used in diverse systems ranging from the Battlezone video game to the VAX-11/730 minicomputer, from the Xerox Star workstation to the F-16 fighter’s Magic 372 computer. The fastest version of this processor, the Am2901C, used a logic family called emitter-coupled logic (ECL) for high performance. In this blog post, I open up an Am2901C chip, examine its die under a microscope, and explain the ECL circuits that made its arithmetic-logic unit work. A very detailed, technical look at this processor.

Proton has done far more for Linux gaming than any porting company out there, by bringing about 6000 games to us in less than 2 years. There’s about 100 games every month that get a Platinum rating according to ProtonDB. (because of the recent changes on ProtonDB rating, this is now more accurate than it was before). Proton has become better over time: the percentage of games getting a Platinum rating is steadily increasing over time as well – it used to be about 40% of all unique games reported, and now we are closer to 50%. This is cumulative, so the range will vary month by month but the trend is very clear. Proton is one of the biggest contributions to desktop Linux in at least the past ten years. Thanks to Proton, I now play all my games on Linux, and could finally just remove Windows from my desktop altogether. All I do when I want to buy a game that doesn’t support Linux natively is check ProtonDB, and if the rating is platinum (works out of the box) or gold (might need to run a command, move a file around, or select a specific Proton version in Steam), I just buy it without further issues. If it’s rated silver, I’ll take a more detailed look and weigh the work vs. the benefit. It’s been amazing, and I pretty much forget which games in my Steam library use Proton, and which don’t. It’s so seamless and effortless that I don’t have to know – from big, triple-A titles, all the way down to small indie games.

Visopsys is a hobby OS for x86-compatible PCs, started in 1997. Version 0.9 was released this morning, and there’s a change log. The summary: This major release offers a subtly updated look, enhanced networking capabilities and associated programs, Unicode support, a software packaging/download/install/uninstall infrastructure with an online ‘store’, a user space window shell, VMware mouse integration, HTTP, XML, and HTML libraries, some C++ and POSIX threads (pthreads) support, ‘pipes’ for interprocess communication, and additional hashing algorithms. Visopsys has a long history on OSNews – the oldest mention being from 2005. It’s been in relatively steady development ever since.

Bill Gates is now the favorite target for coronavirus misinformation according to data compiled by the New York Times and Zignal Labs, a company that analyzes media sources. Conspiracy theories conflating Gates with the virus were mentioned 1.2 million times on TV and social media from February to April, 33 percent more often than the 2nd most popular conspiracy theory linking 5G with COVID-19, according to Zignal Labs, peaking at 18,000 mentions a day in April. It’s cheaper to be an idiot than to be responsible.

Today, it seems we’re on another track completely. Despite being endlessly fawned over by an army of professionals, Usability, or as it used to be called, “User Friendliness”, is steadily declining. During the last ten years or so, adhering to basic standard concepts seems to have fallen out of fashion. On comparatively new platforms, I.E. smartphones, it’s inevitable: the input mechanisms and interactions with the display are so different from desktop computers that new paradigms are warranted. Worryingly, these paradigms have begun spreading to the desktop, where keyboards for fast typing and pixel-precision mice effectively render them pointless. Coupled with the flat design trend, UI elements are increasingly growing both bigger and yet somehow harder to locate and tell apart from non-interactive decorations and content. I doubt anyone here will disagree with the premise of this article, even if you might disagree with some of the examples. These past few weeks I’ve set up virtual machines of all the old Windows releases just to remind myself of just how good the graphical user interface introduced in Windows 95 was perfected over the years, culminating in the near-perfect Classic theme in Windows XP and Server 2003. Later iterations of the Classic theme, in Vista and onward, would sadly retain some of the Aero UI elements even when setting the Classic theme, ruining the aesthetic, and of course, the Classic theme is gone altogether now – you can’t set it in Windows 10. Similarly, Platinum in Mac OS 9 is still more coherent, more usable, and more intentful than whatever macOS brought to the table over the years. We can find solace in the fact that trends tend to be cyclical, so there’s a real chance the pendulum will eventually wing back.

With the release of Sculpt version 20.02, we follow our roadmap’s mission to make Sculpt OS easier to approach. In particular, we identified the reliance on a command-line interface as a potential barrier of entry. As Sculpt OS is not a Unix-like system, it should not require any Unix know-how from the user. To relieve users from this burden, Sculpt 20.02 introduces a custom graphical file browser and editor that can be used for interactively inspecting and tweaking the state of the system. The traditional command-line interface is still present as a fallback for advanced tasks though. The updated manual goes into detail about the use of the new system. Sculpt OS is related to the Genode project – a popular mainstay at OSNews – and basically ties a number of their technologies together into a general purpose desktop operating sytsem. Sculpt is an open-source general-purpose OS. It combines Genode’s microkernel architecture, capability-based security, sandboxed device drivers, and virtual machines in a novel operating system for commodity PC hardware. Sculpt is used as day-to-day OS by the Genode developers. The download page provides a ready-to-go VirtualBox image, so if you want to play with Sculpt OS – they couldn’t have made it any easier.

Microsoft is working on a tool that will let you replace the Windows Run feature on Windows 10. The Spotlight-like launcher for Windows 10 will be released later this year, as part of the company’s effort to customize Win+R and give users numerous features but keep the handling as easy as possible at the same time. Microsoft’s Spotlight-like launcher for Windows 10 is said to be part of PowerToys upcoming update. According to Microsoft, PowerToys Run is designed to replace Win + R shortcut. I use Ulauncher on my computers, and I can’t imagine using them without it. It’s about time a similar feature came from Microsoft, but the fact it’s a separate PowerToy thing and not a default on Windows means it’ll remain a niche thing. This should be standard out of the box.

The lock screen work that we landed in 3.36 was the outcome of a long-running programme of UX work, which we first put together at the GNOME UX hackfest in London, back in 2017. There are still some outstanding pieces of the login/unlock experience that need to be filled in, and this is something that we hope to work on over the coming development cycle. However, we are also turning our attention to other aspects of the shell, which we have wanted to update for some time. In the rest of this post, I’ll describe some of the areas that we’re hoping to improve, before going on to talk about how we’re going to do it. An overview of what to expect from upcoming GNOME releases.

I am pleased to announce the KWinFT project and with it the first public release of its major open source offerings KWinFT and Wrapland, drop-in replacements for KDE’s window manager KWin and its accompanying KWayland library. The KWinFT project was founded by me at the beginning of this year with the goal to accelerate the development significantly in comparison to KWin. Classic KWin can only be moved with caution, since many people rely on it in their daily computing and there are just as many other stakeholders. In this respect, at least for some time, I anticipated to be able to push KWinFT forward in a much more dynamic way. This is a great concept, and will allow more experimentation and exciting new features in a place where this normally simply doesn’t make much sense.

We’ve just released SRU 20 for Oracle Solaris 11.4, the April 2020 CPU. It is available via ‘pkg update’ from the support repository or by downloading the SRU from My Oracle Support Doc ID 2433412.1. The administrator of my organisation needs to supply me with a Support Identifier before I can do something as simple as read the documentation about this new version, so I have no idea what to tell you. I guess Solaris technically isn’t dead yet?

Hercules is an open source software implementation of the mainframe System/370 and ESA/390 architectures, in addition to the new 64-bit z/Architecture. Hercules runs under Linux, Windows (98, NT, 2000, and XP), Solaris, FreeBSD, and Mac OS X (10.3 and later). The installation instructions will aid you in setting Hercules up.

If an application from a Chinese company installed a kernel driver onto your system with complete access to your computer, but they pinky-promised not to abuse this access and power, would you install the application? Well, if you’re interested in Riot Games’ new hit game Valorant, that’s exactly the question you’re going to have to answer. Riot Games, the company behind one of the most popular games in the world, League of Legends, recently starting publicly beta testing their new game, Valorant. Two months ago, the company penned a rather condescending blog post detailing their future anti-cheat technology, which would include a Windows kernel driver (running in ring 0, in x86 parlance). Valorant is their first game using this kernel driver, and as it turns out, this kernel driver starts at boot, and due to its very nature has full system access, even when you’re not running Valorant. According to Riot Games, we just have to trust them on their blue eyes that their kernel driver is fully secure and won’t be exploited by malicious third parties, and that the company won’t use it to spy on people or otherwise violate their privacy. Riot states on Reddit that “multiple external security research teams” have reviewed the driver, but as far as I can tell, these reviews have not been published for public vetting. What we’re dealing with here is a rootkit, a method more and more anti-cheat systems are employing in the fight against cheating. The argument is that game developers need full, complete, and total access to your system in order to prevent you from cheating, and a kernel driver is how they do it. There’s a long history of these sorts of things going horribly, horribly wrong. We all still remember the Sony rootkit debacle, where Sony CDs installed rootkits on users’ computers that ended up being exploited left, right, and centre by malicious parties. In 2016, Capcom installed a similar rootkit meant for anti-cheat with Street Fight V, which was an absolute security train wreck. And closer to home for Riot, the game client for their very own League of Legends installed crypto miners on users’ computers in the Philippines. Despite the inherent dangers in installing closed-source security-by-obscurity rootkits, Riot is dead-set on continuing to use them, and it’s only a matter of time before their rootkit will be forced upon League of Legends players as well – which in my case means I won’t be able to play League of Legends anymore even if I wanted their rootkit on my computer, since I play on Linux through Wine/Lutris, which doesn’t support kernel drivers at all. Players of Riot’s games will have to ask themselves if they trust Riot to install a rootkit with complete and full access to their system – browsing history, chat logs, email, everything. You have to trust Riot when they say the rootkit is “secure” and won’t be exploited by malicious third parties, and that the company itself won’t use it to invade your privacy. Interesting sidenote: Riot Games is owned by the Chinese company Tencent, the company behind WeChat. Tencent is, for all intents and purposes, an arm of the Chinese government, so not only do you have to trust Riot Games, you also have to trust their owner, Tencent, as well as who Tencent literally answers to – the Chinese government. I’m not going to tell anyone what they should or should not do with their computers, and if you trust Riot, Tencent, and the Chinese government enough to let them install a rootkit on your computer, then that’s your right to do so. However, I do feel users need to be at least aware of the choice they’re making.

Colorado — like most states and territories across the country — is experiencing record unemployment numbers. But the state’s unemployment system is built on aging software running on a decades-old coding language known as COBOL. Over the years, COBOL programmers have aged out of the workforce, forcing states to scramble for fluent coders in times of national crisis. A survey by The Verge found that at least 12 states still use COBOL in some capacity in their unemployment systems. Alaska, Connecticut, California, Iowa, Kansas, and Rhode Island all run on the aging language. According to a spokesperson from the Colorado Department of Labor and Employment, the state was actually only a month or two away from “migrating into a new environment and away from COBOL,” before the COVID-19 pandemic hit. Are you one of the already 17 million people laid off in the US, losing what little health insurance you had in the process, and now you can’t even apply for unemployment assistance because some baby boomer coded the damn system in COBOL? Time to lift yourself up by the bootstraps and learn the wonders of COBOL!

Google has made significant progress toward developing its own processor to power future versions of its Pixel smartphone as soon as next year — and eventually Chromebooks as well, Axios has learned. The chip, code-named Whitechapel, was designed in cooperation with Samsung, whose state-of-the-art 5-nanometer technology would be used to manufacture the chips, according to a source familiar with Google’s effort. Samsung has also manufactured Apple’s iPhone chips, as well as its own Exynos processors. Apparently, Google has received the first batch in recent weeks. This development process has been one of the worst-kept secrets in the industry, since Google pretty much admitted it was developing its own mobile SoC years ago.

Google is replacing some Android apps for Chromebooks with Progressive Web Apps (PWAs). A PWA is essentially a webpage that looks and feels like a traditional app. This will certainly be good news for many Chromebook owners. In some cases, PWAs are faster and more functional than their Android counterparts. PWAs also take up less storage and require less juice to run. When PWAs are a better option than Android applications, you know you’re scraping the bottom of the barrel. I really don’t understand why Google doesn’t just turn Chrome OS into a more traditional desktop Linux distribution – they’ll get better applications, better tooling, and better performance than shoehorning Android applications into Chrome or pretending a website is an application.

Intel’s Dynamic Platform and Thermal Framework (DPTF) is a feature that’s becoming increasingly common on highly portable Intel-based devices. The adaptive policy it implements is based around the idea that thermal management of a system is becoming increasingly complicated – the appropriate set of cooling constraints to place on a system may differ based on a whole bunch of criteria (eg, if a tablet is being held vertically rather than lying on a table, it’s probably going to be able to dissipate heat more effectively, so you should impose different constraints). One way of providing these criteria to the OS is to embed them in the system firmware, allowing an OS-level agent to read that and then incorporate OS-level knowledge into a final policy decision. Unfortunately, while Intel have released some amount of support for DPTF on Linux, they haven’t included support for the adaptive policy. And even more annoyingly, many modern laptops run in a heavily conservative thermal state if the OS doesn’t support the adaptive policy, meaning that the CPU throttles down extremely quickly and the laptop runs excessively slowly. It’s been a while since I really got stuck into a laptop reverse engineering project, and I don’t have much else to do right now, so I’ve been working on this. It’s been a combination of examining what source Intel have released, reverse engineering the Windows code and staring hard at hex dumps until they made some sort of sense. Here’s where I am. Someone has to do the dirty work.

The ReactOS Team is pleased to announce the release of version 0.4.13. As with prior releases, keywords are noted representing the release itself and highlighting key improvements. In this particular case, the 0.4.13 version shows the results of significant hard work to bring improvements to the USB stack, further development on the Xbox port boot process, an Explorer File Search for the Shell module, as well as many other changes. There’s also new work on accessibility features, and the 64 bit version has seen considerable improvements, too.

The Verge reports: Apple and Google announced a system for tracking the spread of the new coronavirus, allowing users to share data through Bluetooth Low Energy (BLE) transmissions and approved apps from health organizations. The new system, which is laid out in a series of documents and white papers, would use short-range Bluetooth communications to establish a voluntary contact-tracing network, keeping extensive data on phones that have been in close proximity with each other. Official apps from public health authorities will get access to this data, and users who download them can report if they’ve been diagnosed with COVID-19. The system will also alert people who download them to whether they were in close contact with an infected person. This is a clever use of technology, but as always, what can be used for good, can also be used for evil. A technology like this certainly seems useful in our current worldwide predicament, but it’s not hard to imagine what can be done with it that might be more nefarious. That being said, it’s refreshing to see these companies working together for the good of their users for once, instead of the constant hostility towards users to create platform lock-in and shareholder value. In any event, the APIs for this new system will arrive in iOS and Android over the coming months – through a regular OS update on iOS, and through Google Play on Android.

With Android 7.0 Nougat, Google introduced a partition scheme designed to speed up software updates. In Nougat, Google added support for duplicating certain partitions so that inactive partitions can get updated in the background and then swapped to active with a quick reboot. This “A/B partition” setup allows for “seamless updates” to take place on supported Android devices, much like Google’s Chrome OS. However, Google has never mandated the use of A/B partitions, so many devices out there that don’t support seamless updates. That could change with Android 11, however, as Google is making it mandatory for newly launched devices to support virtual A/B partitions. Anything to make the update situation on Android smoother is welcome.

There’s a storm brewing in the world of Qt and KDE, as the parent company of Qt, The Qt Company, is contemplating restricting new Qt releases to paying customers (i.e., not releasing them as open source) for twelve months. This obviously affects the KDE project considerably, who have been negotiating with The Qt Company for years now. An announcement made by The Qt Company in January derailed said negotiations, however. As KDE’s Olaf Schmidt-Wischhöfer explains: They announced that LTS releases of Qt will only be available for paid license holders. It is still unclear what this implies for contributions to Qt and for the sharing of security fixes between the various parties (including The Qt Company, the many Qt experts contributing, the KDE community, and Linux distributions). It seemed the two parties were working on a path forward acceptable to all parties involved, but then came the announcement earlier today that The Qt Company was contemplating restricting all releases to paid customers for twelve months. It seems bad blood has been brewing for a while, as Schmidt-Wischhöfer states: The Qt Company says that they are willing to reconsider the approach only if we offer them concessions in other areas. I am reminded, however, of the situation half a year ago. We had discussed an approach for contract updates, which they suddenly threw away by restricting LTS releases of Qt instead. All software changes in Qt will still be available at as Open Source as required by our contract – maybe with a delay of 12 months if the company decides to part ways with the communities. We will continue to work on a contract update that helps all sides. But even if these negotiations were to be unilaterally stopped by The Qt Company, Qt will stay Open Source, and KDE will be able to use it. I am also absolutely sure that the Qt + KDE communities will continue cooperation on new features, bug fixes, and security fixes, even should The Qt Company decide to forgo the benefits of cooperation. Luckily for the future of KDE and Qt, there is an agreement in place between KDE and The Qt Company that states that “ should The Qt Company discontinue the development of the Qt Free Edition under the required licenses, then the Foundation has the right to release Qt under a BSD-style license or under other open source licenses.” This is a serious issue that I hope can be resolved, as nobody will benefit from a serious rift between The Qt Company and the KDE project.

Windows is getting support for browsing Linux file systems! Except, not really, since it only applies to WSL. We’ve had the ability to access your Linux files since Windows 1903, but now you can easily get to them from your left-hand navigation pane in File Explorer. Selecting the Linux icon will show you a view of all your distros, and selecting those will place you in the Linux root file system for that distro. As far as I can tell, this only applies to distributions installed through Windows Subsystems for Linux, not to actual distributions installed elsewhere on your computer (on other hard drives or partitions). Cool new feature, I guess, but properly sanctioned Windows support for Ext4 and other Linux-focused file systems would be so much more helpful.

Some very nice performance fixes landed this week, which should substantially boost move and copy speeds for local transfers and transfers to and from Samba shares in particular. But that’s not all, and there’s more on the menu… Every week, there’s a blog post highlighting the various changes, bugfixes, small new features, fixed paper cuts, and other small changes within KDE and its associated projects and programs. They’re a joy to read, and I would love it if more major software projects did this.

Hobbyist licenses for OpenVMS have been a notable option for users of the VAX, Alpha, and Integrity business servers. HP 3000 users tried for a similar license for MPE/iX, especially in the months following HP’s news it wouldn’t continue its 3000 business. HP declined to create the kind of license the users wanted to power the basement and in-garage 3000 servers they’d brought home. With the change in ownership of OpenVMS — HP Enterprise turned over the business to VMS Software Inc. — the hobbyist program is ending at HPE. VSI is considering one option to continue hobbyist-class licenses. That’s one hell of a bummer. I hope they can come to sort of solution or agreement.

One of my goals with GBE+ is to program an emulator that is as complete as I can possibly make it. That means emulating devices like the GB Printer. To tell the truth, I had my eye on GB Printer support for some time, but only recently have I done enough work on the DMG/GBC core to make that possible. A long time ago, I tried getting the GB Printer to work in VBA-M (1.8.0) but the Linux version didn’t seem to do anything. That is to say, VBA-M did emulate the printer as if it were connected, but it didn’t save the image anywhere I could find. The Windows version worked flawlessly and showed me the final print as I expected. Maybe that was just user-error on my part, but it inspired me to one day make an emulator that would properly emulate the GB Printer on Linux, my OS of choice. Digressing, let’s take a look at what the GB Printer is doing and how it interacts with a Game Boy system. The Game Boy Camera and Game Boy Printer were these almost mythical items I’d talk about with my friends and my brothers, and the idea of taking photos with a Game Boy was so wild and out there it sparked our imaginations. To this day, I’ve never seen or used one in real life, and that bums me out.

In February, KrebsOnSecurity told the story of a private citizen auctioning off the dangerous domain corp.com for the starting price of $1.7 million. Domain experts called corp.com dangerous because years of testing showed whoever wields it would have access to an unending stream of passwords, email and other sensitive data from hundreds of thousands of Microsoft Windows PCs at major companies around the globe. This week, Microsoft Corp. agreed to buy the domain in a bid to keep it out of the hands of those who might abuse its awesome power. I had no idea that a seemingly innocuous default chosen decades ago had this much of an impact.

Google has been ramping up the Linux environment on Chrome OS lately, with features like microphone support and USB connections. For those of you who spend a lot of time in the command-line Terminal, Chrome OS 83 (currently in the Dev channel) has updated the app with new themes and customization options. The Terminal app on Chrome OS has changed very little since the Linux container was originally released — it’s a single window with text. However, the new version shipping in Chrome OS 83 offers tabs, pre-made themes, customizable colors and fonts for text, and even cursor options. To be honest, I’d rather have a proper, traditional Linux distribution than Chrome OS, but I guess these are welcome additions for those among us using the terminal on Chrome OS.

I guess current world events are starting to affect the flow of news in our sector, too, since there’s a decided lack of interesting stuff to talk about. So, let’s talk about this: One of the immediate differences Ubuntu 20.04 desktop/laptop users will notice when booting in UEFI mode is the boot splash screen improvements thanks to leveraging Red Hat’s work on providing a flicker-free boot experience and pulling in the UEFI BGRT system/motherboard logo during the boot process to provide a more transitive experience. Canonical in turn is working on pushing some of their improvements back into upstream Plymouth. The Ubuntu 20.04 LTS boot experience is on-par to what has been found in Fedora and other Linux distributions like Arch Linux for over one year. I love it when different distributions and other projects work together to improve something that isn’t particularly sexy or high on anybody’s agenda, yet still is a welcome improvement. This is a great example of that.

The Cidco MailStation is a series of dedicated e-mail terminals sold in the 2000s as simple, standalone devices for people to use to send and receive e-mail over dialup modem. While their POP3 e-mail functionality is of little use today, the hardware is a neat Z80 development platform that integrates a 320×128 LCD, full QWERTY keyboard, and an internal modem. After purchasing one (ok, four) on eBay some months ago, I’ve learned enough about the platform to write my own software that allows it to be a terminal for accessing BBSes via its modem or as a terminal for a Unix machine connected over parallel cable. A year old story, but come on, this is timelessly cool.

In Windows 10 version 2004, we are introducing the concept of Hosted Apps to the Windows App Model. Hosted apps are registered as independent apps on Windows, but require a host process in order to run. An example would be a script file which requires its host (eg: Powershell or Python) to be installed. By itself, it is just a file and does not have any way to appear as an app to Windows. With the Hosted App Model, an app can declare itself as a host, and then packages can declare a dependency upon that host and are known as hosted apps. When the hosted app is launched, the host executable is then launched with the identity of the hosted app package instead of its own identity. This allows the host to be able to access the contents of the hosted app package and when calling APIs it does so with the hosted app identity. This seems like something that could be useful for progressive web apps, and maybe even Electron apps by making them use Edge Chromium’s rendering engine instead of having every Electron application use its own copy of Chromium, which could benefit performance and battery life.