In the case of houses, I would think in most cases there's less conflict between prettiness and efficiency, for things like furniture there's much less space for the aesthetics to make a given piece more or less functional or efficient. However the tension isn't entirely gone, Juicero and 'McMansions' spring to mind as possible counterexamples.
The SmallInteger limitation is probably because as an optimisation they stored them as immediate values rather than generic objects, and Squeak shares this limitation (the newer Spur format extends this to one or more additional types depending on image bitness).
Related to references and the above, Eliot Miranda's blog may be informative as it provides both details and sometimes code for many of the changes that have happened in the Squeak (and now OpenSmalltalk) VM, e.g. http://www.mirandabanda.org/cogblog/2013/09/13/lazy-become-a...
There have been very extensive changes since 2002, yep, such as a much improved interpreter, a JIT, a replacement of the original object memory format which incidentally supports faster become and most recently a new bytecode set.
Even broader is the one in the drafted repeal of the Fixed-Term Parliaments Act, the scope of (b) being particularly worrying - what exactly counts a related purported decision?
'A court of law may not question— (a) the exercise or purported exercise of the powers referred to in section 2,(b) any decision or purported decision relating to those powers, or (c) the limits or extent of those powers.'
It would be even better if Kallithea or RhodeCode adopted the UI style shared by GitHub/Gogs/Gitea and friends. Then we could have the best of both worlds - good, well-known UI but with software that isn't as closely coupled to Git as some others are (and is lightweight with requirements)
Not the author, but the kernel is Multiboot compliant. See: https://sortix.org/man/man7/installation.7.html 'If you wish to dual boot, you need an existing operating system with a multiboot compliant bootloader such as GRUB.'
Assuming the tagged reference or capability system was built, wouldn't it need software to take advantage of it? If it's not actively used, no real point having it over more block pointer space - and I doubt significant amounts of software would use such a filesystem-specific feature.
It's not publicly owned but the market is way less dysfunctional than in the US - aside from the few fiber & cable ISPs, a single phone line allows you to choose from a reasonably broad selection of ISPs.
Here's the problem with that idea: How do you convert your abstract high-level description into a set of specific operations? First you need to parse your specification, and parsing natural language is already hard. Secondly, you have to infer everything else that was requested and will be needed but was not originally specified.
Alright, now you have your list of requirements. Firstly, you must break each requirement down into a long series of small steps that perform exactly one operation - such as add 1 and 1 together. You must also find the correct order for all of the steps, as well as the operations to store and manage all required data in memory as meeded.
Finally, the list must either be translated to the native language of your computer's CPU or ran by a program running on the CPU.
As you can see, this is actually a large and difficult task, even if you manage to not encounter any unsolvable problems along the way. I would think the following comes naturally: The difference between your language and the 'dumb-as-rocks' ones is that the latter are implementable and usable.
Elsewhere on the internet (without resorting to seedier places like torrent sites) you can find versions of SunOS 2.x/3.x/4.x as well as Solaris 1.x, 2.x, 7.x and 8.