>> In the last few years, it seems web performance has fallen by the wayside. Indeed, with many sites now using frameworks like React and Vue, SPAs becoming commonplace and requests going into the hundreds, the average webpage is now bigger than ever, with 2–3MB pages being more common than ever.
A really good reminder! I've been trying to go back to JavaScript basics recently after having learned Vue a short while ago. Not just because of the performance gains but also because I feel like it's valuable to be able to talk in-depth about vanilla JavaScript concepts in an interview if you're there for a front-end/full-stack role.There have been times when I've wanted to use an animation or something from a library, and instead of pulling in the whole library I'll read the code to see if I can isolate just the parts that I need and only bring that in. That's saved me a lot of clutter in the past. That being said, I usually will throw something like Bootstrap in for CSS styling even on a small project. There are more lightweight frameworks out there for CSS styling but I would need to learn them whereas I'm already familiar with Bootstrap. I could also try to style it myself but having the grid system that the framework provides keeps things clean and that actually does benefit the user (fewer bugs).
As a CTO and engineering lead, I prioritize my ship velocity because that determines my rate of product learning. A properly skilled React engineer is much more productive than one not using a good framework, assuming the same product feature complexity and footprint. I can iterate much more quickly with React than without.I serve my users and customers more effectively by shipping faster. I have to assume that the size of my web asset payload or the relative responsiveness of my UI is less important than that. The author of this piece appears not to have worked in the industry.
Hey Jenny! Can you explain what you mean by "product learning"?
Learning by running empirically valid experiments with modifications to a live product. It has to be cheap to modify and deliver that product for this approach to product management to make sense. Web apps are great for this, and this is why they are heavily favored even for enterprise software where other options make sense for other requirements.
This article is written by me on a Friday when I realize that I'm going to have to write a custom view and with animations to make the UI look right and I don't want to so I offer the alternative "or it could just be ugly." Ten out of ten the designer tells me no. Ten out of ten it's me the developer putting myself before the user.