I'd argue that while Rust has a high barrier to writing code due to lifetimes and other type constraints, its still quite easy to read.

(Kind of the inverse of perl)

While it's a lot easier to read then Perl, it's still not as easy as something like a Python.

Emulating the lowest common denominator is the function of an LLM. It works better for things like code because boring code is actually the best code.

You should eat your own dog food, but maybe you should not drink your own rat poison.

The original reseaech around thinking fast and slow (aka system 1 system 2 thinking) failed to be replicated when researchers tried.

I love how everything is an expression with a value. And match expressions are quite nice, especially with the option type. I really miss those when working in javascript.

How would you fix the spec? Add a line explicitly stating the /Library/Application Support dir is only for applications with a bundle ID, instead of just implying it?

Does it track my behavior to sell it to advertisers of less whimsical storefronts?

It would allow them to negotiate directly with Mastercard, making the deflection in TFA impossible.

So fuel would basically become a corn based battery. (Ideally something more efficient than corn would be grown though)

The name of this feature is transclusion.

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

It was part of Project Xanadu, and originally considered to be an important feature of hypertext.

Notably, mediawiki uses transclusion extensively. It sometimes feels like the wiki is the truest form of hypertext.

Ward Cunningham (inventor of the Wiki) spent some time trying to invent a transclusion-first wiki, where everyone had their own wiki-space and used transclusion socially https://en.wikipedia.org/wiki/Federated_Wiki

it never quite took off

I think true transclusion would be more than that.

In Xanadu you could transclude just an excerpt from one document into another document.

If you wanted to do this with HTML you need an answer for the CSS. In any particular case you can solve it, making judgements about which attributes should be consistent between the host document, the guest document and the guest-embedded-in-host. The general case, however, is unclear.

For a straightforward <include ...> tag the guest document is engineered to live inside the CSS environment (descendant of the 3rd div child of a p that has class ".rodney") that the host puts it in.

Another straightforward answer is the Shadow DOM which, for the most part, lets the guest style itself without affecting the rest of the document. I think in that case the host can still put some styles in to patch the guest.