Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Why Everything Must Change Every Five Years

DZone's Guide to

Why Everything Must Change Every Five Years

It seems like every time you turn around, there's a new JavaScript framework to help solve this or that problem. Read on to get one dev's take on this.

· Web Dev Zone ·
Free Resource

Jumpstart your Angular applications with Indigo.Design, a unified platform for visual design, UX prototyping, code generation, and app development.

You complain about JavaScript fatigue, and that's valid. The ecosystem moves fast, and it's hard to keep up. Dare I say impossible?

But won't you think of the authors and the conferences and the speakers and the trainers and video course makers and everyone else working hard to teach you all the new things?

A whole industry relies on new things coming out to confuse you!

Why, if you're not confused about that new feature, who will come to our talks? Who are we going to teach?

If a new framework doesn't come out to boil the ocean and replace everything that existed before it, who is going to buy the hundreds of books and video courses that we want to make?

You can't make more sales if there's nothing new to sell. If you can't make more sales, how are you gonna pay rent? Hosting fees? Vacations in Bali?

Sure -- hundreds, even thousands of people enter the field every day. People change jobs and become software engineers. People go from one type of engineering to another. People grow up and get their first jobs.

The field is growing, and that's a good thing. You can sell your conferences and your books and your courses to the newcomers.

But wouldn't it be nice if you could also sell them to everybody else? There's a lot more of everybody else.

Software Engineering is growing at about 24% per decade. You can't build a training industry on that. Not a big one anyway.

There's a whole other 76%! You can sell stuff to them.

But you first need to get them confused.

Invent a new front-end framework. Say that tables are bad and CSS rules all. 10 years later, turn CSS into tables. Double whammy!

Create new bundlers and compilers and tell everyone that JavaScript must be compiled - it's really much better that way. Invent a whole new way to talk to backends because REST and Ajax are lame.

Don't tell anyone that all these things are pretty much the same as always behind the scenes. You still need Ajax to talk to the backend, everything still turns into HTML in the end, and CSS still winds up a bunch of <style> tags no matter what bundler you use. 

It's the oldest play in the book. Invent something new, convince everyone it's better, watch a cottage industry spring up around it. Training, consulting, all the things.

But really, we're all at the mercy of this. Sometimes, I think the big companies just have too many engineers with nothing to do so they keep coming up with new things.

Take a look at the Indigo.Design sample applications to learn more about how apps are created with design to code software.

Topics:
javascript ,web dev ,javascript frameworks ,vue.js ,react.js

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}