Great question! I find that I only reach for frameworks for larger projects that really benefit from the reusability and encapsulation that they provide.
For a small portfolio I made for a client, though, I used plain JavaScript — even if it meant I had rebuild some routing functionality myself.
At the end of the day, I think there's nothing wrong with using frameworks; using vanilla JS gives you way more control, but you'll have to do more work.
In any case, thanks for sharing! I think it's super useful for newer developers to see that there are lots of people working just with vanilla JS, especially when they can get overwhelmed with all the different frameworks currently available.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great question! I find that I only reach for frameworks for larger projects that really benefit from the reusability and encapsulation that they provide.
For example, for an enterprise application I'm working on, I'm using React because there are a lot of moving parts and reused components.
For a small portfolio I made for a client, though, I used plain JavaScript — even if it meant I had rebuild some routing functionality myself.
At the end of the day, I think there's nothing wrong with using frameworks; using vanilla JS gives you way more control, but you'll have to do more work.
In any case, thanks for sharing! I think it's super useful for newer developers to see that there are lots of people working just with vanilla JS, especially when they can get overwhelmed with all the different frameworks currently available.