4 ms·
Given how fat a modern website is, I am not sure that a kitchen sink library would change much. It could actually improve things because there would be fewer re
by 0cf8612b2e1e 1y ago
Given how fat a modern website is, I am not sure that a kitchen sink library would change much. It could actually improve things because there would be fewer redundant libraries for basic functionality.
Say there is neoleftpad and megaleftpad - both could see widespread adoption, so you are transitively dependent on both.
- palmfacehn 1y agoThere's also the option of including that standard lib with the runtime.
- crabmusket 1y agoThat is exactly what happens today. JS has a standard library. It's just not evenly distributed.
- int_19h 1y agoJS standard library is missing very basic things like maps with value semantics for keys that aren't primitives.
- 9dev 1y agoAnd never ever be able to correct your past mistakes, because some sites might still be using them? The web platform is no .NET runtime you can just update.
- int_19h 1y agoWeb browsers update far more often than .NET runtime, if anything. And .NET still supports a lot of deprecated stuff going all the way back to 1.0; so does Java (old-style collections, for example). Also, JavaScript is a shining example of "never ever be able to correct your past mistakes" already, so it's not like this is something new for the web.