Because that CSS can be evaluated with lower latency than the equivalent js

unsafe rust is still typed orders of magnitude better than C

Yep cost is the reason, allegedly the ts team found go a better language for a port and both using a less ergonomic language and switching target every six months have associated costs

And that's a fine argument to make! But this stupid garden analogy is nonsense.

no, it is the same idea, even if the excavator was magically free there are associated costs like keeping an industrial machine in your garden, danger or heavy machinery and possibly it is going to destroy you garden.

the analogy is not between each specific consequence/cost, it is relative to "single axis optimization" not being a solid strategy

Here the list is the "flattened” ast of (Node, slice of input corresponding to the node)

The list represents the possible parses and the remaining input for each. In most cases you might prefer an unambiguous grammar, so a successful parse is a singleton list of a pair of the full parsed result with an empty input sequence.

But parser combinators build your final parser out of little bits, and sometimes those little bits might be something potentially ambiguous, like "any number of leading zeros followed by a number" which needs to parse "0" as no leading zeros and the number 0, but "00" as one leading zero and the number 0.

Non-deterministic parsers can easily blow out with backtracking much like careless recursive descent parsers, though.

this only warn that there is some implementation-defined stuff coming next, not that all these operator are free of undefined behaviour

Not everyone needs to care about everything and there is reason to say that a result like this one from openai is quite sterile and possibly damaging to the socio-cultural dynamic of the field.

I never did a blind test but I feel i get much improved writing for work stuff with instructions to use ASDSTE-100

I feel like solid-js is in a good place to be a platform

loadshedding is based on each load having an associated priority