Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

Monthly Archive:: May 2018

Eudora source code released

Computer History Museum (CHM), the world's leading institution exploring the history of computing and its impact on the human experience, today announced the public release and long-term preservation of the Eudora source code, one of the early successful email clients, as part of its Center for Software History’s Historical Source Code. The release comes after a five-year negotiation with Qualcomm.

The source code for both the Mac and Windows versions are released, and there's a post on Medium with more details about this latest work by the Computer History Museum.

I've never used Eudora in any serious manner, so I don't have the kind of connection with it that some others have. Still, I am always happy when 'dead' software's source code is released as open source, so that it effectively never dies.

A gorgeous guide to the first wave of personal computers

Photographer James Ball (aka Docubyte) knows what a computer is. He's spent part of career lovingly photographing the machines of yesteryear, from the giant mainframes of the '50s and '60s to the first wave of personal computers in the late '70s and '80s. When he saw Apple's iPad pro advertisement that ended with a young girl asking "What's a computer?" as she typed away on her tablet, it provoked him.

"I'm not some old technophobe, and I get the whole post-computing cloud/device blah blah thing," Ball told Motherboard via email. "But I wanted to pick up an old Mac and say 'Hey! Remember this? This is a computer. The era of crazy shaped beige boxes and clunky clicking keyboards, for me and a lot of other people, that is a computer."

To honor those machines, Ball has created a series of high resolution animated gifs honoring 16 machines from the era of the birth of the personal computer. He calls the project 'I Am a Computer: Icons of Beige.'

These are gorgeous.

PlayStation CEO: PS4 entering final phase of life cycle

PlayStation 4 is entering the final phase of its life cycle, Sony Interactive Entertainment president and CEO John (Tsuyoshi) Kodera said at Sony Investor Relations Day 2018 in Tokyo today.

The platform first launched in North America and Europe in November 2013, followed by Japan in February 2014. It has shipped 79 million units as of March 31, 2018.

Didn't I just buy a PS4 Pro? Am I the only one to whom this seems... A little premature?

Rune – Haiku images on ARM

Up until recently, Haiku builds for ARM have targetted individual ARM boards. The compile process for ARM images required two things: an architecture, and a target board (such as the Raspberry Pi 2). This board setting adjusted a large number of defines throughout Haiku at compile time to set the operating system up for the target ARM device. The board selection also handled placing all the propriety bits (a lot of which have sketchy licensing) into the Haiku image during compile. Haiku would then have to distribute these files. (sketchy licensing and all)

Over the past few years, François Revol, Ithamar R. Adema, and others have worked to add Flat Device Tree (FDT) support to Haiku. FDT’s enable operating systems to obtain core knowledge of the devices they run on by simply swapping one or more compiled binary files. These files describe critical things the operating system needs to know about the hardware they run on. Really important things such as what devices exist at what memory locations. (Think video frame buffers, serial ports, etc)

In a series of cryptic commits in July 2017, I removed these board-centric build steps with grand plans of making testing (and running) Haiku on ARM devices easier.

No, this does not mean Haiku now runs on ARM, as it has been able to do that for a while now. The goal of these changes and improvements is to speed up development of Haiku's ARM build, and to simplify the distribution of ARM builds into a single, generic ARMv7 image.

Hidden sheep and typography archaeology

Because a typeface is not just its pixels, but also its spacing, I wanted to look at the authentic source material for Chicago. That required some technical archaeology: the original Macintosh, released in 1984, was the first widely available computer that used proportional typography on screen and it had an entirely unique way of storing and managing fonts. (Standards like TrueType didn’t appear until later.)

I have some software background in typography, so I managed to extract the genuine 1984 font data using my 2018 computer. (The details of that part are a bit beside the point but are in the footnote at the bottom if you're interested). Having got the font, bitmap and spacing data for Chicago, I used the same little program to extract all the other Macintosh bitmap fonts.

Fun little bit of typography archeology on the old Macintosh.

C is not a low-level language

In the wake of the recent Meltdown and Spectre vulnerabilities, it's worth spending some time looking at root causes. Both of these vulnerabilities involved processors speculatively executing instructions past some kind of access check and allowing the attacker to observe the results via a side channel. The features that led to these vulnerabilities, along with several others, were added to let C programmers continue to believe they were programming in a low-level language, when this hasn't been the case for decades.

Processor vendors are not alone in this. Those of us working on C/C++ compilers have also participated.

The Power Mac G4 Line

The tower form factor may be a thing of the past, at least until the new Mac Pro shows up next year, but for years, if you needed the most powerful and flexible machine money could buy, the Power Mac was the only way to go.

For almost five years, the heart of the Power Mac was the PowerPC G4 chip. Starting in 1999 it clocked at just 350 MHz, but by the time the Power Mac G4 line was retired, a tower with dual 1.42 GHz CPUs could be ordered. In that time frame, things like Gigabit Ethernet, SuperDrives, and Wi-Fi became mainstream.

I have a soft spot for all Macs from the PowerPC G4 era - back when Apple wasn't boring - and the various models of Power Mac G4 aren't exceptions. I can't really explain why I find PowerPC G4 Macs so appealing, even to this day - all I know is that I am dead-set on collecting a number of them, especially those I couldn't ever afford when they were new.

Google and Microsoft disclose new CPU flaw

Microsoft and Google are jointly disclosing a new CPU security vulnerability that's similar to the Meltdown and Spectre flaws that were revealed earlier this year. Labelled Speculative Store Bypass (variant 4), the latest vulnerability is a similar exploit to Spectre and exploits speculative execution "that modern CPUs use. Browsers like Safari, Edge, and Chrome were all patched for Meltdown earlier this year, and Intel says these mitigations are also applicable to variant 4 and available for consumers to use today."

However, unlike Meltdown (and more similar to Spectre) this new vulnerability will also include firmware updates for CPUs that could affect performance. Intel has already delivered microcode updates for Speculative Store Bypass in beta form to OEMs, and the company expects them to be more broadly available in the coming weeks. The firmware updates will set the Speculative Store Bypass protection to off-by-default, ensuring that most people won’t see negative performance impacts.

This cat ain't going back in no bag anytime soon.

Windows 95 could run Windows 3.1 in a virtual machine

And the second The Old New Thing story, about adding a Windows 3.1 virtual machine to Windows 95.

As the Windows 95 project started to come together, I was approached to undertake a special project: Run Windows 3.1 in an MS-DOS virtual machine inside Windows 95.

This was the ultimate in backward compatibility, along multiple axes.

First of all, it was a demonstration of Windows 95's backward compatibility by showing that it could even use an emulated MS-DOS virtual machine to run the operating system it was designed to replace.

Second, it was the ultimate backward compatibility ripcord. If you had a program that simply wouldn't work with Windows 95 for whatever reason, you could fire up a copy of Windows 3.1 in a virtual machine and run the program there.

To use it, you installed Windows 3.1 and Windows 95 into separate directories, and then made a few edits to the Windows 3.1 SYSTEM.INI file to replace the mouse and serial drivers with special versions. There were some other preparatory steps that had to be done, but eventually you got to the point where you could double-click the Windows 3.1 icon, and up came Windows 3.1 in an MS-DOS virtual machine.

This is quite similar to how Windows 3.x worked in OS/2 at the time.

Why is Windows ZIP support stuck at the turn of the century?

I've got two fun The Old New Thing stories for you today, starting with a story about Windows' ZIP file support.

Every so often, a customer will ask whether Windows Compressed Folders (Zip folders) supports something fancy like AES encryption, and we have to shake our head and apologize. "Sorry, no."

Why this sad state of affairs?

The compression and decompression code for Zip folders was licensed from a third party. This happened during the development of Windows XP. This means that the feature set of Zip folders was locked to whatever features were hip and cool as of around the year 2000.

You'd think Windows would eventually start supporting other archive formats as well, but no.

299 macOS apps are so buggy, Apple fixes them in AppKit

What do Photoshop, Matlab, Panic Transmit, and Eclipse have in common? They are among the 299 apps for which macOS applies compatibility fixes.

Here's the full list of bundle IDs, along with the functions that checks for them, and the first caller to those functions. It's also available in CSV format.

Note that this is just a list of apps Apple has developed compatibility tweaks to make them run on newer macOS versions. As the list demonstrates, even the best apps often needs some tweaks on newer macOS. In addition, most of these patches are only applied to older versions of apps.

Here's how I extracted the list, and some interesting things I found in it.

This is absolutely fascinating, and provides some amazing insight into which applications Apple considers crucial to the macOS user experience and platform. We all know Windows performs various tricks to maintain backwards compatibility, but I had no idea Apple went to decent lengths too for the same reasons.

Google makes two different versions of Android

We go through this every time a new version comes to Google's own phones while we wait for it to come to the rest. And the outcome is always the same - Pixel phones (and previous Nexus phones) look the way Google wants them to look and the rest of the phones look however the company that made them want them to look. That's because you can't see Android - it's simply software that supports the things you're looking at.

It's confusing. And tech bloggers (myself included) don't help ease the confusion very well when we write about the things we see on a software update for the Pixel. It's too difficult to try and break everything down every time we write something, and while we are good at a lot of things, we tend to shy away from "difficult". To compound it all, when we do try to break "Android" down, we usually make it worse. I'm going to try here because I'm feeling courageous and want to face "difficult" head on today. If I don't come back, tell my wife I love her.

Android is quite a complicated term, entity, and operating system.

Razer Phone XDA display analysis

When contemplating who’d be a major player in the Android smartphone business, the gaming hardware giant Razer probably doesn’t come to mind. While they have yet to establish themselves as a reliable smartphone provider, Razer’s first attempt did not at all seem like it was their first time dabbling into Android, likely because much of their engineering team came from Nextbit. Razer leveraged their status in gaming hardware to appeal to those who game, and those who game hold high refresh rate monitors in high regard. So Razer put one on a smartphone.

This article takes a close look at the Razor phone's display, which is rather unique among Android phones for its 120Hz refresh rate (iPhones have 120Hz displays as well).

Europe gets more open-access as university stand-offs spread

Bold efforts to push academic publishing towards an open-access model are gaining steam. Negotiators from libraries and university consortia across Europe are sharing tactics on how to broker new kinds of contracts that could see more articles appear outside paywalls. And inspired by the results of a stand-off in Germany, they increasingly declare that if they don’t like what publishers offer, they will refuse to pay for journal access at all. On 16 May, a Swedish consortium became the latest to say that it wouldn't renew its contract, with publishing giant Elsevier.

A lot of this research in partially or fully tax-funded, and as such, published articles must be freely available to the public. Good development.

Hands-on with the RED Hydrogen One

We just got a look at the upcoming RED Hydrogen One smartphone at an event meant for "RED Pioneers" (read: superfans). It is, without a doubt, one of the most ambitious smartphones in years from a company not named Apple, Google, or Samsung. It's an Android phone with a 5.7-inch display and top-tier phone specs, but that description doesn't do justice to what RED is trying to accomplish here.

The company better known for high-end 4K cameras with names like "Weapon" and "Epic-w" isn't entering the smartphone game simply to sell you a better Android phone (though it does have both Verizon and AT&T signed on to support it). No, this phone is meant to be one piece of a modular system of cameras and other media creation equipment - the company claims it will be "the foundation of a future multi-dimensional media system".

I doubt this phone will ever have any mass-market success, but that's not really the point anyway. I like that RED is trying something new, something different, and takes it to the extreme with this industrial design. The module system here is different from previous failed attempts at doing so in that it's designed to tie in with RED's popular and expensive camera's and lenses from other big camera brands, instead of trying to appeal to the mass market.

This might actually work out.

Inside the 76477 Space Invaders sound effect chip

The 76477 Complex Sound Generation chip (1978) provided sound effects for Space Invaders and many other video games. It was also a popular hobbyist chip, easy to experiment with and available at Radio Shack. I reverse-engineered the chip from die photos and found some interesting digital circuitry inside. Perhaps the most interesting is a shift register based white noise generator, useful for drums, gunshots, explosions and other similar sound effects. The chip also uses a digital mixer to combine the chip's different sound generators. An unusual feature of the chip is that it uses Integrated Injection Logic (I2L), a type of digital logic developed in the 1970s with the goal of high-density, high-speed chips.

iOS developers form union to pressure Apple

A number of prominent third-party iOS developers have formed a union to put pressure on Apple to change several App Store policies.

We believe that people who create great software should be able to make a living doing it. So we created The Developers Union to advocate for sustainability in the App Store.

Today, we are asking Apple to publicly commit - by the tenth anniversary of the App Store this July - to allowing free trials for all apps in the App Stores before July 2019. After that, we'll start advocating for a more reasonable revenue cut and other community-driven, developer-friendly changes.

I've railed against the long-term sustainability of the application store model for years now, long before it became en vogue in wider developer circles. I absolutely love the idea of independent developers forming a union - even if it's not a literal union - as a means to put pressure on Apple, Google, and other owners of application stores to take better care of developers.

At the same time, I fear that they are too late - the vast majority of the App Store's revenue comes from crappy pay-to-win mobile games, not from well-made, lovingly crafted applications. I simply don't think these developers are important enough to a bean-counting bottom-liner like Tim Cook.

Google’s Duplex will warn that calls are recorded

Since Google revealed a robo-caller that sounds eerily human earlier this month, the company has faced plenty of questions about how it works. Employees got some answers this week.

On Thursday, the Alphabet Inc. unit shared more details on how the Duplex robot-calling feature will operate when it's released publicly, according to people familiar with the discussion. Duplex is an extension of the company's voice-based digital assistant that automatically phones local businesses and speaks with workers there to book appointments.

At Google’s weekly TGIF staff meeting on Thursday, executives gave employees their first full Duplex demo and told them the bot would identify itself as the Google assistant. It will also inform people on the phone that the line is being recorded in certain jurisdictions, the people said. They asked not to be identified discussing private matters. A Google spokesman declined to comment.

This is a good step, and while the technology is awesome, I'm still quite reluctant about whether or not we really need this. Aside from the very legitimate use cases for people with disabilities, to whom this technology could be life-changing, I'm wondering just what regular users get out of it.

Pie menus: a 30 year retrospective

Today (May 15, 2018) is the 30 year anniversary of CHI'88 (May 15-19, 1988), where Jack Callahan, Ben Shneiderman, Mark Weiser and I (Don Hopkins) presented our paper "An Empirical Comparison of Pie vs. Linear Menus". We found pie menus to be about 15% faster and with a significantly lower error rate than linear menus!

This article will discuss the history of what's happened with pie menus over the last 30 years (and more), present both good and bad examples, including ideas half baked, experiments performed, problems discovered, solutions attempted, alternatives explored, progress made, software freed, products shipped, as well as setbacks and impediments to their widespread adoption.

Fantastic read with fantastic examples. Set some time aside for this one - you won't regret it.

GDPR hysteria

In another week the GDPR, or the General Data Protection Regulation will become enforceable and it appears that unlike any other law to date this particular one has the interesting side effect of causing mass hysteria in the otherwise rational tech sector.

This post is an attempt to calm the nerves of those that feel that the(ir) world is about to come to an end, the important first principle when it comes to dealing with any laws, including this one is Don’t Panic. I’m aiming this post squarely at the owners of SME’s that are active on the world wide web and that feel overwhelmed by this development. A bit of background about myself: I’ve been involved in the M&A scene for about a decade, do technical due diligence for a living (together with a team of 8). This practice and my feeling that the battle for privacy on the web is one worth winning which has led me to study online privacy in some detail puts me in an excellent position to see the impact of this legislation first hand as well as how companies tend to deal with it.

The GDRP is not nearly as draconian or complex as people are scared into believing (mostly by people who conveniently also sell GDRP compliance services). Over the past few weeks and months, I've translated countless internal and external corporate documents about the GDPR from companies both big and small, for all kinds of sectors, many of which you know, and none of them are freaking out and none of them find this particularly difficult or complicated. Even a legal simpleton like me understands it just fine, and all I need to do is translate texts about it.