4 ms·
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
by lmm 6y ago
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.
- fiddlerwoaroof 6y agoYeah, 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://gbracha.blogspot.com/2009/06/ban-on-imports.html?m=1 https://wiki.c2.com/?BanOnImports https://wiki.c2.com/?BanOnImports
- asddubs 6y agono 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.
- BiteCode_dev 6y agoIt's also because Python has such an awesome stdlib that it's so popular. So there is that.