Why is front-end development so unstable? (2018)

Post by tomcam » Tue, May 31, 2022, 3:37 AM UTC

abraxas wrote: post #122

xwolfi wrote: post #117

Earlier quoted context omitted.

Depends HOW you coded. I started JS at 11 yo in 2001, and became fulltime around 2012 - 2 more years of JS than you, I'm your grandaddy in this ever changing mess... I do not know Broccoli either. Googling it: "A fast, reliable asset pipeline, supporting constant-time rebuilds and compact build definitions" I raise my eyes to the ceiling and whine "why the hell isn't there an Oracle or IBM for JS to finally standardi…

Very, very few places will let you not use a framework nowadays. There is a ton of cargo culting around JS frameworks and coding vanilla is pretty much heresy land these days. Personal projects? Go for it. Commercial apps built for your employer? Good luck with that. Not only will you be raked over the coals for "reinventing the wheel" you'll also be blamed for any stumble along the way, whether it's related to using…

Post by bobthepanda » Tue, May 31, 2022, 3:54 AM UTC

lopatin wrote: post #137

bobthepanda wrote: post #23

Earlier quoted context omitted.

I think part of it is also level of effort. You could right click "inspect element" in any browser and mess around in the html or the JS console and see things happening live. This is an extremely low barrier to entry. Low barriers to entry are good, our profession is very well compensated and developed economies could certainly use low effort ways to get people from lower compensated jobs into higher compensated job…

Yeah but to be good, you have to have like at least 5 years of experience shipping stuff. It's kind of like going through many years of law/medicine school.

Post by bigmattystyles » Tue, May 31, 2022, 4:33 AM UTC

syntaxfree wrote: post #139

bigmattystyles wrote: post #21

Earlier quoted context omitted.

I don't agree with you but I don't disagree either. Our use cases are very vanilla, and now that I have quite a bit of sway in my team, when people deviate from the showcased Kendo way, I push back and see if the desired way deviating from Kendo is a necessity or a nice to have. If it's the former, we sometimes have the experience you described, though I've often be helped by stackoverflow, their forums or Kendo's su…

You’re glowing, man.

Post by [deleted] » Tue, May 31, 2022, 5:13 AM UTC

miiiiiike wrote: post #130

etoxin wrote: post #126

Changing APIs. When the front-end gets JSON from an API. We really don't know what we're getting. We need to liaise with the API team to figure out how these APIs work and when they change, we don't know what changed. Luckily there is a new solution. End to end type safety. Using tools like graphQL allows FED build tools to get the entire API schema and bring that into the typescript build. If the API changes, your b…

This comment makes absolutely no sense in the context of the article. Did you read it?

Post by ricardobeat » Tue, May 31, 2022, 6:44 AM UTC

nawgz wrote: post #108

ricardobeat wrote: post #84

Earlier quoted context omitted.

These are not really counterarguments to the fact that things change a lot here, and newcomers and veterans alike need to continuously learn, and pick the best. None of these started off as the default choice, I remember when each and every one of these was the weird / risky option.

They are very much counter arguments to the idea that there is big churn still happening. Webpack 2 was in CRA in 2017 Redux and MobX have been the #1 and #2 state managements for that whole span, and clearly all the observable libs are successors of MobX after Proxy came out Every language changes, many with breaking version changed that JS avoids I don’t know how you’d point at package management as an issue in JS…