How do you reconcile avoiding external dependencies and writing own software as much as possible with the usage of ReactJS? (You wrote about that week before this post.) I would argue that React is neither essential library (you can rather easily achieve most things React is used for with vanilla javascript) nor is its basic functionality that hard to implement (e.g. various "Build your own React" articles on the internet).
My context is that I've maintained the same codebase for a decade and it appears the rot mostly occurs in libraries. What's more, when you invest in learning a library's api, it's usually at the expense of learning a core programming idea.
amazing article i loved it... https://www.claadss.com
How do you reconcile avoiding external dependencies and writing own software as much as possible with the usage of ReactJS? (You wrote about that week before this post.) I would argue that React is neither essential library (you can rather easily achieve most things React is used for with vanilla javascript) nor is its basic functionality that hard to implement (e.g. various "Build your own React" articles on the internet).
I arrived at similar conclusions in my video about the six hidden costs of software dependencies (or in more catchy terms: 'npm install servitude')
https://youtu.be/rQegYUsU7ec
My context is that I've maintained the same codebase for a decade and it appears the rot mostly occurs in libraries. What's more, when you invest in learning a library's api, it's usually at the expense of learning a core programming idea.
You might be interested in my recent paper about building up a zero-dependency stack all the way up from machine code: http://akkartik.name/akkartik-convivial-20200607.pdf