neperj on Nostr: Thanks, after much analysis paralysis to pick a framework, I took an advice from a ...
Thanks, after much analysis paralysis to pick a framework, I took an advice from a golang dev (not a frontend dev) to just keep it with vanilla, and it just worked for me, but yes I only did simple things and haven't worked on real projects, still can't see what vanilla can't do.
been building a NIP-99 client, just the fact nobody is using vanilla makes me feel awkward and missing something very obvious that I will find out later.
I thought it may be good to share (do you agree?):
"I'm not really a frontend dev so take my opinions as Grandpa Simpson shouting at the clouds. Honestly, for most cases, plain HTML, CSS and JS is just fine for what you need. A lot of the tooling to "make things easier" (on the unfounded premise that vanilla is too hard) ends up making things harder. So instead of having a single HTML file with CSS and JS in it, you now have to contend with some framework concepts and conventions. Guess what? You're now divorced from the technology that underpins it and are now dealing with an abstraction. Something goes wrong, a version of one of the thousands of dependencies has a bug in it. Now you're hunting around forums trying to solve a problem for a tool that was supposed to make your life easier. Even worse, none of the knowledge you have is transferable to other frameworks so now you're in this technology echo chamber and instead of having frontend developers, you have "react" developers, who manage concepts like "react component lifecycles".
Plain HTML, CSS and JS are so well documented, you're only upskilling, not "trying to fix build issues".
No build times, instant reload, well documented, no weird concepts. What's not to love about Vanilla?"
been building a NIP-99 client, just the fact nobody is using vanilla makes me feel awkward and missing something very obvious that I will find out later.
I thought it may be good to share (do you agree?):
"I'm not really a frontend dev so take my opinions as Grandpa Simpson shouting at the clouds. Honestly, for most cases, plain HTML, CSS and JS is just fine for what you need. A lot of the tooling to "make things easier" (on the unfounded premise that vanilla is too hard) ends up making things harder. So instead of having a single HTML file with CSS and JS in it, you now have to contend with some framework concepts and conventions. Guess what? You're now divorced from the technology that underpins it and are now dealing with an abstraction. Something goes wrong, a version of one of the thousands of dependencies has a bug in it. Now you're hunting around forums trying to solve a problem for a tool that was supposed to make your life easier. Even worse, none of the knowledge you have is transferable to other frameworks so now you're in this technology echo chamber and instead of having frontend developers, you have "react" developers, who manage concepts like "react component lifecycles".
Plain HTML, CSS and JS are so well documented, you're only upskilling, not "trying to fix build issues".
No build times, instant reload, well documented, no weird concepts. What's not to love about Vanilla?"