China’s Xiaomi, Huawei Technologies, Oppo and Vivo are joining forces to create a platform for developers outside China to upload apps onto all of their app stores simultaneously, in a move analysts say is meant to challenge the dominance of Google’s Play store. I’m glad Android is open enough to allow alternative application stores to exist, but whether or not non-Chinese application makers would want to partake in a Chinese state-run application store effort is another issue altogether.

Just another heads up that kernel extensions on macOS will soon stop working. This has been known for a while, but you might not even know you’re using kernel extensions in the first place. System extensions on macOS Catalina (10.15) allow software like network extensions and endpoint security solutions to extend the functionality of macOS without requiring kernel-level access. At WWDC19, we announced the deprecation of kernel extensions as part of our ongoing effort to modernize the platform, improve security and reliability, and enable more user-friendly distribution methods. Kernel programming interfaces (KPIs) will be deprecated as alternatives become available, and future OS releases will no longer load kernel extensions that use deprecated KPIs by default. If you use macOS, run kextstat | grep -v com.apple to see how many third party kernel extensions you have running. Things like VirtualBox, controller support for Steam, DropBox, Little Snitch, and more all come with kernel extensions, so there’s definitely chances you might be running some without even realising it.

So the Democratic party of Iowa tried to use an untested app to report caucus results during the Iowa primary caucus, and… It went as well as you’d expect. Digging deeper into the app, it should’ve been obvious this was never going to work. In this case, however, it looks like Shadow used a test platform for the app’s public distribution. Installing software through a test platform or sideloading onto your device manually both come with security risks, as app store review processes are designed to discover whether a piece of software is hiding malware or does something behind the scenes it’s not supposed to. In the event you do sideload an app or try installing an unofficial version, your smartphone typically warns you of the risks and asks if you want to proceed. It’s also a less stable model for deploying software at scale, which might explain the difficulty precinct chiefs had in downloading the program. The screenshot from Motherboard also shows that the app was distributed using the platform’s free tier and not its enterprise one. That means Shadow didn’t even pony up for the TestFairy plan that comes with single sign-on authentication, unlimited data retention, and end-to-end encryption. Instead, it looks like the company used the version of TestFairy anyone can try for free, which deletes any app data after 30 days and limits the number of test users that can access the app to 200. What an unmitigated disaster. We’re in 2020 right? Not in 1783?

With Google Takeout, you can download your data from Google apps as a backup or for use with another service. Unfortunately, a brief issue with the tool last November saw your videos in Google Photos possibly get exported to strangers’ archives. How does this even happen? Too bad companies like this have armies of lawyers and obtuse terms of service to hide behind – since software is a special little butterfly that isn’t held to the same standards as any other product we use – so nobody will ever be held accountable for this.

The real reason for Britain’s nonexclusion of Huawei was kept under wraps by its government: fear of retaliation. After Brexit, London sees itself as dependent on Beijing’s goodwill. In an interview with the Global Times on Jan. 20, the Chinese ambassador to Britain made it clear that an exclusion of Huawei would severely damage economic and political relations. And for Johnson, the threats from Beijing—a government with expansive control over its national economy—were more credible than those of U.S. President Donald Trump’s administration. Of course, fear isn’t much of an appealing public justification, especially for someone such as Johnson, who wants to project the image of a fearless leader. That’s why the government has come up with an extensive technical justification for the decision—an explanation that’s full of contradictions. Wait, you mean to tell me that going alone instead of being part of the biggest trade and power block after the US opens you up to manipulation and spying by and subservience to the likes of China and Russia? This should make it clear to the US and the EU that the UK should not be trusted with intelligence data.

We’re very grateful to this week’s sponsor: UnitySync®. For a unified GAL and more, UnitySync helps sync objects between LDAP and cloud directories with this highly scalable and customizable tool. Directory Wizards offers responsive technical support before and after your purchase, as well as other directory tools to simplify directory maintenance. A free evaluation available to test drive your solution. Please visit their website to learn more: https://www.dirwiz.com/unitysync .

System calls are a way for unprivileged, user applications to request services from the kernel. In the RISC-V architecture, we invoke the call using the ecall instruction. This will cause the CPU to halt what it’s doing, elevate privilege modes, and then jump to whatever function handler is stored in the mtvec (machine trap vector) register. Remember, this is the “funnel” where all traps are handled, including our system calls. We have to set up our convention for handling system calls. We can use a convention that already exists, so we can interface with a library, such as newlib. But, let’s make this ours! We get to say what the system call numbers are, and where they will be when we execute a system call. This is part 7 in a long series about writing a RISC-V operating system in Rust.

EU lawmakers overwhelmingly called on Thursday for rules to establish a common charger for all mobile device makers across Europe, a drive that iPhone maker Apple has criticised. Members of the European Parliament voted by 582-40 for a resolution urging the European Commission, which drafts EU laws, to ensure that EU consumers are no longer obliged to buy new chargers with each new device. This story is a case of government regulation done extremely well. This whole process started with a voluntary agreement in the industry to standardise on one charger and port, and if they failed, the EU would step in and enforce it by law. This agreement has worked out quite well – first micro USB, now USB-C. However, one popular phone maker decided to not adhere to the agreement, and so, more than ten years after the agreement, and thus ample time for this phone maker to follow suit, the EU will now have to step in. Apple has already moved all of its devices to USB-C, save for one – the iPhone. Now they won’t have much of a choice but to follow along. Much like with RoHS, the rest of the world has only benefited from this push for a charging standard, as anyone who remembers the feature phone and PDA days can only attest to (you should see my mutually incompatible collection of just PDA chargers – I must have dozens of them!). And no, this won’t stifle innovation. This whole process is done in collaboration with the industry and standards bodies, so if newer options come along that the sector wants to standardise on, they can – just as they did with the move from micro USB to USB-C. Apple will just have to suck it up – maybe while they’re at it, they can finally make a charging cable that doesn’t suck?

Under hard time pressure, the ground had to quickly figure out what was wrong and devise a workaround. What they came up with was the most brilliant computer hack of the entire Apollo program, and possibly in the entire history of electronic computing. To explain exactly what the hack was, how it functioned, and the issues facing the developers during its creation, we need to dig deep into how the Apollo Guidance Computer worked. Hold onto your hats, Ars readers—we’re going in. Amazing story.

IBM named Arvind Krishna as chief executive officer, replacing longtime CEO Virginia Rometty. Krishna is currently the head of IBM’s cloud and cognitive software unit and was a principal architect of the company’s purchase of Red Hat, which was completed last year. Rometty, 62, will continue as executive chairman and serve through the end of the year, when she will retire after almost 40 years with the company, IBM said in a statement Thursday. Good luck to the man, I guess. IBM isn’t exactly the most exciting company in the world.

The iPad is now ten years old, and people still have to write articles about how, no, really, you can do real work on an iPad! In 1994, ten years after the Mac was originally introduced, I got my first computer, a Performa 450. Nobody wrote any articles about how, actually, real work on a Mac is possible. Everybody who had a Mac used it for real work. There was no need to write articles about how you could use Macs for real work, because for Macs, it was – and still is – actually true. There are countless people who work on iPads, but the central thread in almost all of the articles and stories about these people is that they involve countless, extensive compromises to make it work – whether that’s resorting to a PC for a lot of tasks, or using complex, hacky Shortcuts to accomplish things any other computer can do without you even thinking about it. I see no reason an iPad can’t be a full, proper computer that can replace many a laptop and desktop, but Apple will need to put some serious weight behind iOS as a platform. The hardware is more than capable – it’s the software that holds it back. The fact we’re ten years into this thing and there’s still no Xcode for iPad tells you all you need to know about how Apple sees the iPad.

This Businessweek article isn’t new. It’s from August 2019. But it has some great data visualizations that I thought our readers would be interested in, looking at technology adoption in general and mobile OS market share in particular, starting with this one:

KnightOS is an operating system I started writing about 10 years ago, for Texas Instruments line of z80 calculators — the TI-73, TI-83+, TI-84+, and similar calculators are supported. It still gets the rare improvements, but these days myself and most of the major contributors are just left with starry eyed empty promises to themselves that one day they’ll do one of those big refactorings we’ve been planning… for 4 or 5 years now. Still, it was a really interesting operating system which was working under some challenging constraints, and overcame them to offer a rather nice Unix-like environment, with a filesystem, preemptive multiprocessing and multithreading, assembly and C programming environments, and more. The entire system was written in handwritten z80 assembly, almost 50,000 lines of it, on a compiler toolchain we built from scratch. The things people can squeeze out of these limited devices astounds me every single time.

I’ll be setting my system up on a Windows machine, but you could just as easily set it up on a macOS or Linux machine. When I first attempted this install, I used VMware Workstation 14 Pro for Windows. After going through most of the installation process I couldn’t get OpenStep in to a color screen mode no matter how much I tried. I eventually found out that VMware Workstation doesn’t support the proper VESA display modes, and try as you might you’ll get an error on boot that says “VESA Mode Not Supported.” Fortunately, Virtual Box – which is cross-platform between Windows, macOS, and Linux and completely free – does support the proper VESA mode and works great for the installation of OpenStep. Still, there are some quirks when setting up your VirtualBox VM initially. The VM must have 1 processor with 1 core, 64MB of RAM, and a 2.0GB hard disk on an IDE controller. You will need to configure one IDE CD-ROM drive and one floppy drive. The hard drive must be at IDE 0:0 (Primary Master), and the CD-ROM drive must be at IDE 0:1 (Primary Slave). You will have to edit the properties of the VM upon creation to ensure you adhere to these standards. All other default options of the VM during the creation wizard can be left alone. NextStep is a lot of fun to explore and play around with, since you can clearly see the early days of Mac OS X in there, for obvious reasons. It’s definitely worth it to set an evening apart and follow this tutorial.