Alto System Project: Dan Ingalls demonstrates Smalltalk

It is a bit hard to explain in an HN comment something that requires live experience, You can start by having a look at, link "Eric Bier Demonstrates Cedar" link "Alto System Project: Dan Ingalls demonstrates Smalltalk" this video "SYMBOLICS CONCORDIA ONLINE DOCUMENTATION HYPER TEXT MARKUP 1985" link You can see how NeXT builds on many of these concepts on the famous "NeXT vs Sun" marketing piece, link Sun also had some ideas along these lines with NeWS, "NeWS: A Networked and Extensible Window System," link Naturally OS/2, BeOS, Windows, macOS, iOS, and even Android share some of the ideas. Now, before I proceed note that actually modern Linux distributions have all the tooling to make these concepts happen, but it fails short to have everyone agree on a proper stack. So basically, the main idea is to have a proper full stack in place for developing a Workstation computer as one single experience, from bottom all the way to the top. On Xerox's case, they used bytecode with in-CPU execution via programmable microcode loaded on boot, and later on just a thin native glue on top of host OS. The environments had frameworks / modules for the whole OS stack, supported distributed computing, embedded of data structures across applications (OLE can trace its roots back to these ideas), REPLs that not only could interact with the whole OS (commands, modules, running applications), it was also possible to break into the debugger, change the code and redo the failed instructions.

Bravo was modal, Gypsy was non-modal, Smalltalk-74 onwards had multi-windows (including pop-up menus) and a metaphorical desktop. I assume you know these interesting presentations: link , this video EDIT: see also e.g. link

The ideas he's promoting aren't new, and in fact predate even the NES. They date back to Smalltalk, which was created at Xerox PARC in the 1970s: this video

You won't get any reliable numbers during wartime. I heard Ukrainian government recently mention they ordered a million. Hundreds of small companies (around 10 employees each) in Ukraine are making and assembling drone's right now (according to journalists who filmed them in Ukraine last month). I counted at least two dozen companies in the Netherlands, probably a few hundred all over Europe. Besides the frame that holds the 4 or six rotors together all other parts are off the shelf, mostly ordered from Shenzen. You can CNC mill a carbon fiber or aluminum frame from a single plate on an x-y flatbed cnc. I researched all this last night because I need $20K-$200k investment right now to start my own startup making unjammable autonomous kamikaze drones with 20K payload on top of 20km optical fiber spools unreeling. I think it is possible to make them lighter without fibers if you put a few thousand microprocessors in with a wafer scale integration for $500. Of course you could just make cheap drones that kill every warm body in sight[4] indiscriminately. To disable a tank you need these fiber tethered drones with bigger payloads[3][5][6]. You cab see two fiber strands still in the air in a few frames of the video. What you need is a Paul MacCready style development cycle for drones in the field. You need to be able to make 10 crashes per hour, fix the drone by replacing with off-the shelf components and try again. The programming should be live-coding like Squeak Smalltalk, no r

I'm not sure of the timing (and whether you're sarcastic) but yeah, I found it funny compared to PARC showing Steve Jobs how the Smalltalk environment allowing modifying GUI behavior at run-time let them iterate quickly, sometimes in front of users ( this video ). I guess link is the closest you get with a compiled language :-) P.S. link has good historical context on that visit(s)