Google’s not-so-secret new OS

I decided to dig through open source to examine the state of Google's upcoming Andromeda OS. For anyone unfamiliar, Andromeda seems to be the replacement for both Android and Chrome OS (cue endless debates over the semantics of that, and what it all entails). Fuchsia is the actual name of the operating system, while Magenta is the name of the kernel, or more correctly, the microkernel. Many of the architectural design decisions appear to have unsurprisingly been focused on creating a highly scalable platform.

It goes without saying that Google isn't trying to hide Fuchsia. People have clearly discovered that Google is replacing Android's Linux kernel. Still, I thought it would be interesting for people to get a better sense of what the OS actually is. This article is only intended to be an overview of the basics, as far as I can comment reasonably competently. (I certainly never took an operating systems class!)

What excites me the most about Fuchsia and related projects are the people involved. The pedigree here is astonishing - there are quite a few former Be, Palm, and Apple engineers involved. The linked article contains a good higher-level overview, and I do truly believe it's one of the most exciting projects in the operating systems world right now.

What remains to be seen, however, is this: just how serious is this project? The breadth of the project and the people involved seem to suggest this is indeed something quite serious, and all signs point towards it being a future unification and replacement for both Chrome OS and Android, which is quite exciting indeed.

HMD Global will launch Nokia 3310 homage

But perhaps the most interesting of these devices, at least from the perspective of mobile enthusiasts, is not a smartphone at all, but a modern version of a classic workhorse of a feature phone, the Nokia 3310. Known primarily for its plentiful battery life and nearly indestructible build, the 3310 was released at the turn of the millennium as a replacement to the also-popular 3210.

At just €59, this new incarnation seems priced competitively enough to win over nostalgic former owners for use as a second phone.

This is amazing. The 3310 is one of the most iconic pieces of technology ever created.

Operating system: from 0 to 1

Probably you asked yourself at least once, how an Operating System (OS) was written from the ground up? You probably have spent years programming, but still understand operating system as a collection of abstract concepts, not how to implement an operating system in actual code. In your mind, somehow the operating system can magically control the underlying hardware and do what you want through the higher level API of your favorite programming language. You wish to understand the details, but for some reason, it seems too difficult because regardless how much you learn, it is never enough. You may feel that you are missing an important piece of the puzzle, and get stuck. However, deep inside you still want to write an operating system without a crystal clear understanding. After all, you are a software engineer, and an operating system is a software. You should know your software better than anyone else!

If that is the case, this book is for you. By going through this book, you will be able to find the missing piece that is essential and enable you to implement your operating system, from scratch!

A free detailed book about writing your first operating system.

“A great disturbance in the force…”

The news is that after 15 years the IMDb is closing down its message boards, but the story is their creation in the first place: a tale of Apache, mod_perl, PostgreSQL, C, and XEMacs, all served up on a BeOS bun in a Bristol-area cafeteria; of missed deadlines, missed opportunities and misplaced innocence given the scale of comments, comment spam and trolling up to that point. Brought to you by Colin M. Strickland, a developer whose CV has long read "you can blame me for the message boards" (and yes, he does go by the initials cms).

POSIX has become outdated

The POSIX standard for APIs was developed over 25 years ago. We explored how applications in Android, OS X, and Ubuntu Linux use these interfaces today and found that weaknesses or deficiencies in POSIX have led to divergence in how modern applications use the POSIX APIs. In this article, we present our analysis of over a million applications and show how developers have created workarounds to shortcut POSIX and implement functionality missing from POSIX.

The first official Mac clone: Daydream

A neat piece of computing history - a combination of a hardware dongle and software that lets you run up to System 7 on a NeXT machine (and with some hacking, Mac OS 8).

The latest addition to my NeXT/Mac collection, a Daydream ROM box made in about 1993 by Quix Computerware AG. This unit plugged into the host NeXT's DSP port and contained genuine licensed Macintosh LC ROMs. This allowed the NeXT to boot off the ROMs and thus become a Mac. It was the first time Apple licensed Mac ROMs to a 3rd party and also offered the same performance as a Quadra 950 at a much lower price point and that was including the purchase of the NeXT system. It ran up to system 7.5 officially though with a few hacks 8.1 can be made to run. It is not a Mac virtual machine; it actually boots as a Mac.

The manual contains more information, and it explains that Daydream installs a secondary kernel that in turn boots the Mac ROM.

This in and of itself is quite cool, but as it turns out, that's not where the story ends. People - including some of the original Daydream developers - have hacked this tool to remove the need for the hardware ROM dongle by inserting the ROM directly into the secondary kernel. This means that if you have a 68k NeXT machine, you can boot directly into System 7 or Mac OS 8. Or, more likely, if you have a NeXT emulator such as Previous, you can boot your NeXT emulated machine directly into System 7 or Mac OS 8 (video).

Incredibly cool, and I had no idea this existed. While NeXT and Apple people were doing these awesome things, I was still using MS-DOS. Strange realisation.

Steam opens up with Steam Direct

When we consider any new features or changes for Steam, our primary goal is to make customers happy. We measure that happiness by how well we are able to connect customers with great content. We've come to realize that in order to serve this goal we needed to move away from a small group of people here at Valve trying to predict which games would appeal to vastly different groups of customers.

Thus, over Steam's 13-year history, we have gradually moved from a tightly curated store to a more direct distribution model. In the coming months, we are planning to take the next step in this process by removing the largest remaining obstacle to having a direct path, Greenlight. Our goal is to provide developers and publishers with a more direct publishing path and ultimately connect gamers with even more great content.

This is a big step for Steam, and will make it incredibly trivial for developers and publishers alike to publish games on Steam.

Bored with ho-hum cloud backups? Use Usenet instead

Unfortunately, this kind of service isn' t free, and the cost can be a barrier. However, there is a cost-effective way to store your cloud backups: Usenet. With access to a Usenet news server, you can simply upload your backup there, and it will be stored redundantly in news servers all over the world. Best of all, this approach typically costs considerably less than a cloud backup service.

Obviously, this is not your typical method of cloud storage. Many may snicker or find it plain weird to tap into this vintage part of the Internet in such a modern way. But oddly enough, we have experience experimenting with this alternative offline storage when it comes to backing up a Linux system. And backing up your Linux system to usenet ultimately requires only a handful of steps. It's not only possible - it's scriptable, too.

I didn't know this was possible, but that's mostly because I never thought of it. Clever.

Sailfish OS 2.1.0 released

This update, 2.1.0 alias Iijoki brings major architectural changes to Sailfish OS by introducing Qt 5.6 UI framework, Bluez5 Bluetooth protocol (ready to be deployed for development purposes), basics for the 64-bit architecture and text selection in browser. Included is also a beta level implementation for Virtual Private Networks (VPN) (please read release notes) and the first version of QML live coding support. In addition, 2.1.0 adds bigger fonts to the UI, improves the use of camera and fixes a number of errors, many of which were reported by our developer community.

Maybe I'll get around to updating my Jolla phone and tablet at some point, but I really don't see a reason why. Since I reviewed Sailfish OS and the Jolla phone more than three years ago, nothing has been done to address the elephant in the room. The operating system itself was quite stable, good-looking and full-featured from the beginning, and that has only improved with the constant stream of updates and refinements. However, the application situation is still incredibly dire, and we're all still using the same few applications - updated only very infrequently - that we were using three years ago. Several have even died out.

Instead of investing in attracting developers to write Sailfish applications (the three year old promises of support for paid applications still hasn't been fulfilled, for instance), the company got distracted with crazy projects like the tablet, and investing heavily in making Android applications 'run' on Sailfish. While Android applications do 'run', it's still a slow, frustrating, and utterly jarring experience that's a complete and utter waste of resources. Had they spent even half the effort spent on Android application compatibility on attracting native developers, the platform would be in a far better state.

Jolla proclaimed they wanted to take over the world, but in doing so, lost touch with the very people they should've continued to focus on: open source/Linux-oriented enthusiasts, former Maemo/N900 users. Not a large group of people, of course, but definitely a big enough - and, more importantly, loyal enough! - group of people to sustain a small, community-focused company.

Whatever.

Jolla's CEO Sami Pienimäki penned a letter to the community about upcoming developments for the company. There's some stuff in there about Russia and tablet refunds.

Android Wear 2.0 review: Google’s second swing at smartwatches

Android Wear 2.0 is also buggier than it should be, especially given the fact that it had an extended public beta period and its launch was delayed by months. Beyond them taking a long time to launch, it can be hard to tell when an app is actually launching, because the screen will flicker back to the list of apps before it will launch the one you just tapped. The Google Assistant also crashed often, forcing me to repeat my inquiry multiple times (or more likely, I just get frustrated with it and pull out my phone).

The changes and improvements look decent, but if you don't first get the above things right, they're all for naught. When will software makers learn that performance - especially UI responsiveness - is the single most important part of a consumer-oriented device?

Not that it matters to me - for some mysterious reason, these new watches won't be coming to The Netherlands. They're coming to the rest of Europe - just not The Netherlands. The Google Pixel is also still pretty much sold out in the two or three countries where it's supposedly available, with no indication they're ever going to be available elsewhere.

Here's a tip, Google: if you want to be a successful hardware maker, maybe make sure interested consumers can actually, you know, buy your stuff?

Microsoft hosts the Windows source in a 300GB Git repository

Just as Windows' development had become complex and fragmented, so too did the company's internal systems for things like source control, issue tracking, testing, building, code analysis, and all the other tasks that fall under the application lifecycle management umbrella. And just as Windows' development was unified as OneCore, the company has embarked on an effort to unify its ALM and develop what it calls One Engineering System (1ES).

The cornerstone of 1ES is TFS, but for 1ES, the company wanted to do more than just standardize on TFS; it wanted to switch to a single version control system. TFVC, Source Depot, and Git were the obvious contenders, though other options such as Mercurial were also considered. In the end, the company standardized on Git.

Why reinvent the wheel all the time, when you can just use a tool everybody else is already using anyway?

The Windows for Workgroups launch event

Due to an SSD failure last year, I lost a bunch of my virtual machines, including my Windows 3.11 virtual machine. I don't actually use these for anything, but I like having these old operating systems at my fingertips, in case, I don't know, the world is about to end and the only way to prevent it is to run a very specific Windows 3.11-only application. So, yesterday, I recreated the virtual machine.

This seems like an excellent opportunity to link to the original Windows for Workgroups (Windows 3.11) launch event, from October 1992. I'm not even going to try to characterise or summarise this event, because it's so incredibly Microsoftian and '90s, the English language simply doesn't contain enough words to paint an accurate picture.

I grew up with MS-DOS and later Windows 3.x, so this is a strange, somewhat... Twisted throwback to... Let's call it 'simpler' times.

Haiku’s Augustin Cavalier on the Lunduke Hour

Augustin Cavalier (also known as Waddlesplash) was a guest on The Lunduke Hour, where he explains a lot about what's been going on with the Haiku project for the last couple of years, and why it's been so long from Alpha 4 to the upcoming Beta 1.

Cavalier goes into Haiku's rather unique package management system, progress on the application front, and tons of other things. Definitely worth a listen.

Internet shutdown hits businesses in Cameroon

Business owners in the town of Buea, the capital of the Southwest Region of Cameroon say they are struggling to operate following an internet shutdown that began on January 17. Internet users here say that they can no longer communicate or access information, particularly on social media. Many internet cafes, micro finance institutions and money transfer agencies have had to shutdown.

"When things like this happen and they just ban the internet which is the source of my livelihood. I just feel like maybe I made the wrong decision. Maybe I should just leave the country like my friends and never return again. And I personally feel bad that that would be unpatriotic on my part but you know, we have to do what we have to do sometimes. And now I don’t even know if the Internet will be returned. I don't know when it will be returned," said IT entrepreneur, Churchill Mambe.

It's remarkable how important the internet has become, especially in developing countries.

What Vizio was doing behind the TV screen

What did Vizio know about what was going on in the privacy of consumers' homes? On a second-by-second basis, Vizio collected a selection of pixels on the screen that it matched to a database of TV, movie, and commercial content. What's more, Vizio identified viewing data from cable or broadband service providers, set-top boxes, streaming devices, DVD players, and over-the-air broadcasts. Add it all up and Vizio captured as many as 100 billion data points each day from millions of TVs.

Vizio then turned that mountain of data into cash by selling consumers' viewing histories to advertisers and others. And let’s be clear: We're not talking about summary information about national viewing trends. According to the complaint, Vizio got personal. The company provided consumers' IP addresses to data aggregators, who then matched the address with an individual consumer or household. Vizio's contracts with third parties prohibited the re-identification of consumers and households by name, but allowed a host of other personal details - for example, sex, age, income, marital status, household size, education, and home ownership. And Vizio permitted these companies to track and target its consumers across devices.

That's... That's a lot of very creepy spying.

Blue Lion, the next OS/2, moves into beta testing

Per Arca Noae's revised release schedule, and as announced at Warpstock 2016, Blue Lion (ArcaOS 5.0) moved into beta testing stage today. The first beta release has been made available to the test team, and we anticipate a rigorous round of installation, modifications, formatting, deletion, disk wiping, and all that other fun stuff which accompanies a healthy beta test.

We do not anticipate a public beta cycle nor are we planning a gamma release or an untold number of release candidates. Instead, we fully expect ArcaOS 5.0 to emerge from beta testing at the end of March and to become generally available at that time.

As mentioned during earlier coverage, ArcaOS is a sort-of continuation of eComStation, since it's founded by several eCS developers who felt eCS had ground to a halt.

The open source Amiga DVI/HMDI graphics card: MNT VA2000

The VA2000 is a FPGA based graphics card for Amiga 2000/3000/4000 computers featuring high resolutions and color depth over DVI-D/HDMI. It has a hacker-friendly expansion header for upgrades and custom mods and features a slot for MicroSD cards that can be mounted in AmigaOS.

The YouTube video provides additional insight into the open source graphics card. Interestingly enough, I've been looking into getting my hands on a classic Amiga, but the one I would want - an A3000 or A4000 - are quite hard to come by here in The Netherlands.

The curious case of NextStep on AIX

This is interesting: it turns out there was a NextStep release for IBM AIX workstations. From the initial, archived press release (via Steven Troughton-Smith):

AIX PS/2 NextStep Environment Version 1.1 is a state-of-the-art graphical user interface and programming environment for AIX workstations, designed to be compatible with the same application programming interface (API) as the NextStep product, Software Release 1.0, provided by NeXT, Incorporated.

AIX PS/2 NextStep Environment Version 1.1 provides icons and menus to facilitate access to system utilities and applications. The AIX NextStep Interface Builder is designed to provide a rich set of well-defined objects and graphical cut-and-paste capabilities for designing and implementing application user interfaces. The Objective-C (3) Compiler provides the benefits of object-oriented programming for developers who choose to design additional objects for the application development environment. AIX PS/2 NextStep Environment can help increase the productivity of programmers and end users.

Steven Troughton-Smith, who has a thing for collecting NEXT/early OS X builds and versions, is now looking for this piece of software history, but not a whole lot can be found about this online. I did ran into a thread in comp.sys.next.advocacy from 1995 in which a Robin D. Wilson sheds some more light onto the fate of this product:

And we ran it on an RS/6000 model 540 (with 63MB of RAM no less) -- it was pretty fast. The thing that killed it is Steve Jobs wanted IBM pay more money for 2.0. They had only _just_ finished porting 1.0 to AIX (it did run on top of AIX -- and there were several hacks made to accomodate it -- but it did run fine). When NeXT was shipping 2.0, IBM felt they wouldn't be able to sell 1.0 (there we some rather dramatic improvements between 1.0 and 2.0). They also didn't want to spend more money on it (as SJ was demanding for 2.0), and they didn't feel like porting 2.0 would take any less time (meaning they wouldn't get done until NeXT released a newer version). All that considered -- IBM abandoned NS.

This wasn't a "bad decision" by SJ (per se), but I can see IBM's view on this easier than I can see NeXT's...

Steven also stumbled upon a very, very long FAQ about NextStep/AIX, which contains tons of information. This will probably be very hard to find, but for the sake of digital archaeology and preservation, we really need to find it somewhere and preserve it. Absolutely fascinating.

The enviable pedigree of UNIX and POSIX

But today's breakthroughs would be nowhere and would not have been possible without what came before them - a fact we sometimes forget. Mainframes led to personal computers, which gave way to laptops, then tablets and smartphones, and now the Internet of Things. Today much of the interoperability we enjoy between our devices and systems - whether at home, the office or across the globe - owes itself to efforts in the 1980s and 1990s to make an interoperable operating system (OS) that could be used across diverse computing environments - the UNIX operating system.

As part of the standardization efforts undertaken by IEEE, it developed a small set of application programming interfaces (APIs). This effort was known as POSIX, or Portable Operation System Interface. Published in 1988, the POSIX.1 standard was the first attempt outside the work at AT&T and BSD (the UNIX derivative developed at the University of California at Berkeley) to create common APIs for UNIX systems. In parallel, X/Open (an industry consortium consisting at that time of over twenty UNIX suppliers) began developing a set of standards aligned with POSIX that consisted of a superset of the POSIX APIs. The X/Open standard was known as the X/Open Portability Guide and had an emphasis on usability. ISO also got involved in the efforts, by taking the POSIX standard and internationalizing it.

A short look at the history of UNIX standardisation and POSIX.

Fearful of hacking, Dutch will count ballots by hand

Let's talk about elections! Except not the American ones, but the Dutch elections, coming up in March.

Concerned about the role hackers and false news might have played in the United States election, the Dutch government announced on Wednesday that all ballots in next month's elections would be counted by hand.

We haven't been using electronic voting ever since it was demonstrated the machines were quite easily hackable, but everything higher up in the stack was still electronic - such as counting the paper ballot and tallying up the results from the individual voting districts. The upcoming election will now be entirely done by hand - voting, counting, and tallying, making it that much harder for foreign powers to meddle in our elections.

This switch to full manual voting is taken two days after Sijmen Ruwhof posted a detailed article explaining just how easy it would be to hack our voting process.

Journalists from Dutch TV station RTL contacted me last week and wanted to know whether the Dutch elections could be hacked. They had been tipped off that the current Dutch electoral software used weak cryptography in certain parts of its system (SHA1).

I was stunned and couldn't believe what I had just heard. Are we still relying on computers for our voting process?

Turns out the "security" of the counting machines and software, as well as the practices of everything around it, is absolutely terrible. The article is an endless stream of facepalms - and really shines a light on just how lacklustre the whole electronic part of the process was, and hence provides an interesting look behind the scenes of an election.