> the Web is now 30 years old, past its peak, so if browsers still need to update bi-weekly for new features and experiments, this in combination with lack of browser diversity proves without any shade of doubt there's something very wrong with the incentives for browser development, the Google/Mozilla browser cartel, and the evolution of "web standards".
Or maybe new features are still coming out in the W3C specs and need to be implemented. Did you know CSS now has a parent selector, or that JS will be getting functional piping soon?
On functional piping, this has been in the pipeline with a few competing proposals for a while (I prefer the F#-like version myself). Will be surprised if/when it actually makes it in.
Or maybe new features are still coming out in the W3C specs and need to be implemented. Did you know CSS now has a parent selector, or that JS will be getting functional piping soon?