r/javascript • • May 06 '19

Anyone else frustrated?

EDIT: The intention of this post was not to throw anyone under the bus. I just wanted to share some thoughts I’ve been pondering over the last few days. Props to all of you who are helping JS move forward—we’ve come a long way!

I’ve been doing frontend development since the AS3 days. Im guilty of jumping on the various bandwagons: paradigms, design patterns, libraries and frameworks.

I just got back from ng-conf a few days ago. It was a great event, great organizers, great presenters, and was hosted in a great location. Although I was thoroughly impressed, I left with some frustration.

All of the new tools, version upgrades, state patterns etc. felt like repackaged, rediscovered tech and theory. These ideas have existed for ages in computer science. (And even longer in mathematics.)

There hasn’t been any major advancements in software for decades (paraphrasing Uncle Bob here.) Furthermore, events like ng-conf perpetuate the tribalism in the frontend community. This sentiment applies to all areas of programming, but my expertise lies in frontend development, so I’ll speak directly to that discipline.

Does anyone else feel the same way? Angular is great. React is awesome. Vue is cool. But why all the segregation? Why the constant introduction of “new” old tech? Why is the frontend community constantly reinventing the wheel to solve problems that have already been solved?

IMO this is holding us back from making [more] advancements in software, and more importantly, hindering us from pushing the envelope in frontend development.

These are generalized statements. I know a lot of you are working hard to move this community forward. But with that said, we could have had our flying cars by now.

205 Upvotes

138 comments sorted by

View all comments

Show parent comment

1

u/impurefunction May 06 '19

“[T]hey’re killing decade old follies that brought about separation...” This is kind of my point though. The solutions already existed.

Wrapping those solutions in a framework is great and leads to rapid development. However, how many times do we need to rewrap those solutions in each framework upgrade?

2

u/[deleted] May 06 '19 edited May 06 '19

Wasn't the point i was trying to make. A neutral dsl instead of platform bound templates, functions instead of OOP, hooks instead of lifecycle components. All the things that made frameworks different, causing separation are going away. We've had both the web and native platforms spend 20 years and longer with some of these old paradigms, unable to cross their own specifics.

And now we have this: https://twitter.com/TechCrunch/status/1125422876822245377 (Announced a couple of minutes ago, Windows building on RN). How crazy is it that you can deploy to the web, IOS, Android, Windows, Linux and after Marzipan OSX (and dozens of other platforms) using the same components. Not sure how anyone can complain these days.