Don´t worry too much guys, we have "The Renaissance", one man framework, SSI, things are coming back.
We can be Webmasters again!
I Am Happy Not to Be a Web Developer Anymore
71–73 of 73 posts
Re: I Am Happy Not to Be a Web Developer Anymore
#72As an old web developer myself, that surfed pretty much all the waves (No JS, just a Perl or PHP monolith, then JS with XMLHTTPRequest, jQuery, Backbone, Ember, WebPack, Angular 1 and finally React) this argument doesn't make sense. No, there isn't a new JS framework every minute. No, you don't need to learn a new thing everyday. There's really only 4 framerworks (React, Vue, Angular & Svelte, in this order), they pr…
I could almost agree, but for at least one aspect: 90% or more of today's SPA web apps are just glorified information pages, that do not need any React, Vue, Angular or Svelte. That is where the hype train shows. They could just as well be way simpler in design, and avoid having to reimplement (through a dependency or not) the back button. Many cases for actually multi page apps, that are needlessly implemented as SPA with additional router BS and tons of dependencies and a heavy framework, rather than simply going for server side rendered template and being done with it. This comes mostly pushed by frontend developers, who want their shiny framework of choice to be relevant everywhere. A job guarantee.
Re: I Am Happy Not to Be a Web Developer Anymore
#73I get the point the writer is making: web development is a mess. However, I also think that stepping off that treadmill can make one's impression of the field a bit skewed, because there is no longer an incentive of the writer to keep up with the nuances of the changes. Web frameworks do come and go, but they're also not that different from each other. New ones show up, but that doesn't mean that everyone flocks to t…
I feel like I stepped off frontend the treadmill and haven’t been able to catch up with frontend. React, Angular, Vue, Next, Nuxt, Svelte, Typsecript, Tailwind, Bundlers. It feels like a mountain to climb to get my head around that lot!
Most of those are just rehashing of already discovered ideas. It is not like they have much of a secret sauce. Just put some concepts together. If you are a good developer, you can understand what they do in no time. But that makes it even more annoying to see the hype around something that is nothing special. Add to that a mountain of silly configurations and limitations due to design decisions, and you get a "modern" web stack. Take for example "tree shaking". I remember how there was a hype around it. Every second day I would see some post about tree shaking or read some blog or whatever, where people point out tree shaking. Tree shaking! Tree shaking here! tree shaking there! Most of them never stopped and thought about how they shouldn't need to be shaking, but instead should avoid putting that much shakable shit into their trees in the first place.
It almost seems like people are getting off on the fact, that they manage configuration complexity in web projects, as if that makes them somehow qualified. Instead they should be saying:
Wait a minute, why am I configuring all this shit? Why is my web app so big, that using a minifier makes any significant difference? Does my web app really do that much? Couldn't I get by with just rendering templates and add a tiny amount of JS?
But people do not ask and continue riding the hype train and it even makes them more in demand, because way too many people think they need this.