News for hackers. Stuff that matters.
Re:HTML Tips (2020) by lmm on Wednesday May 05, 2021 @11:10PM (#27058753)
In Python there's a saying: the standard library is where modules go to die. That effect applies even more so for browser builtins.

IMO we would be better off moving most of these things out of the browsers and into some kind of web component standard.

Re:HTML Tips (2020) by fiddlerwoaroof on Wednesday May 05, 2021 @11:49PM (#27058968)
Yeah, I’ve long thought that the model of a relatively sparse standard library in a sufficiently expressive language is the ideal. What’s really needed is a newspeak-style parameterized “push” module system (or ML functors) to replace “pull”-style imports.

This way, modules can declare that they need certain functionality and then the end user provides it: instead of npm-style infinitely-deep dependency trees.

https://gbracha.blogspot.com/2009/06/ban-on-imports.html?m=1

https://wiki.c2.com/?BanOnImports

Re:HTML Tips (2020) by asddubs on Thursday May 06, 2021 @12:28AM (#27059178)
no way, browsers have a stacked deck especially in regards to accessibility, but also things like platform appropriateness and handling corner cases that only affect specific scenarios. web components tend to be the 80% that whoever made them cared about, which varies from use case to use case.
Re:HTML Tips (2020) by BiteCode_dev on Thursday May 06, 2021 @05:17AM (#27060815)
It's also because Python has such an awesome stdlib that it's so popular. So there is that.