Monthly Archive:: October 2017

Apple let a few YouTubers post the first iPhone X reviews

Update (original story below): the real review embargo has been lifted, and it turns out Apple gave reviewers only 24 hours between handing over the phone and lifting the embargo. This raised another red flag for me, and my red flags may have merit: it turns out Face ID is not exactly without issues. Nilay Patel details that while Face ID works quite well inside, it has issues outside in the sun or under fluorescent lighting. It regularly just wouldn't recognise his face in these environments.

The other problem is actually much more interesting: almost all of the early questions about FaceID centered around how it would work in the dark, but it turns out that was exactly backwards. FaceID works great in the dark, because the IR projector is basically a flashlight, and flashlights are easy to see in the dark. But go outside in bright sunlight, which contains a lot of infrared light, or under crappy florescent lights, which interfere with IR, and FaceID starts to get a little inconsistent.

I took a walk outside our NYC office in bright sunlight, and FaceID definitely had issues recognizing my face consistently while I was moving until I went into shade or brought the phone much closer to my face than usual. I also went to the deli across the street, which has a wide variety of lights inside, including a bunch of overhead florescent strips, and FaceID also got significantly more inconsistent.

I'm not spending a lot more time on iPhone X reviews today, because it's impossible to review a phone in 24 hours. Beware of the reviews you're reading online today, and to Patel's credit, they clearly label their "review" as a work-in-progress draft that they'll be updating based on questions from users. As such, it doesn't carry any advice or grades or anything like that, which is commendable. I haven't had time to dive into other 24-hour "reviews" just yet (it's the middle of a workday here, after all).

All in all, this is a very strange launch and review situation, and while it's too early to tell if Apple is truly insecure, the early signs of Face ID issues definitely don't help to alleviate my red flags.




Apple's iPhone X - its most anticipated new phone in a very long time - goes on sale this Friday, Nov. 3.

So sometime this week, as usual, you'll be able to read and watch a bunch of serious-sounding reviews, as Professional Gadget Reviewers critique everything from bezels to battery life.

But Apple did something different this year. It invited a handful of YouTubers you probably haven't heard of to its fancy penthouse in New York, gave them some early hands-on time with the iPhone X, and let them publish their videos a day or more in advance of the official reviews. (It also let Wired/Backchannel's Steven Levy write a "first first impression of the iPhone X" post because Steven Levy. It also gave one to Axios co-founder Mike Allen, who had his nephew play with it. And Mindy Kaling for Glamour. And The Ellen Show.)

This is quite remarkable. Why would Apple invite a number of relatively unknown YouTubers to a fancy event, hand them a few restrictive talking points and an hour or so of hands-on-time, and allow them to call their videos "reviews", well before the real review embargo is lifted? This is basically just a repeat of the hands-on time journalists, bloggers, and YouTubers got after the launch event a few weeks ago.

This is a carefully orchestrated "control the message" type of thing, and all the videos are practically identical, with the same limited number of talking points, all shot in the same fancy nondescript loft-like Apple Store (?) somewhere in New York City.

Apple clearly wanted this to be the first thing people saw of the iPhone X. No critical reviews by detail-oriented people like MKBHD, Dieter Bohn or heck, even John Gruber (who is not happy with this). No, Apple invited small-time YouTubers who are easily impressed to make the video of their lifetimes to ensure they'd get nothing but shallow, fuzzy good press.

It reeks of insecurity, and if I didn't know any better, I'd be very worried about just what the heck is wrong with this phone.

When man meets metal: rise of the transhumans

Earlier this year I went to an event in Austin, Texas, billed as a sneak preview of the evolution of our species. The #Bdyhax Conference, which took place in a downtown exhibition complex, promised a front-row insight into the coming "singularity" - that nirvana foretold by science fiction in which biology and technology would fuse and revolutionise human capability and experience.

The headline acts of the conference were mostly bodyhackers - DIY experimenters who, in their basements and garages, seek to enhance their own flesh and blood with biometric implants and cognitive enablers. These brave pioneers were extending their senses, overcoming physical limitation, Dan-Daring themselves and the rest of us into the future.

This will only get more advanced as the years go by. For now, actual technological augmentations and implants are mostly reserved for people who actually need them - things like prosthetic legs or a pacemaker - but eventually, we'll start to develop augmentations to enhance the senses or abilities of the human body for people who are otherwise healthy.

Your body, your rules, but scary nonetheless.

Replacing exploit-ridden firmware with a Linux kernel

Two weeks ago, security researchers managed to disable the Intel Management Engine, and last week, Google held a talk at the Open Source Summit (née LinuxCon) in which they unveiled their plans to completely (well, almost completely) replace every bit of code between the operating system you know about (Windows, Linux, BSD, whatever) and the bare metal x86 processor (Intel-only, for now).

With the WikiLeaks release of the vault7 material, the security of the UEFI (Unified Extensible Firmware Interface) firmware used in most PCs and laptops is once again a concern. UEFI is a proprietary and closed-source operating system, with a codebase almost as large as the Linux kernel, that runs when the system is powered on and continues to run after it boots the OS (hence its designation as a "Ring -2 hypervisor"). It is a great place to hide exploits since it never stops running, and these exploits are undetectable by kernels and programs.

Our answer to this is NERF (Non-Extensible Reduced Firmware), an open source software system developed at Google to replace almost all of UEFI firmware with a tiny Linux kernel and initramfs. The initramfs file system contains an init and command line utilities from the u-root project (http://u-root.tk/), which are written in the Go language.

Both the slides from the talk and the video are available.

The iPad Pro as main computer for programming

In the summer of 2017, I wanted to know what it would be like to use an iPad Pro as my main computer. I found out that it can actually work, thanks to an iOS app called Blink, an SSH replacement called Mosh, iOS 11 and running stuff on a server.

You could argue the title is a tad bit misleading - there's a lot of thin client DNA in his setup - but it's an interesting look at how to achieve this, nonetheless.

Google Pixelbook review: emperor of Chrome

Dieter Bohn:

When I think about whether the Pixelbook could reasonably replace a MacBook or a Windows laptop, my gut says that, for most people, the answer is "no." To solve the "last 10 percent" on a Pixelbook, you really have to be very savvy about how to navigate the different computing paradigms of Chrome and Android to make the whole thing work - and even then, it's not easy. Unless you're an expert in the ways of both the web and Android, it shouldn't be your only computer.

If I were Apple or Microsoft, I would be thinking a lot about the generation of students who are savvy with Chromebooks and Android apps, and who might just want the same thing they're used to from their classroom, just in a much nicer package. I don't know that it'll happen this year, though.

Honestly, I think the iPad Pro is a better comparison. On both devices, you can get quite a lot more done than you'd expect, but you have to deeply understand how the platform works to get there. And if you're debating between them, here's the TL;DR: the iPad Pro has better apps, is a tablet-first device, and has a worse web browser. The Pixelbook has worse apps, is a laptop-first device, and has a better web browser.

Dieter Bohn hits the nail on the head here - devices like the iPad Pro or the Pixelbook aren't so much about converting traditional longtime desktop/laptop users - they're about making sure that kids currently growing up with iOS and Android/Chrome OS devices in their pocket or at school have a powerful, all-purpose computing device they already know how to work with and that they already like for the future. It's similar to how people wanted to have the same computer at home as they were using at work - IBM-compatible PCs with DOS and later Windows.

The fact that the iPad Pro and Pixelbook are already as good as they are should really worry Microsoft, most of all.

AMD’s Ryzen CPU with Vega graphics threatens Kaby Lake

AMD's Ryzen and Threadripper processors re-established AMD's chips as competitive with Intel's. While the AMD parts gave up a bit of performance to their Intel rivals, especially in single-threaded tasks - a result of the combination of slightly lower clock speeds and slightly inferior instructions-per-cycle (IPC) - they shine in multithreaded tasks, with AMD often offering many more cores and threads than Intel for the same or less money.

In the mainstream desktop space, Intel's Coffee Lake chips have reasserted that company's dominance; Skylake-X does the same in the high-end desktop space, too, albeit at a high price.

But things are looking like they're going to be different in the mobile space. That's because the two new chips, the Ryzen 7 2700U and Ryzen 5 2500U, show signs of being faster in both processor and graphics tasks than Intel's latest comparable chips.

These chips also bode well for supposed upcoming AMD APUs, which I'm looking forward to as a way to build a relatively cheap but still powerful secondary machine.

Google releases Android 8.1 preview, Android Studio 3.0

Today we're giving you an early look at Android 8.1. This update to Android Oreo includes a set of targeted enhancements including optimizations for Android Go (for devices with 1GB or less of memory) and a new Neural Networks API to accelerate on-device machine intelligence. We've also included a few smaller enhancements to Oreo in response to user and developer feedback.

Android 8.1 while literally nobody is even using Android 8.0 yet. OK Google, OK.

Coinciding with the Android 8.1 developer preview, Google also released Android Studio 3.0.

This release of Android Studio is packed with many new updates, but there are three major feature areas you do not want to miss, including: a new suite of app profiling tools to quickly diagnose performance issues, support for the Kotlin programming language, and a new set of tools and wizards to accelerate your development on the latest Android Oreo APIs.

Office Mobile is much more than a simple set of mobile apps

Microsoft's set of Office Mobile apps are great. I prefer them over the full Office suite. I realize that a lot of people find the Office Mobile apps to be subpar. But there are people out there for whom the Office Mobile apps are more than fine. Why isn't Microsoft doing anything with them?

I posed this same question not too long ago. The Metro Office applications are the best Metro applications out there, and they prove it's definitely possible to build good, useable, fast, and useful Metro applications. I find it entirely baffling that Microsoft is doing whatever it takes to push users to the slower, more cumbersome, overloaded, and entirely overkill Win32 Office applications. If Microsoft implemented the ability to open multiple instances of each app, most people would get by just fine with the Metro ones.

Purism Librem laptops disable Intel’s Management Engine

Only a few weeks after the news that security researchers had managed to completely disable the Intel Management Engine, Purism has announced it's disabling the IME on all of its available Librem laptops.

Purism's Librem Laptops, running coreboot, are now available with the Intel Management Engine completely and verifiably disabled.

The Management Engine (ME), part of Intel AMT, is a separate CPU that can run and control a computer even when powered off. The ME has been the bane of the security market since 2008 on all Intel based CPUs, with publicly released exploits against it, is now disabled by default on all Purism Librem laptops.

Disabling the Management Engine is no easy task, and it has taken security researchers years to find a way to properly and verifiably disable it. Purism, because it runs coreboot and maintains its own BIOS firmware update process has been able to release and ship coreboot that disables the Management Engine from running, directly halting the ME CPU without the ability of recovery.

Great move.

Another year: the iPhone is still the best choice for most people

Over the weekend, people with review units of the Pixel 2 XL began noticing a problem. No, not the already-known issues of muddy color and grainy textures when viewed in low-light, but one that's potentially more worrisome: screen burn-in. First reported on Twitter by Android Central's Alex Dobie, multiple people have noticed that when you look at the screen with a gray background, you can see faint outlines of the phone's navigation buttons on the bottom.

You can see it below, and I can confirm I'm seeing something similar on my own review unit.

The display problems of the Pixel 2 XL - due to its LG-made panel - are baffling. Google claims it's getting serious about hardware, but putting a panel in your flagship phone that isn't only sub-par when it's working, but is also showing burn-in after mere days of use, is wholly and utterly inexcusable. This is not a budget, €150 phone - this is a flagship phone with a flagship price, and consumers deserve better than this clearly garbage display.

Another year, another round of flagships, another year of the iPhone simply being the best all-round option for most, normal people. For most average, normal people, the iPhone will give them an easy-to-use, secure, and updated phone with a decent resale value two to three years down the line. Additionally, Apple Stores or official Apple retailers are widespread, so you often have easy access to in-person customer service.

Samsung/HTC/LG phones don't get updates - or only six months after the fact - but carry the same flagship price, often leaving their users with insecure and out of date software. The Nexus program no longer exists, and Google's Pixel phones are only available in like 2 countries, and on top of that, its flagship model has a display worse than my Palm T|X. The Android market is in a terrible state right now.

Anybody who doesn't care about software and hardware the way most of us do is, years and years in, still best served by an iPhone. Depending on budget, get an iPhone 6S, 7, or 8 (forget the ridiculously overpriced iPhone X); the Android world simply doesn't have a phone that can compete with any of those three - and that's a sad state of affairs. Google has been wholly unable to address the biggest problems Android suffers from - most notably, updates - and we're way past the point where this can be excused without really scraping the bottom of the barrel of excuses.

Suggesting non-nerdy, regular people get an Android phone at this point in time is simply irresponsible.

The Xerox Alto, Smalltalk, and rewriting a running GUI

We succeeded in running the Smalltalk-76 language on our vintage Xerox Alto; this blog post gives a quick overview of the Smalltalk environment. One unusual feature of Smalltalk is you can view and modify the system's code while the system is running. I demonstrate this by modifying the scrollbar code on a running system.

Smalltalk is a highly-influential programming language and environment that introduced the term "object-oriented programming" and was the ancestor of modern object-oriented languages. The Alto's Smalltalk environment is also notable for its creation of the graphical user interface with the desktop metaphor, icons, scrollbars, overlapping windows, popup menus and so forth. When Steve Jobs famously visited Xerox PARC, the Smalltalk GUI inspired him on how the Lisa and Macintosh should work.

Be sure to read the comments after the article itself, since it includes comments and clarifications from none other than Alan Kay himself.

Puerto Rican iPhone users given access to Loon balloons

Apple, AT&T, the FCC and Alphabet's X division have all put into motion efforts to give residents of Puerto Rico more cellular connectivity.

Apple has been working with AT&T to extend and activate cell service for users in Puerto Rico. To improve what is a terrible connectivity situation there, it’s going to enable a provisional band of LTE that has been recently approved, but not activated in the US and Puerto Rico, where it has not been licensed. This will allow iPhones to connect to Alphabet X's Project Loon balloons in the region, which were activated today.

This should allow users to send text messages and access some critical online services.

It's always a welcome change of pace to see companies like this working together to help people in need. Good work, Alphabet/Google, Apple, and AT&T.

Now there's a sentence you won't hear very often.

PC-MOS released under GPL

The old PC-MOS was released under the GNU GPL this Summer. From Wikipedia:

PC-MOS/386 was a multi-user, computer multitasking operating system produced by The Software Link (TSL), announced at COMDEX in November 1986 for February 1987 release. PC-MOS/386, a successor to PC-MOS, can run many MS-DOS software titles on the host machine or a terminal connected to it. Unlike MS-DOS, PC-MOS/386 is optimized for the Intel 80386 processor; however early versions will run on any x86 computer.

The GitHub project includes a 1.44MB disk image for the latest version that will work under VirtualBox, but does not include older versions of the operating system from before it required an 80386+. The system won't work properly if you set a modern date at the boot up prompt.

Windows 10 Fall Creators Update: lots of small changes

Overall, the Fall Creators Update is a nice set of improvements to Windows. Windows 10 continues to get better with each update. Its grab-bag nature continues to underscore just how Windows development has changed. As the Fluent work makes clear, Windows today is in some sense never finished. That's not something to be scared of; any piece of actively maintained, supported, updated software is in a sense "not finished."

With the new approach to developing and delivering Windows, that "unfinished" nature is more overt than it used to be. I'm sure some of the semi-annual Windows updates will feel larger in scope than others, depending on how the development work is going; others will feel a bit smaller. Because so much of the ground work was laid in the Creators Update, albeit hidden from view, this feels like a smaller update.

It's a list of relatively small and disjointed features, but I still really like this update. Especially the Fluent Design changes to applications are very welcome, and make Metro applications feel less... Dead? Less cold? They have more warmth now, which is definitely something missing from pre-Fluent Metro and current iOS UI design (not so much from Material Design, which is rife with colour and depth). The very, very subtle blur effect, the 'highlight' when hovering over buttons and menus, and the odd animation here and there really address the concerns of people who feel Metro takes the "flat" design trend too far to the extreme.

As a sidenote, "flat" really is a terrible term, since none of these UI design styles are really flat. Fluent, Material Design, and whatever iOS has are actually anything but flat, and have far more Z-depth than anything that came before - but I digress.

The emoji picker is really nice, but it baffles me why it's emoji-only; as someone with a deep, deep hatred for special character input on Windows, it baffles me that it doesn't include special characters. The new GPU panel in Task Manager is also very nice, and it feels like Edge is less flakey, too.

All in all, a nice free update.

The new MacBook keyboard is ruining my life

I was in the Grand Central Station Apple Store for a third time in a year, watching a progress bar slowly creep across my computer's black screen as my Genius multi-tasked helping another customer with her iPad. My computer was getting its third diagnostic test in 45 minutes. The problem was not that its logic board was failing, that its battery was dying, or that its camera didn't respond. There were no mysteriously faulty innerworkings. It was the spacebar. It was broken. And not even physically broken - it still moved and acted normally. But every time I pressed it once, it spaced twice.

"Maybe it's a piece of dust," the Genius had offered. The previous times I'd been to the Apple Store for the same computer with the same problem - a misbehaving keyboard - Geniuses had said to me these exact same nonchalant words, and I had been stunned into silence, the first time because it seemed so improbable to blame such a core problem on such a small thing, and the second time because I couldn't believe the first time I was hearing this line that it was not a fluke. But this time, the third time, I was ready. "Hold on," I said. "If a single piece of dust lays the whole computer out, don't you think that's kind of a problem?"

The keyboard on the MacBooks and MacBook Pros is an unmitigated disaster. In pursuit of thinness nobody else is looking for, Apple severely crippled its most important Mac product line - and that's even without taking the Touchbar into account.

DragonFlyBSD 5.0 released

DragonFlyBSD 5.0 is the first release with preliminary boot support for HAMMER2, the project's new filesystem.

Preliminary HAMMER2 support has been released into the wild as-of the 5.0 release. This support is considered EXPERIMENTAL and should generally not yet be used for production machines and important data. The boot loader will support both UFS and HAMMER2 /boot. The installer will still use a UFS /boot even for a HAMMER2 installation because the /boot partition is typically very small and HAMMER2, like HAMMER1, does not instantly free space when files are deleted or replaced.

Microsoft shows off its Fluent Design changes to Windows 10

All of the new design changes to Windows 10 are demonstrated in a new video from Microsoft. It’s a good showcase of how subtle the changes are, but it doesn’t tease much for the future. Microsoft’s Fluent Design System is designed to be the true successor to Microsoft's Metro design, and will appear across apps and services on Windows, iOS, and Android. Microsoft is focusing on light, depth, motion, material, and scale for its Fluent Design, with animations that make the design feel like it's moving during interactions in Windows.

Like Metro applications before them, these Fluent applications look really nice, but it's all for naught. Microsoft showed off its redesigned Outlook application for Windows (and macOS), and guess what? It's a Win32 application.

If not even Microsoft itself is interested in making Metro/Fluent applications, why should anyone else?

Microsoft's approach to Metro/Fluent has been baffling from day one, and it doesn't seem like anything's changing any time soon. They made really great Metro Office applications, but then proceed to hide them from the Windows Store behind the "mobile" tag, and artificially cripple them by not allowing you to open more than one document per Office application.

Even when Microsoft does make great Metro/Fluent applications, they artificially cripple them.

I have no idea what Microsoft is doing, and I don't blame developers for giving them the finger. They are telling an unreliable, unfocused, unclear, and chaotic developer story, and any developer worth her salt wouldn't touch the Windows Store/Metro/Fluent with a ten-foot pole.

Where is Haiku R1?

With all the infrastructure changes and improvements, paired with the bug fixes in our master Haiku branch, we are slowly and steadily moving towards the R1 Beta 1 release which will live in its own R1(!) branch.

R1 Beta 1 installations should slowly roll towards the final R1 release via package updates. R1 Beta 1 is going to be a big step towards our first stable release.

The exact dates are still not solid. I know we have been saying "soon" for quite a while... But soon.

...

ChrysaLisp: an assembler/C-Script/Lisp 64bit OS

Assembler/C-Script/Lisp 64 bit OS. MIMD, multi CPU, multi threaded, multi core, multi user.

Runs on OSX or Linux for x64, PI64 Linux for Aarch64. Will move to bare metal eventually but it's useful for now to run hosted while experimenting. When time allows I will be doing a VM boot image for UniKernel type appliances and a WebAssembly target to play around within the browser.

Allows modelling of various network topologies with point to point links. Each CPU in the network is modelled as a separate host process, point to point links use shared memory to simulate CPU to CPU, point to point, bi directional connections. There is no global bus based networking on purpose.

What nobody told me about the Netherlands

Some years ago, already working in 'active transport', and seeking to deepen my understanding around urban design, I took the opportunity to take a family holiday for a week in the Netherlands. Among many many reactions to the experience, one big one I experienced was simply surprise that nobody had told me about most of the amazing things I'd see.

I've been meaning simply to write a list of these amazing things for years now. Unfortunately I'm not all that sure that there is any way to convey the 'amazingness' to those who haven't visited.

The Netherlands is one of the most - if not the most - densely populated western countries, which forced urban planners to get creative. Growing up and living in The Netherlands it's easy to take for granted just how good we are at traffic and urban design. That is, until you take a trip abroad to pretty much any other country - even our beloved neighbours like Germany or Belgium - and realise just how terrible everyone else is at properly segmenting and protecting cyclists and pedestrians, even in densely populated and tightly packed cities.

Urban design is a fascinating subject, and once you start paying attention to it here in The Netherlands, you'll discover an endless array of affordances to protect cyclists, pedestrians, and cars (yes!), while also creating neighbourhoods that usually have only one entry/exit point for cars so they can't be used for through traffic, all designed with the goal of corralling cars away from where people actually live.

I often wonder - will this make The Netherlands a haven for self-driving cars, or a hell?