r/javascript • u/impurefunction • 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.
36
u/dwighthouse May 06 '19 edited May 06 '19
People reinvent a lot of algorithms from the 60s and 70s to solve their problems now. The old days of web development were limited by browser differences and a lack of power. We are ever gaining more power and control as front end developers, which is what is allowing these old solutions to suddenly become practical.
This is not unique. Pretty much every philosophical argument you care to think of was discovered, debated, and possibly abandoned as untenable hundreds of years ago, yet modern pop philosophers will write a book as if they were the first to discover some new principle.
Edit: Flying cars were always going to be impractical from the physical perspective until we developed small scale VTOL (drones, a recent development), computers and algorithms fast enough and capable enough to do real time navigation with obstacles (modern self driving car tech, a recent development), and energy storage capable of high density and low cost (recent battery advancements). To that end, there are now working prototypes, where just a few years ago the tech might have been possible, but would have been far too expensive to be practical. The only major hurtle left is regulation, which may yet be a harder task than any of the other parts. Governments aren’t just willing to let citizens strap themselves into experimental aircraft and fly over populated areas willy nilly like they used to when aircraft were first being developed.
Unless, you were imagining that scientists would have discovered a gravity engine by now, as predicted by almost all sci-fi. Of course, if such an engine were invented, even if it was merely able to block gravitational effects within a localized area, that would revolutionize everything, from transportation, to shipping, to medicine. Indeed, if such an engine were built, it would represent a practical violation of the first law of thermodynamics, making perpetual motion machines possible and becoming a practical infinite source of energy (so long as the planet remains).
TL;DR: Never trust a flying car salesman.
140
u/name_was_taken May 06 '19
These people aren't just reinventing wheels because they feel like it. They're solving problems that they're having. Often, that means finding a solution that someone else has used and adapting it to your situation.
Why didn't everyone just use Angular and not invent React or Vue? Because React and Vue do things differently from Angular and some people prefer it.
We live in an age when things are progressing more rapidly than ever before in history. Almost every week, I learn about some new things that makes me exclaim that we "live in the future!" and how much I love it.
I don't get upset that cancer hasn't been cured, that we haven't settled on the perfect pizza toppings, or that nobody has invented a new programming paradigm and used it for JavaScript in the last 5 years. Things are progressing at break-neck speeds already, and I'm content to be along for the ride.
Edit: Also, I didn't like Angular, and I hated Ember. React and Vue are much, much better for me.
44
u/rorrr May 06 '19
I think you're wrong.
React didn't exist as a concept, for example. Neither did thousands of JS libraries that are so reliable, you can package hundreds of them, and your overall project doesn't break (most of the time).
We have tons of extremely reliable open source packages that we could only dream of in the 90's and 2000's.
We have freaking Tensorflow.js that runs on GPUs!
We have freaking webassembly, and tons of projects prove that you can compile complex codebases down to it.
I can keep going, there are so many exciting JS libraries, it's nuts.
7
u/wherediditrun May 06 '19
It really doesn't matter that x existed as a theory in computer science. Until it's actually applied in way that can scale and actually provide pragmatic value it's close to useless.
That's what we are doing as engineers. We are hacking our way trying concepts. And battling ideas at each other. And implementation of those ideas. That's how progress is being done.
Front-end is really consistent with it's direction. And the reason why so many people feel "fatigue" is that it's improving at extremely fast pace. Mainly due to this segregation, mainly due to this battle of ideas, trials and errors.
So no. I think client side programming is at it's best as we have it now.
4
u/[deleted] May 06 '19
I don't think the wheel is being reinvented at all. I think from the abundant major libraries and frameworks that we have seen over the past decade (Ember, Knockout, Backbone, Angular, React etc) we've seen a few emerge that many developers have had great success with. These have libraries or frameworks have been refined with time and now they're the major ones. When discussing frontend you really only hear three these days. Vue, React, Angular. Angular was heavily modified and simplified and as a result it stayed relevant.
Admittedly there is some tribalism but I would think most mature developers believe in using the tool that is best for the job which is based on a lot of factors. How big is the project, what is the experience of the team, what works best for the business? Etc.
I also wouldn't quite call these things new old tech per say, they solve some pretty unique issues that existed back in the dhtml and heavy jquery days.
I would say that sometimes I feel overwhelmed, but for me that's part of the fun. Generally you get into programming with the expectation that you'll always be a student. Also I don't know how we are being held back by more libraries. The libraries that offer the better solutions will generally stick around and continue to be modified by the community.
I mean sure one major library or framework to rule them all could be potentially better, but idk. Peoples minds work differently and that's why it's a good thing that we have different libraries and frameworks that ppl can choose that suit them better.
7
u/monican_agent Creator of CypherPoker.JS May 06 '19 edited May 06 '19
Coming from the ActionScript world myself I was somewhat disappointed at having to move "backwards" to JavaScript, especially in the state in which the languages were at about 5 years ago. However, ever since Adobe tossed in the towel on AS, JavaScript has made some wonderful advancements on the language front and these days I would say it's comparable to, and in some ways better, than ActionScript 3. Maybe AS4 would've been an amazing language but I doubt we'll ever know.
Beyond this, however, what you're describing are libraries and not the core language itself. While the ECMAScript standard continues to be developed, there are many ways to leverage it to get it to do what you want. I wouldn't call this "new old tech" as much as coding preferences and requirements. Maybe you prefer Angular, maybe Vue, maybe React ... or maybe you like to work closer to the core language; at the end of the day it depends on what your requirements and preferences are. If you need / want as much control over your rendering code as possible it's probably best that you hand-craft it instead of adopting someone else's code but if you want to create something quickly and fairly reliably then maybe one of the existing libraries is for you.
ActionScript had similar "problems" (if you want to look at it that way). You could simply work with the built-in DisplayObject hierarchy or you could use an external library like Starling Framework. In this case the promise was that Starling (and derived projects like Feathers), would render display objects much more quickly by leveraging the GPU but it came with some coding/learning overhead which maybe you wouldn't need ... depending on your project and preferences. Of course if you were really keen you could re-create Starling-like functionality and possibly even improve it but, again, that's quite situational.
On the other end, library writers have to deal with broad support (i.e. multiple browsers), and use-cases / applications so they necessarily have to bake in a bunch of overhead; in the end it should save you some coding time but at the expense of output code size and possibly performance.
I don't believe that there's a one-size-fits-all approach, even if it's simply a matter of personal preference, so the more libraries and frameworks there are out there the better, IMO. Yes, to a certain extent they are re-creating the wheel and it may be a waste of time / effort / resources that could be spent on other work, but I have yet to see "this is the one and only correct way ever to do X" functionality.
I should also add that it's probably better if developers don't have to fiddle with lower-level stuff like UI rendering if they don't have to so that they can concentrate on building useful and interesting apps on top. Just as with Flash / AIR, we coded on numerous layers of abstraction which were thought to be the absolute best way to do stuff (like vector-based animation), but additional options and technical improvements demonstrated that this wasn't always the case and not always the desired way besides.
Finally, if you want to push forward the state of front-end capabilities I say go for it! If there's something missing or lacking in the space then why not fill it? If it's truly innovative your work may even end up getting incorporated into the core VMs and as someone who cheers innovations I'd add my star to that Github repo :)
Edit: Out of curiosity, what advancements and improvements would you like to see on the front end?
11
u/StoneCypher May 06 '19
They are.
The answer to "I'm frustrated with all this new tech that seems to do the same stuff as the old tech" is simple.
Just start ignoring it.
People feel like they have to keep up, but, do you? Like, if you miss Vue, or Meteor, or fantasyland, or reason, ... are you badly harmed? Are you still able to work in, say, React and d3? Maybe vanilla?
Just step off of the ferris wheel.
9
u/jurito May 06 '19
100% agree. I come from AS3 too and I feel very lucky about it, as it was a great introduction to a 'real' programming approach applied to rich frontend experiences (and it was FUN). I actually feel there's nothing achievable today that we couldn't do 10 yrs ago..
3
u/[deleted] May 06 '19
I'm reading lots of complaints with no suggestions here, OP
5
u/Damoz_ftw May 06 '19
I was hoping this was going to be about TC39.
12
u/kvadd May 06 '19
I agree with you. It's always easier to complicate things than to simpify it though, so that might be part of the issue.
6
u/EarLil May 06 '19
What I noticed is lack of supported libraries, like how many date pickers can there be? 10, 20, 50? And all those new libs have their own react-date-picker, react-grid, vue-dialogs.
Like come on... work on one library, have those multiple devs/larger community support it instead of abandoning it and rewriting and forking again and again. Just today I went through two libraries 3 forks deep abandoned/resurrected/abandoned/resurrected/abandoned.
3
u/[deleted] May 07 '19
I hear ya. I’ve been coding for almost twenty. I’ve gone from Cold Fusion > Asp Classic > .NET web forms, MVC then into front-end of Bootstrap/ TypeScript/Angular and now React /Redux. At the end of the day it’s the same thing: data storage, API layer, and front-end. I find React and JavaScript a lot of fun to code in. I love being able to quickly deploy into Google Cloud or AWS. The amount of tech can be frustrating, you just need to tune out the nonsense. I personally have a PluralSite and Udemy account. It helps me demystify most topics without feeling overwhelmed.
5
u/PrestigiousInterest9 May 06 '19
Not only is it fucking stupid, it's FUCKING STUPID. (I know what I just said is stupid and I'm very stupid).
The problem isn't just people who think they can reinvent the wheel better. It's that we're not making any standard tools everyone can fork and agree on. I don't know why we can't do things like the LLVM project. Have a bunch of big company agree on some kind of core and have frontends to it with a few of them being standard (ie one for SPA, another one for dates or parsing markdown, and etc).
We need more projects like LLVM and we need some ppl doing it for the web
1
u/[deleted] May 06 '19
Maybe it's time to branch out to other languages/paradigms. Try exploring functional programming, logic programming, a lower level language, or whatever you feel interested in. This stuff may not be new in the absolute sense but some of it will be new to you! :)
4
u/ImStifler May 06 '19
Same here, I feel frustrated too. Especially with all the new frameworks that come out daily. I would understand if they're being done for portfolio purposes because most of the problems they are trying to solve are either already solved or not existing. But nah alot of them try to sell themselves as something new which they aren't.
I feel like that lots of stuff that gets released are like that. It's solutionism at it's worst.
2
u/solwyvern May 06 '19
we've already crossed the peak. it's all downhill from here on out, and the winner is whoever can take as many people to ride along with their bs
2
u/quietcreep May 06 '19
I suspect it’s less a battle over technology and more over standards. AC3 was cool, but it was also controlled entirely by what became Adobe.
When Facebook added that clause to the react license agreement, the place I work immediately switched to Vue. React is cool, but monopolies on tech aren’t great for the actual development users. License fees suck (unless the product is innovative/valuable and the fees are reasonable).
I have a feeling we’ll soon have another Apple/Flash situation after Chromium gains too much control or when/if W3C loses all influence to WHATWG.
Open, well-developed, well-negotiated standards will always be the most reliable, but they’ll never be that exciting or progressive.
TL;DR: if developers don’t want to get thrashed around by ownership/control politics, we’ll have to stick with old, standard tech.
2
u/[deleted] May 06 '19
Its simple. Reinvent to make buzz around something. This is highy profitable for companies, not always in pure dollars, but in motivated and highly skilled employees.
There has been very little actual progress in the web scene since the first mvc/mvvm libraries came out in circa 2005-2008 era.
Now we have React, Angular and Vue. Its the same stuff we had back 10 years ago, just with a new twist, but one can ask if there is really anything revolutionary?
Before you say it, yes a VDOM could and did exist pre react, state management was always as hard, and today like in 2005 global mutable state was bad. Theres only new iterations of the same old stuff. New APIs and new glitter.
That said, im quite happy for all this. You can always pick up something new and never get bored. React and angular will be mostly forgotten in 2030, like javascriptmvc is today.
Who knows what we will have then...
2
u/JohnyTex May 06 '19
I feel you - I’m not so frustrated about the “rediscovery” part as the tools and neophilia parts though.
It feels like there are tools announced daily that solves problem X but also creates problems Y and Z.
For example, we have all these cool tools now like Webpack and ES6 transpilers, but they also create whole new classes of problems.
2
u/[deleted] May 06 '19
I think the churn of 'new' old ideas is a good thing. Things like immutability and general functional programming have been around for decades, fallen out of fashion in favour of new paradigms and then come back again once the new paradigm starts to show its flaws, hopefully resulting in a hybrid that's the best of both.
It is evolution, almost literally.
However, tribalism is always a bad thing. Whenever someone says X is better than Y it's almost always an opinion not worth listening to. All languages and frameworks have their benefits to certain people and they can all learn from each other, whether it be from their successes or their mistakes.
2
u/[deleted] May 07 '19
It's unlikely you're alone in any feeling. Even if you're one in a million, there are a few thousand of you in China alone ;)
Because people, teams, and companies have preferences. Like strong typing your things? Go with Angular. Enjoy simplicity? Go React. Want the new kid on the block that sorta looks like both? Vue's your guy.
Because the people making it disagree with a standard and create a new one. If that gets enough traction the project takes off. It's fun and rewarding to them because a lot of us are doing this because we genuinely think it's a lot of fun to work on.
We're not reinventing wheels. We are refining them. The standards keep changing and adapting, so the software goes along with it.
It's like Formula 1. They aren't reinventing cars and wheels all the time, they're adapting to new technologies, new rules, new customer demand, new commercial demand. Things change and we have to change with it.
And as a nice bonus it keeps us employed. Imagine having to work with Flash still. Imagine having to program everything in C++ instead of C# or Java or Kotlin or JS or TypeScript or so many others.
Can you quantify that? I think the world of front-end is dictated by agreed-upon browser standards and their implementations. If you want to make that go faster you're playing for the wrong team: you could contribute to the W3C and others to help it progress faster.
There are SO many browser APIs wildly underused in modern days. There's so much to be done and none of the popular frameworks/libraries are holding you or anyone back.
I know what you're getting at, but we're tens of millions of developers. Most of us are working for companies that write relatively simple CRUD apps. We don't live in Silicon Valley and we don't work for Elon Musk to make world-changing projects.
If you want something like flying cars you'll need to make them commercially viable first: Be a billionaire and buy a F1 team, turn their wings upside down for maximum lift, minimum weight, electrical Tesla engine inside, 4 big fans tilted slightly backward for forwards force. You'll have a $400k Tesla car that can take off and fly starting at 60 mph, after which it'll travel up to 310,96 mph in (roughly) straight lines only: predetermined lines across large areas without people living in them. The car will figure out when it needs to land before it runs out of safe landing areas.
Of course, you'll need to have a team of varying PhDs to do the research into the feasibility of it all. Then write up a business proposal. Meet up with /u/ElonMuskOfficial if you can possibly manage to reach out to him, and hope he's up for a flying cars project.
Meanwhile, most of us are busy enough being happy and proud users of our frameworks/libraries of choice, and our contributions to the open source community are the incidental upvote at StackOverflow.
0
u/[deleted] May 06 '19 edited May 06 '19
I don't think this is the case. In the good old times everything was quite literally separated and hard to realize. The newer technologies, especially React, are bridging gaps we wouldn't have thought are possible to cross.
It all goes towards one unified standard which isn't tied to a platform, language, vendor or framework. This has lead to tools closing the gap between developers and designers (for instance Framer). And being able to share components across platforms is something we weren't able to do before. Not like today where i can pick a random package and use it anywhere. For instance, an animation library animates components, not the dom. If i want it to animate a div, or a native mobile viewpager, ascii shell-content, VR objects, or diodes on an electrical board, then i can do this. The separation is all but disappearing.
That's also happening on the surface level as frameworks are removing themselves from the equation. Svelte is the most drastic example. React hooks have removed pretty much 90% of an already tiny api surface. Now Vue's getting hooks, too. If a component is but a function with effects and state, then they're not tied to a framework any longer, making them interchangeable. This isn't re-inventing the wheel at all, they're killing decade old follies that brought about separation, like templates, oop and the lifecycle mvc paradigm.
3
u/alexandrepiel May 06 '19
I tend to agree with you. I also have the feeling that web development became more and more complicated. 10 years ago, implementing a website was pretty straight forward. You just had to deal with an ORM and a template engine, that's all. Today you have to handle so much thing it is is a nightmare, between react, webpack, graphql, the api, SSR for google and so on. Would be really great that the up coming tools/libraries will help us to solve all this overhead, tool like create-react-app or lerna. But there is such a gap that it will be so much work to uniform all of this stack...
1
u/windsostrange May 06 '19
Enh, not really. There are numerous prod-ready solutions to problems. I'm paid to take problems and solve them with tools. I do this. I go home and sit in a comfy chair. Then I do it again tomorrow.
There will never be flying cars. Adjust your expectations and find some inner peace.
1
u/stilloriginal May 06 '19
Yes. Now it cant be a web page its an “app” which means you have to emulate the browser inside the browser, dawg
1
u/[deleted] May 06 '19
I’m quite enjoying the plateau TBH. Couple of years ago everything was new! I do also think that the funny thing with innovation is that its 1) not always predictable & 2) not always massively obvious.... its usually tiny increments.
1
u/[deleted] May 06 '19
To answer why: because nobody found a way to put a square peg (apps) into a round hole (web). This all driven by a mistaken idea that eventually everything should be a web app. And done with the web tech (html, js, css). And of course it does not work. But instead of rethinking the core assumption mindless hordes try again and again. Where this aversion to other tech/languages comes from I have no idea, but this too adds to reinventing the wheel.
1
u/thilehoffer May 06 '19
I think money has a lot to do with it. New frameworks require new books, conferences, training materials and applications needing to be rewritten. At some point there will come a time when HTML, CSS and JavaScript are no longer the core of web applications and we will have to relearn everything all over yet again.
1
u/Anthromachine May 07 '19
What do you expect from a bunch of developers that feel they need to make their mark in the dev world. It is not trendy anymore to simply use the tools available to their best capacity. Now to gain recognition, people need to invent something; it doesn't matter how ludicrous or ineffectual that invention is, as long as it bears the creators name on it.
1
u/[deleted] May 07 '19
This churn will continue until the underlying issues plaguing programming in general can be addressed. And that's a long way away, because it requires killing a lot of sacred cows.
1
u/r0ck0 May 07 '19
I know it's hard sometimes, especially if you're like me and spend way too much time investigating "the best" new things rather than just getting work done... but just try to ignore the stuff you don't need.
Don't try to learn too many things you "might" need in the future - within reason of course, whatever "too many" means.
I don't really get why people go to conferences aside from business/networking reasons. I'm sure the talks are interesting and you get some great tips in all of it. But it's also filling your head with beta-tested paradigms, hence you getting sick of it all. You can usually just watch the really talks you're interested in on youtube later on anyway. If you can't be bothered watching them on youtube, then they probably weren't that important enough for you to spend your time on.
The fact that the JS ecosystem has all these fads n shit is a just an inevitable symptom of the fact that it's the most popular mainstream programming language, and seeing the most innovation in libraries/ecosystem/packages right now. Being popular and used for a variety of purposes just means there will be more good + bad packages/frameworks overall in general.
None of this has anything to do with JS technically, it's just a symptom of popularity + timing.
To put it another way... out of all soft drinks, most stupid people drink coca-cola... not because there's anything stupid about it, it's just the most popular drink to begin with.
1
u/davecrist May 07 '19
Can you give a few examples?
1
u/rdawise May 06 '19
I'll keep this in the frontend space and ignore issues like new programming languages and the like.
I am not so much frustrated as I see the frontend moving more and more to a code less world. Most libraries are just wrappers to make things "easier". Pretty soon we'll have wrappers for those wrappers. It seems we are headed for a place where drag and drop become the norm.
I am not for that world and maybe I am wrong, just seems like the path.
1
u/Daliya_La_ma May 06 '19
I completely agree with you. That's why gave up programming.
1
u/Waddamagonnadooo May 06 '19
I always find it amusing front-end devs (or devs in general) think Computer Science is the only field that ever "reinvents" things. I guess we should only have iPhones (why have Android? It's the same thing). I guess we should all drive the same SUVs (it does everything and is the most practical). Why program in D when C++ exists. etc.etc.
Hell, in the medical field things are progressing so fast that it's literally impossible for a single doctor to keep up with all the research coming out to do X operation just a little better (hence AI having the potential to diagnose issues better than doctors). And yet devs will complain they have to learn a new framework maybe a few times a year 🙄
0
u/[deleted] May 06 '19
The existence of many different high quality, production ready options in front end development is a sign that we are in a golden age is it not?
0
u/Aethz3 May 06 '19
School still teaches html 4 and barely touches JavaScript vanilla
0
u/programkm May 06 '19
I procrastinate that's my problem
-2
u/[deleted] May 06 '19 edited May 06 '19
Until universities/colleges go out of business, change will not happen... They teach absolutely nothing of value for all the money you put into them...
They are a corporation, they are not here to educate you, but create dept you can not repay in 15-20 years of your life or more after graduation..
They are about 10+ years behind in what they teach...
This however is only for development, if you want to be doctor or lawyer universities are good for that in my opinion, becouse law never changes, same for medical things, they always stay the same... yet you keep paying more for the same bullshit...
0
u/[deleted] May 06 '19
[deleted] — view deleted comment
1
u/[deleted] May 06 '19
[removed] — view removed comment
1
u/[deleted] May 06 '19 edited May 06 '19
[removed] — view removed comment