12 ms·
The code here is clean, well written and honestly not that much more verbose than many of the framework ones. I also found it simple to understand. Would you n
by listless 4y ago
The code here is clean, well written and honestly not that much more verbose than many of the framework ones. I also found it simple to understand.
Would you need a “framework” when an app gets beyond TODO? I think you would need to start refactoring your code to be more framwork-like. But this is something we don’t do, and I would say would even be considered “anti-pattern”.
- mch82 4y agoMy bet is that as soon as someone popularizes a way to manage state across a set of web components the pendulum will swing back to the “Vanilla JS” approach. It’s so nice to work on web apps without having to install NodeJS, builders, cli tools, and so on. And it encourages software engineers to learn the web platform APIs instead of learning frameworks. HTML and CSS are actually quite nice to work with, given modern browser developer tools. Much simpler to work with when they are literal files. It wouldn’t surprise me if people continue to compile other languages to JavaScript or WASM though. It seems reasonable a Java developer might like to work in Java or a Ruby developer in Ruby instead of writing JavaScript. But I don’t understand how people feel confident writing web applications if they don’t take the time to understand CSS, HTML, or the browser APIs.