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.
It's actually not in the app store, and it may only be available on Pixel phones. You get the app not by downloading it from anywhere, you just enable "developer mode" in the system settings, and the app magically appears in your app menu (the full menu, not on any home screen by default). There is a subreddit dedicated to this app ( https://www.reddit.com/r/androidterminal/ ).
I've never used a Samsung phone, but I think their DeX environment might allow you to do the same things that the "terminal" app supplies.
If you can't get either of the above to work, give Termux a try. It's not full gnu/Linux, but it's pretty close.
I use Android phones, and there are at least two ways to get iPython going on an Android phone.
The first is Termux, which provides a gnu userspace atop the Android kernel. This app is pretty old, and well-tested. There is an active and helpful Termux community. But it has some downsides: 1) The version of Termux in the Google Play Store is not the preferred and maintained version, although the Play Store version does work. The preferred version is in F-Droid, but the future of F-Droid itself is uncertain in the light of recent Google policy decisions. 2) Termux does not have access to directories such as /proc, /sys etc, which prevents some gnu/Linux utilities from working and 3) The Termux filesystem layout is very non-standard, so unless a program has been packaged explicitly for Termux, installation will probably be messy. I was able to get most, but not all of the Python packages I use frequently, to run within Termux. I could not get astropy to work, for example. Termux has nice usability features like pinch-to-zoom to change the font size. Termux requests a wakelock, and if you grant the wakelock then the OS will not throttle the app when your phone is locked.
The other option is the relatively recently added "terminal" app. terminal runs a plain-vanilla Debian Linux OS within a VM. Its file system is laid out exactly as you would expect, so if you want to get iPython and lots of libraries, you can just run the Anaconda Python installation script, and it will run unmodified with no errors. Nice! You can also install other nice desktop-style apps like VeraCrypt. There are a few downsides: 1) The OS will throttle the app, and occasionally kill the app, when the app is not actively being used interactively. 2) I have found no way to change the tiny font. 3) It's a Google app, so it might disappear for no good reason, as so many Google products do.
Both of these options work especially nicely on a foldable phone, because then the tiny phone keyboard is much less of an issue. A foldable phone plus the terminal app really is a pocket Linux computer.
There was a time when I would have salivated over this. But now I can run iPython on my phone, and have numpy, sympi, scipy, astropy and countless other packages. Physical keyboards are great for calculators - much better than virtual keyboards on phones. But the keyboard advantage seems to me most valuable for quick calculations, not elaborate things like this calculator offers. If I'm going to do matrix calculations, I want to be able to put the data into a file with a real, and familiar, editor. I want to be able to grab tables of data from the web. If I make a plot, I want to be able to save it to a PNG file. I want a high resolution color display. A phone running iPython/Python seems much better to me, especially since almost everyone who would want to do what this calculator does already has a smartphone. Also, I can ssh into my phone and interact with it using my desktop computer's keyboard and monitor, eliminating the phone keyboard limitations when a full sized computer is nearby.