I loved Nokia's Linux phones, and bought several of them. I drove to New York (from Boston) twice to get an N900 as early as possible. But I wonder what they would have had to do to make that line of phones a mass-market success. Users of the N900 had root privilege. Can you imagine a support nightmare that would have been for T-Mobile et al.? To sell Linux phones to the general public, I think they would have had to lock down the OS to the point that it resembled what Android is today.
Don't forget the N950! It was an aluminum body successor to the N900, with a glorious slide-out keyboard. Built like a tank. They were never released for sale to the public, perhaps because Nokia's leadership had already decided to kill its line of Linux phones. But I've got one.
I've read this paper several times, over the years, and I've never understood why its considered such a landmark. I think it could be losslessly compressed to one paragraph of modest length.
I had an old astronomy app I wrote for pre-iPhone app store era Nokia phones (N900 etc.). I decided to get Claude code recreate it as an Android app. The old app produced several display pages for things like the positions of the planets. I was having Claude code recreate the app display page by display page, describing the display that should be produced, with no reference at all to the original app's code (or even its existence). After having it reproduce several pages, it added another one unprompted. The page it added was in the original app, but I had not gotten around to adding it to the Android app. The Nokia app's code is still on github, and somehow Claude must have made a connection between what I was asking it to code (without ever mentioning the Nokia app) and my github repository's Nokia code. It correctly implemented the page without me even mentioning the missing page. My jaw hit the floor.
Testing wasn't really the issue with the loss of the two shuttles. In both cases, it was mostly a management issue. For Challenger NASA had seen o-ring erosion in earlier launches, and decided it was not a big risk to the crew. Then they launched Challenger against the recommendations of the engineers in charge of o-ring seals. For Columbia, they has seen foam strikes in earlier launches, but since they had not caused catastrophe in the past, they decided that foam strikes were acceptable. Even when it was clear that a large foam strike had occurred on the launch of Columbia, management wasn't concerned enough to try to get ground-based images of the shuttle to check for damage. Could Columbia's crew have been saved had they known the extent of the damage? No one can say of course, but not even trying to do everything possible was inexcusable.
This probably signals the beginning of the end for OpenAI. Eventually all of the AI chatbots will have Ads at least on the free and low-cost tiers. But there's a strong incentive not to begin enshitification until the number of competitors has dwindled, and an oligarchy has been established. Google, Meta et al. can afford to lose money on AI for a long time, because they have real revenue from other business products; they can stay Ad free until the small-fry go bust.
Because, wonderful as Termux is, it has a very nonstandard filesystem layout, so installation scripts for something like Anaconda will not run without extensive modifications. And Termux has no access to /proc, /dev etc., so lots of utilities fail. Since Terminal provides a full Linux VM, all programs that will run on Linux just work as expected.
Also, if your Android phone is a Pixel, you can run the recently added Terminal app, which runs a plain vanilla Debian distribution within a VM. So you then have a pocketable Linux machine to develop code on. Not only does Python run on it, you can install the entire Anaconda Python suite.
Yes, but all problems with tainted food are not as visually obvious as mold. After some bad surprises, I've decided to never eat anything I ordered from Amazon.
The current situation on Google's Android Pixel phones is odd. The old non-LLM Google Assistant works well in a limited domain: Things like setting alarms, phoning by name, etc. It's similar in scope to Siri, but with better voice recognition, and better context awareness. However, Google is desperate to kill Google Assistant and force all Pixel users to use Gemini instead. Gemini 3 is a very good LLM, and far, far, far more versatile than Google Assistant. But Gemini won't do the simple things as reliably as the old Assistant. Setting an alarm works maybe 90% of the time with Gemini. If you asked the old Assistant "What time is it?" it would respond "It's 4:40 PM". If you ask Gemini "What time is it?" it will sometimes respond "It's 4:40 PM CDT in {your city}", but sometimes it will say "It's four four zero Pee Em in {your city}" and sometimes it will do a web search. Results are spotty in other areas like voice dialing. I've retained the old Assistant, because I want to do the basic things far more often than I want to verbally vibe code. But rumor has it Google is going to disable the old Assistant in March, forcing all users onto Gemini for voice commands. Unless Gemini gets much better at handling simple tasks by then, Pixel users will end up with a voice assistant much more frustrating than Siri.
I'm sure grateful that you did that. I've been surprised by how little online discussion of this app I've seen. It's just extremely cool to be walking around with a real gnu/linux computer in my pocket, which cost nothing to add to the phone, and has no ads or in app purchases.
There is a third option (in addition to the native app and Termux) to get emacs running. The recently added (to at least Pixel phones) "Terminal" app runs a standard Debian distribution inside a VM. emacs can be installed there in exactly the same way it would be on any other Debian machine.