56
A Rant about Front-end Development
(blog.frankmtaylor.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jun 2024
56 points (96.7% liked)
Programming
17314 readers
83 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Fucking LoL!
Anyone here have thoughts about doing basic interactive stuff with at most vanilla JS?
I think basic or even complex stuff is fine in vanilla js.
The problems show up as you scale the team and code base. You can do a large project in vanilla js but you're going to have to solve a lot of the same problems frameworks/libraries have already solved. Maybe it's worth it, maybe it's not.
On the other hand:
Most Frontends are not super interactive google tables like applications and never will be and frameworks won't magically make your code maintainable or enable you to work with 50 other guys on that page that interacts with a simple CRUD-API, yet people choose a complex framework meant for huge projects and pile even more dependencies on to of it for that kind of stuff. it's like using a fleet of 18 wheel trucks for grocery shopping, when a basket and a bicycle are really all you'll need for that.
i'd guess most websites would be fine and feel "modern" with html, css and a small library for ajax stuff, because doing that by hand is repetetive and error prone.
Vanilla JS is perfectly fine to do basic interactive stuff. Data Binding is a bit trickier but can be achieved neatly with Web Components. I like it.
Yea, I'm unclear on how you can take web components and still have widespread browser support (not knowing enough about their ins and outs).
Plain template elements are widely supported and have been for ~10 years (which ideologically matters to me along the same lines as the top post's article) ... perhaps a little bit of hacking together can get you close with just that?
Every browser released since 2020 supports this (custom elements that is), so I don't see an issue with browser support.
You mean the Html template Element? I've never really got that to work, but I also never seriously tried.
It's a little paranoid of me, but I like the idea that a basic web app I make can be thrown onto any old out of date machine, where ~2015 or younger seems about right for me ATM.
Yea. From memory, it's just an unrendered chunk of HTML that you can select and clone with a bit of JS. I always figured there'd be a pattern that isn't too much of a cludge and gets you some useful amount of the way to components for basic "vanilla-js" pages, just never gave it a shot either.