Okay so I'm using this perfectly fine article as an excuse to bring something up, so bear with me here.

This is only slightly related, but it's something that has been bugging me for years, and since I was confronted with it again this past weekend, I might as well get it out of my system: why is nobody innovating anymore in the field of building your own computer? So many aspects of building your own computer are completely crazy when you think about it, and it seems like nobody is really doing anything to fix them.

For instance, why haven't we come up with a way to increase the power you can draw from a PCI-E slot, so that graphics cards don't have to be plugged into the PSU directly with unwieldy power cables, with connectors in the most boneheaded location on the graphics card?

Why are we still using those horrible internal 9/10-pin connectors for USB, the front panel, audio, and so on? These are absolutely dreadful connectors, spread out all over the motherboard in illogical places forcing you to route cabling in unnatural ways, and the pins can easily bend. This is terrible 80s technology that we should've fixed by now.

And the most idiotic connector of them all, which is huge, stiff, almost impossible to plug in, remove, or route properly: the ATX power plug from the PSU to the motherboard. This thing is probably one of the worst connectors you can possibly find inside any computer, and the slot on the motherboard is in an incredibly illogical place considering most case layouts. To make matters worse, the CPU power connector sits at the top-left (usually) of the motherboard, so that's another unwieldy connector and cable with an unnatural route that you have to deal with. It's just terrible.

I like the inside of my computer to look as neat and tidy as possible - not only because it looks nice and is easier to clean, but also because it improves airflow, something quite important with today's processors and graphics cards. However, aging standards with terrible designs and horrible usability that wouldn't look out of place in a 1960s mainframe make that quite the challenge.

We've seen some minor improvements already these past ten years or so, with the advent of modular PSUs and the death of the dreadfully terrible IDE cables and Molex connectors, but more work is definitely needed. We need a replacement for the aging ATX standard, which delivers enough power to the motherboard for the board itself, video cards, and the processors and fans, through a single cable with a modern, easy-to-use connector. It'd be great if a replacement for SATA could also carry power, so that we no longer need to route individual power cables to our hard drives. We need to get rid of 9/10-pin connectors for things like USB and the front panel, and replace them with easy-to-use USB-like connectors.

And last but certainly not least: put all of these things in locations that make sense for the vast majority of cases in use today, so we can reduce the length of cables, save money in the process, and end up with cleaner, easier-to-use computers.

Intel, AMD, NVIDIA, case makers, Microsoft, and whomever else is involved here - sit around a damn table for once, and hash this stuff out. ATX is outdated garbage, and needs a modern replacement. ATX was introduced in 1995 - do you still want to use Windows 95? OS/2 Warp? Version 1.2.0 of the Linux kernel? System 7.5.1? Floppies? CRTs? Of course you don't!

Then why the hell are we still using ATX?

In a paper out this week in Science, researchers Yaniv Erlich and Dina Zielinski report successfully using DNA to store and retrieve "a full computer operating system, movie, and other files".

Which operating system? Turns out it's KolibriOS, the all-assembler, floppy-based x86 operating system originally based on MenuetOS.

I am genuinely excited by the Switch, and the prospects it brings to the table. I'm worried about the lineup of games - or lack thereof, really - so I'm not going to jump in straight away. The reviews of the device and its launch Zelda title are positive, though, so I'm looking forward to what Nintendo has in store for the Switch.

The just released version 17.02 of the Genode OS framework comes with greatly enhanced virtual file-system capabilities, eases the creation of dynamic system compositions, and adds a new facility for processing user input. Furthermore, the components have become binary-compatible across kernel boundaries by default such that entire system scenarios can be moved from one kernel to another without recompiling the components.

Genode's virtual file-system (VFS) infrastructure has a twisted history. Originally created as a necessity for enabling command-line-based GNU programs to run within Genode's custom Unix runtime, the VFS was later extracted as a separate library. This library eventually became an optional and later intrinsic part of Genode's C runtime. It also happened to become the basis of a file-system-server component. If this sounds a bit confusing, it probably is. But the resulting design takes the notion of virtual file systems to an new level.

First, instead of providing a system-wide VFS like Unix does, in Genode each component can have its own VFS. Technically, it is a library that turns a number of Genode sessions into a file-system representation according the component's configuration. Via those sessions, the component is able to access services provided by other components such as file systems, terminals, or block devices. Furthermore, several built-in file systems are provided locally from within the component. Since the VFS is local to each component, the view of the component's world can be shaped by its parent in arbitrary ways.

By default, each component runs in isolation. Whenever two components are meant to share a certain part of their VFS with one another, both mount a file-system session of the same server into their local VFS. This sharing is a deliberate decision by the component's common parent and thereby subjected to the parent's security policy. One particularly interesting file-system server is the so-called VFS server. It uses an arbitrarily configured VFS internally and exports its content as a file-system service, which can then be mounted in other components. This way, the VFS server can be used to emulate a "global" VFS, or to multiplex access to any file-system types supported by the VFS.

Speaking of supported file-system types, this is where the VFS becomes literally infinitely flexible. The VFS features a plugin interface that incorporates file system types provided in the form of shared libraries. If the VFS configuration refers to a file system type not known by the VFS, a corresponding plugin is loaded. For example, there exists a plugin for generating random numbers based of the jitter of CPU execution time. The file system, when mounted, hosts only a single read-only file that produces random numbers. But VFS plugins can become much more creative. Via the rump-kernel VFS plugin, one can incorporate the file systems of the NetBSD kernel into any VFS-using component. Genode 17.02 furthermore comes with a Plan-9-inspired VFS plugin that makes the Linux TCP/IP stack available as a file system. The C runtime then translates BSD-socket API calls to file-system operations on the socket file system, which, in turn, are handled by the Linux TCP/IP stack. The fascinating part is that this all happens within a single component. Such a component is in fact quite similar to a unikernel.

If two applications ought to share the same TCP/IP stack, the VFS server comes in handy. The Linux TCP/IP stack is then mounted once in the VFS server, which, in turn, provides file-system sessions to the applications. Each application then accesses the TCP/IP stack indirectly through those file-system sessions. In this scenario, the VFS server suddenly becomes a network multiplexer.

The VFS is not the only topic of the current release. Another highlight is the introduction of a application binary interface that makes all components binary compatible across kernel boundaries by default. Combined with the new kernel-independent build directories, it has become possible to move complete system scenarios from kernels as different as L4, NOVA, seL4, or Linux in matter of seconds. Further improvements of Genode 17.02 are the addition of a generic input-event processor, new SD-card drivers, the update to the version 0.8 of the Muen separation kernel, and a new mechanism for managing dynamic subsystems. All the improvements are described in detail in the release documentation.

From the EFF:

So what's the big deal?

Unfortunately, the migration away from SHA-1 has not been universal. Some programs, such as the version control system Git, have SHA-1 hard-baked into its code. This makes it difficult for projects which rely on Git to ditch the algorithm altogether. The encrypted e-mail system PGP also relies on it in certain places.

Amazing work.