Yea, the idea that "modern web programming" is beautiful at all franky makes me cringe.
Web programming and the web has separated developers too far from the hardware that actually runs the stuff and, as a result, we have built confusing towers of babel.js.
I mean, Javascript was originally made for developer ease over user reliability - and look at it now - it shows with the cacophony of NPM dependencies prone to "leftpad" style failures and the new frameworks every 6 months. All of this, of course, goes against one of the author's key points: "User experience, even over developer experience."
Unfortunately, I don't think the problem is solved by process but instead on re-education to compiled, reliable systems, made with a typing system designed to catch errors. Introducing more process and efficiency will never make a bicycle into a proper car.
> I don't think the problem is solved by process but instead on re-education to compiled, reliable systems, made with a typing system designed to catch errors.
We already have that in the form of TypeScript, but both left-pad and core-js were, for lack of better term, non-technical failures.
Only the most recent such case - is-promise - was purely a technical failure.
There's not much than can be done when the sole core maintainer of a popular library lands in a penal colony.
While an improvement Typescript is a far cry from the likes of Ada and doesn't really compare.
> There's not much than can be done when the sole core maintainer of a popular library lands in a penal colony.
Perhaps the solution is to not use Javascript, since it always forces you into an "ecosystem" of "frameworks" at every turn - and they are not cheap! Just another thing to throw on the stack. mb's be damned.
> While an improvement Typescript is a far cry from the likes of Ada and doesn't really compare.
Given their respective popularities perhaps the point of diminishing returns was crossed somewhere?
> Perhaps the solution is to not use Javascript, since it always forces you into an "ecosystem" of "frameworks" at every turn - and they are not cheap! Just another thing to throw on the stack. mb's be damned.
This is becoming outdated information thanks to the likes of Svelte:
Web programming and the web has separated developers too far from the hardware that actually runs the stuff and, as a result, we have built confusing towers of babel.js.
I mean, Javascript was originally made for developer ease over user reliability - and look at it now - it shows with the cacophony of NPM dependencies prone to "leftpad" style failures and the new frameworks every 6 months. All of this, of course, goes against one of the author's key points: "User experience, even over developer experience."
Unfortunately, I don't think the problem is solved by process but instead on re-education to compiled, reliable systems, made with a typing system designed to catch errors. Introducing more process and efficiency will never make a bicycle into a proper car.