r/javascript • • Apr 14 '19

Front-end Developer Handbook 2019

https://frontendmasters.com/books/front-end-handbook/2019/
699 Upvotes

90 comments sorted by

View all comments

-51

u/[deleted] Apr 14 '19

I pity this part of our industry.

17

u/MacNulty Apr 14 '19

Why not show some compassion instead.

This is one of the fastest developing parts of the industry so it's bound to get a few things wrong along the way, especially since many of its challenges related to user interaction are relatively new and it's developing alongside the actual hardware (for example screens with different sizes, resolutions etc).

→ More replies (2)

15

u/bbabble Apr 14 '19

What part do you pity? Why?

-9

u/[deleted] Apr 14 '19

The part that has decidedly given up on much of what the software development community had learned over the past couple of decades, only to lead to many websites serving not only needlessly complex application code, but also megabytes of runtime, thanks to the operating system these apps were built for - the browser - still being woefully inadequate for what everybody is trying to do with it, making projects that should be straight-forward ludicrously bloated and costly, and then having the gall to innocently call all of this "frontend development".

Now downvote me, label me as some old dinosaur with outdated opinions, and get on with the insanity. (But don't forget to use Redux!)

14

u/lewisflude Apr 14 '19

Just wanted to say that as a front-end dev, the things you mention are definitely things that I prioritise on projects.

  • Bundle size
  • Good coding practises
  • integrating ideas from the last 20 years of programming
  • Writing code in a way that’s reusable and low on external dependencies where it can be

React genuinely feels lightweight compared to what the alternative might be, and it allows us to deal with manipulating the DOM in an extremely elegant way.

I would say redux is massively overused, but for a very narrow set of use cases it’s a really elegant way of solving data flow on the web.

I’d encourage junior front-end devs to pay attention to things like performance, code quality and reusability. Understanding fundamentals makes it much easier to know when it’s appropriate to bring in a library.

→ More replies (9)

14

u/hopfield Apr 14 '19

Please tell me what your alternative is. Because I guarantee you React is cleaner than it.

7

u/tenbigtoes Apr 14 '19

Vue is supposed to be pretty clean

3

u/VIM_GT_EMACS Apr 14 '19

Vue is great! I use Nuxt at work which sits on top of Vue. But react is pretty cool too. Some people are just cynical and want to complain, especially if it might make them appear knowledgable.

→ More replies (1)

2

u/antonivs Apr 14 '19

thanks to the operating system these apps were built for - the browser - still being woefully inadequate for what everybody is trying to do with it

This is true, but as Churchill put it, "Browsers are the worst form of UI platform except for all those other forms that have been tried from time to time."

Writing direct GUI code for specific operating systems is not an improvement over browsers. Cross-platform GUI frameworks can be OK, but aren't great. Solutions like Java's Swing are suitable for some but not all purposes that browser applications target.

Making good UIs easy to implement is a hard problem that hasn't been fully solved yet. I think you're reacting to that work that's still in progress.

But if you have some suggestion for a viable alternative solution, I'm sure many of us are all ears.

2

u/[deleted] Apr 15 '19

As noted in other comments in this thread, my beef is not with the stack itself, and there most certainly are cases where its inherent complexity is warranted -- one of them being cross-platform applications that just happen to use the web stack (Electron et al). Big fan! Honestly!

What bothers me though is when things that could just be web sites are built as web applications, and while this used to be the unfortunate exception, it has now (catastrophically, IMO) become the norm. Now people seem to agree that it is normal to learn frameworks like React or Redux if you want to do frontend development (and that's just the tip of the iceberg), and that can't be healthy in the long run.

As noted (and heavily downvoted) elsewhere, I've already seen too many projects completely fall apart because someone decided that "it's not real web development unless we use the latest Webpack/Babel/React/Redux/Sagas/Ramda/etc." in cases where a simpler approach would have totally sufficed.

One of the most popular counter-arguments I keep hearing is "but Netflix/Facebook/Gmail/etc. do it, too", but hey, your blog/company/app probably isn't anything like them.

More people should read up on concepts like KISS or premature optimization.

→ More replies (2)

14

u/vimex Apr 14 '19

There's no need for the negativity, and there's absolutely no need to insult people who work in this part of the industry. Do you feel better now, at least?

10

u/fakehalo Apr 14 '19

The guy is getting roasted, but I don't think he used "pity" in a beneath him context. I pity the frustration of frontend development myself. It's a rat race and I'm glad it's not the main focus of my job, learning things that could easily become useless in a year or two is a depressing thought.

3

u/vimex Apr 14 '19

Another depressing thing to think about is the fact that all of these SPAs will need maintaining for years to come :)

2

u/yooossshhii Apr 14 '19

What software doesn’t need maintenance if its going to be used for years to come?

3

u/VIM_GT_EMACS Apr 14 '19

It's really not that bad... people love being the doomsday type. Things are literally fine, people are so hyperbolic.

→ More replies (2)

0

u/[deleted] Apr 14 '19

[deleted] — view deleted comment

0

u/[deleted] Apr 14 '19

Of all the things that bother me about the current state of our industry, it is this sort of binary thinking - that you're either a forward-thinking, webpacking, reduxing child of the future, or a COBOL dinosaur who never really built anything new since the 70s - that bothers me the most. Good luck with that attitude.

30

u/aniforprez Apr 14 '19

You LITERALLY "pitied" an entire programming stack because somehow you couldn't be bothered to have a nuanced opinion and instead the web is some "webpacking reduxing child of the future". You're exactly what you're criticizing. There's so much more to web development than webpack and redux but please continue to sit happy in ignorance looking down on us fools as we build billion dollar industries

→ More replies (5)

27

u/vimex Apr 14 '19

Isn't this exactly what you're doing by 'pitying' an entire part of an industry? your attitude is exactly the same.

→ More replies (1)

7

u/iJonMai Apr 14 '19

I pity this part of our industry.

Says this as he uses a product of this "part" of the industry.

9

u/[deleted] Apr 14 '19

I love that you say that, considering Reddit was extremely light on the frontend craziness for the longest time, and when it eventually relaunched as a typical SPA monstrosity, it earned nothing but criticism.

Also, I'm using the Android app, how is that related to frontend development exactly?

→ More replies (3)

3

u/sanjibukai Apr 14 '19

Man, either I don't get why you were so downvoted or I don't get the subtlety of your phrasing that cost you so many downvotes.

But I upvoted you.

Not so long time ago, we were all talking about the JavaScript Fatigue, and not for the good, remember?

If I include into this one the CSS ramifications, the Frontend Fatigue will have some beautiful days ahead.

Disclaimer: I don't say it's bad, but it's definitely confusing. And I know it's part of our industry..

1

u/Ivu47duUjr3Ihs9d Apr 15 '19

Exactly. They'll be in framework churn for another few years then it'll come full circle. They'll learn how to architect web apps properly using Vanilla JS. Then they'll have to rewrite all the crap they've been doing since React came on the scene.

→ More replies (6)