coreload

All estimates should be accompanied by a "cone of uncertainty". Teams should evolve their ability to describe a cone of uncertainty as well as their ability to estimate. Estimating "accurately" is only possible when understanding the accuracy is elevated to the same importance as the estimate itself.

https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

https://hubbardresearch.com/product-category/publications/ho...

Retrofitting to some but not all languages is not nearly the same as an intentionally language agnostic protocol. To the extent that calling this "web" is at best misleading.

Language specific RPC. At least Cap'n Proto is language agnostic. ConnectRPC is language agnostic and web compatible and a gRPC extended subset. I would have difficulty adopting a language specific RPC implementation.

These are opinion editors. They're expected to have opinions.

This project was attempting to spin up relatively exotic hardware and software concurrently. The Lisp folks had less exotic software already more or less established but attempted to spin up corresponding hardware. The 5th generation project failed faster due to its greater ambition. Both failed ultimately due to commodity hardware greatly outpacing the ability of exotic hardware to keep up.

Yes, and sometimes the context is not just social but legal or contractual, e.g. rounding currency.

Google is no longer a startup. Google is competing for a significant number of talented people. The startup mentality will not easily work for decades of competition with the other wealthiest tech companies.

That would have been difficult since Plan 9 predates each of those other systems. Also Plan 9 took place in Bell Labs as a research project, was based on their own UI research, and was not intended to be a commercially familiar UI. There are interesting ideas in the write ups about the UI that could be applied in nearly any UI today.

Used these for several years. The Apollo Domain OS is still a thing of wonder to learn from.

The Concurrent Clean programming language is based on uniqueness typing, related to linear typing. This may have some inspiration for other concurrent languages.

https://wiki.clean.cs.ru.nl/Clean

I have IBM 5100 nostalgia. I wrote a lot of software for that 40 years ago. Speaking of Lisp Machines, the 5100 was basically an APL machine: BASIC and APL in microcode.

Well-defined object systems map objects to objects. Why would it be surprising that category theory can describe these things?

The questions for software development are about creativity and economy. The jury us still out on these to the best of my knowledge.

Note that this was the advice of developers of distributed OO systems in the early 1980s.

See in the HOPL... "The Development of the Emerald Programming Language"

That poor little c2.com server. The gerbils will be turning their wheels all day.

See also http://jeffsutherland.org/oopsla98/nakamura.html