There ought to be some kind of 2016 css subset that everyone sticks to and then we can reconsider maybe updating it to include any newer stuff that’s absolutely essential once every ten years.
Expecting the runtime/browser to ship a native implementation of virtually everything you might want to do in a turing-complete language, is also really not sustainable, though.
There ought to be some kind of 2016 css subset that everyone sticks to and then we can reconsider maybe updating it to include any newer stuff that’s absolutely essential once every ten years.
Something like C/C++ does? JS16, JS20, JS24?
that mentality is one reason websites spam JavaScript today, because native features of the markup language were being added too slow
Expecting the runtime/browser to ship a native implementation of virtually everything you might want to do in a turing-complete language, is also really not sustainable, though.