3 ms·
It takes work to keep up with the latest-and-greatest in modern web frameworks. 100% agree. But if you're already doing that, because you work in the field, or
by willsmith72 3y ago
It takes work to keep up with the latest-and-greatest in modern web frameworks. 100% agree.
But if you're already doing that, because you work in the field, or are passionate about it, then that checkbox is ticked.
I wouldn't do all that JUST to build a static portfolio, but if you already learnt and kept up with all of that stuff, then I still don't see why not use it.
- sfn42 3y agoBecause in a professional setting the guy who takes over after you also has to know or learn whatever tech you chose. I worked on a team maintaining solutions in React, Vue, angular, Svelte, JQuery and more. It sucked. Basically every task I ever did there was my first time doing that thing with that framework.
- willsmith72 3y agoI totally agree, simpler is better. Except for extenuating circumstances, teams working anywhere remotely close to each other should aim to stick to the same technologies and practices. If that's vanilla js, sure, go for it. I'm not arguing everyone needs to move to react. I'm saying the opposite. Stick to the tools you know. I once worked in a strict java-angular.js shop, and it was awesome. Everyone was familiar with the tech and the company saved energy otherwise wasted on tool-related decisions. My point is this > it is more of a flex in this SPA era to show you know how to make a website the old-fashioned way. is not valuable to me at all. If I were giving advice to a new programmer, I'd tell them learn the basics first, like your html, js, css, and then familiarise yourself with one of the frameworks. Then if you want to build your portfolio, build it in whatever you like, but for people at that level, it can be a great chance to practice and show off their skills to employers. If you're shipping 2MB, who cares.