> what's a cubit?

What's an ark?

Yup. He is, by all accounts, a great supply-chain guy. eg. As far as I can tell, there were no significant breaks in Apple's supplies during COVID.

But he clearly falls afoul of Steve Jobs'warning about leaders with no taste.

This is even an understatement.

It’s not a stretch to say that Tim Cook created the whole Shenzhen microelectronics industry. The thousands of specialist component vendors and large integrators that assemble products trace to his instigation with Compaq and then Apple. The iPod, Macs, iPhone, copied the Swiss Watch model of vast redundant networks of component competetors working as an ecosystem to drive down costs.

This created the skill and machinery base that made it possible for other western design companies (such as Android vendors that were not Samsung or Japanese) to make clones of the iPhone quickly and easily. (Let’s be real, every smartphone is an iPhone 1 clone)

China owes a lot to this work.

Tim Cook needs to drop some acid. He has no creativity what so ever.

You'd think a supply chain guy would be able to get ahold of some psychedelics too...

Have you looked at the Apple Newton memory architecture?

http://waltersmith.us/newton/HICSS-92.pdf

Thanks, will do

In Eclipse Phase:

> The acronym TITAN stands for Total Information Tactical Awareness Network. These were a group of highly advanced, self-improving seed Artificial Intelligences (AIs) that are responsible for the catastrophic event known as The Fall.

Someone else has already made the mandatory Torment Nexus quote.

Emacs is a (virtual) Lisp Machine

The latter 2 usages are pretty much the same. They just have different virtual instruction sets.

> The latter 2 usages are pretty much the same.

Only if you ignore most of reality, sure.

> Only if you ignore most of reality, sure.

No, not really.

Hypervisor VM: emulates a virtual computer with virtual, emulated hardware, but a simulated version of the same CPU as the host, allowing 1 OS to run under another.

E.g. Xen, VMware, KVM, bhyve

Bytecode VM: emulates a partial virtual environment, with an emulated CPU and some form of conversion or translation from virtual environment to the underlying real API and real OS, allowing programs to execute on radically different OSes on different CPUs.

E.g. JVM, MoarVM, Parrot VM, Dis in Inferno

Emulator VM: emulates a virtual computer with virtual, emulated hardware, including a virtual CPU.

E.g. MESS, RetroVM, ZesaruX

Container: emulates an OS from userland down, but shares the same OS kernel across instances.

E.g. Docker, LXC, LXD, Incus, FreeBSD jails, Solaris Zones

So you can't tell the difference between a hypervisor and a bytecode interpreter.

OK.

Wow, just what I wanted for Christmas. Back in the day I found VisiOn's approach fascinating since almost everything at the time was either more tightly integrated or completely unintegrated.

Maybe someone could do the the old Reason software bus based system next? As detailed in Jan 1984 Byte magazine. Lord only knows if there are surviving copies anywhere in the world.

One of the nicer features of D is that arrays are value types with no degrade to pointer.

Smalltalk romantics

do you have showdead turned on?