r/javascript • u/nightman • Jan 31 '17
Front-End Developer Handbook 2017
https://www.gitbook.com/book/frontendmasters/front-end-handbook-2017/details46
u/roselan Jan 31 '17
it's called 2017 because by the time you finish to read it, it will nearly be 2018.
edit: great work thou. I don't know where you find the time to put all that together.
1
30
u/michaelconnery1985 Jan 31 '17
Knowing the JS community half of this will be obsolete within 2 months
9
u/BlueHeartBob Feb 01 '17
As someone who's gotten into JavaScript in the last 6 months and have gotten pretty into react, It sorta feels like this, I understand that you shouldn't be jumping from one framework to the next hottest one but it does feel pretty confusing for someone who's just trying to land some work. Everyday it feels like there's some sort of revolutionary new thing out that's blowing people away. Reading this and only understanding a little bit more than half of what they're even talking about doesn't instill confidence in myself. I now read that react is basically changing into something else just as I believe I have a good understanding of it. Maybe I'm just getting inside of my own head but it's sorta overwhelming.
13
u/greatfool66 Feb 01 '17
Learning Javascript I've had more fun with it since abandoning the Serious Computer Scientist mindset that I need to understand everything at a low level and just started writing fun, hacky code that gets stuff done and not worrying about what % of stuff I understand.
1
u/El_Serpiente_Roja Feb 01 '17
Its only been 6months though. Plus all these frameworks are just implementations of general design patterns. If you get a strong understanding of the underlying design pattern it wont be hard to categorize and learn new frameworks all the time.
0
Feb 01 '17
[deleted]
3
Feb 01 '17
But do you like it more than React enough to tell people to make the jump?
0
Feb 01 '17
[deleted]
1
1
u/youcantstoptheart Feb 01 '17
I use single file components in react, so I know how you feel. Currently trying to build a UI library to convince my team to switch.
0
Feb 01 '17
[deleted]
1
u/youcantstoptheart Feb 02 '17
With
styled-components. this progress arc component is a pretty good example5
u/SquareWheel Feb 01 '17
One thing worth keeping in mind is that there's only so many different takes on the same concepts. When you're learning a new language/framework/workflow, you're learning to incorporate and understand those concepts.
Even if there's a new flavor of the month, you'll be able to understand it more easily having some experience under your belt.
That goes for anything. You just learned
screenand have to switch totmux? It's cool, because you understand what they do and why they do it.Same for
grunttogulp, orlesstosass, or whatever else. It's a whole lot easier to learn the second time, so try not to sweat it so much.4
u/destraht Feb 01 '17
I feel like we have finally worked through the flurry since IE6 went off the market and that its all going to be pretty boring for the next fifteen years.
1
u/omegafivethreefive Feb 01 '17
That was my impression as well. I'm not sure how you can follow the Javascript trends and keep maintainable projects.
Sure, 6 months one-man projects are no problem but if you're working on something for a few years and you have to look back at it several years later you'll probably have a lot less fun.
The sheer amount of knowledge required to understand even the currently proposed stacks is staggering.
1
8
u/TheDarkIn1978 Feb 01 '17
Under "Front-End Interview Questions", there's a link to:
10 Interview Questions Every JavaScript Developer Should Know.
It's not clear if the author is being purposefully biased for dramatic effect, or if he's just blissfully unaware of his blatant hypocrisy while writing things like:
I advise people to hire based on whether or not a developer believes in class inheritance. Why? Because people who love it are obstinately stubborn about it. They will go to their graves clutching to it.
... followed by:
When is classical inheritance an appropriate choice?
This is a trick question. The answer is never.
Good to hear: Rarely, almost never, or never.
Red flags: Any other response.
I think that linking to his article, and therefore validating this author's narrow minded opinions of what it means to be a valuable JavaScript engineer in 2017, particularly when it comes to using ECMAScript 2015 features, is a great disservice to this handbook.
5
u/Seerk Feb 01 '17
Wow, I agree with all of his points but the tone of that article is so awful. I hate that he calls the wrong/incomplete responses "Red Flags", as if they were some kind of personality trait and not something that can be learned.
2
u/b4ux1t3 Feb 03 '17
That's my general problem with anyone who talks down to people who know less than they do.
2
u/acemarke Feb 01 '17
Eh, Eric Elliott is known for having extremely strong opinions regarding inheritance and FP, but his articles and resources are pretty good overall. I'm not saying that a new learner would be expected to know about Eric's opinions and reverse-filter things to compensate, just that I wouldn't throw out all of his info as a response. There's still plenty of value in his material.
6
8
u/Sideburnt Jan 31 '17
Damn. I have a front end developer interview next week and half of this is alien to me, I'm brushing up on my HTML5 understanding and JavaScript. I'll pick up on the interview questions and cram hard.
24
u/erm_what_ Jan 31 '17
No one knows everything, most of us learn what we need to for the project we're working on, then whatever interests us when we have some spare time.
I can count on one hand the number of developers I've come across that understand and use ARIA roles for example.
8
u/Sideburnt Jan 31 '17
Thanks, I'm drifting between being cool as a cucumber and freaking out. I appreciate the voice of reason
7
u/commitpushdrink Jan 31 '17 edited Jan 31 '17
function isPalindrome (maybePalindrome) { return maybePalindrome.split('').reverse().join('') === maybePalindrome; }Good luck!
Edit: comments on spelling addressed, thanks for the review
7
-14
u/lulzmachine Jan 31 '17
wtf is an ARIA role? Is that the crap bootstrap puts in their examples, so you have to remove the excessive markup?
16
u/Codeguin Jan 31 '17
As one of a few developers whose sole purpose for a couple of months in 2016 it was to make sure our product was accessible for people:
with low-vision (so high-contrast modes, large fonts, etc)
can only use keyboard input
who are blind (screen reader support)
as well as everyone else and doing my research into how to best accommodate/develop for those users, I started to understand the difficulties accessible users go through and I feel like, as developers, we need to be inclusive to all persons that may use our software.
So, maybe, don't just blow it off as "crap" and "excessive markup" that you think has no purpose. Expand your horizons and learn about what it is. It can/will help you to become a better developer.
2
u/BrentLabasan Jan 31 '17
Thank you for your work. How did you fall into that position?
3
u/Codeguin Feb 01 '17
Oh. My manager at the time had suggested that I take on the task for the team. I didn't actually know a lot about accessibility so I agreed to do it and ran with it learning a lot. Not that I know everything there is about it but I do know more than I did.
6
u/magenta_placenta Jan 31 '17
They're for accessibility within screen readers. Accessible Rich Internet Apps (ARIA roles) help improve the accessibility of dynamic content and UI controls developed with JS (ajax).
2
u/K0d1Lu Jan 31 '17
Could make a huge difference in SEO in few years as semantic and accessibility become more and more important to search engines
3
u/thbt101 Jan 31 '17
Wow! I don't think I've ever learned so much from one book, and I'm only about 15 pages in. Really nice!
2
u/atonaletude Feb 01 '17
Great resource! I feel fascinated by everything that is out there. But at the same time I feel like my head is going to explode with all the stuff out there...
2
u/doraemon-cat Feb 01 '17
One look at the content page and I immediately was reminded of the Hackernoon JavaScript fatigue article.
1
1
u/Hidden__Troll Feb 01 '17
If this is done by front end masters then it's probably really good. Going to give it a read.
1
u/b4ux1t3 Feb 03 '17
I'm kind of confused why "Front-End Engineer" is also considered "Full-Stack JavaScript developer". Front-end implies the opposite of full-stack, at least to me. Is it different because they have to write things that access the back-end?
-9
u/Njy4tekAp91xdr30 Feb 01 '17
And I'll just continue using plain HTML5, JS, CSS3 and a bit of jQuery. I'll even use the new ES6 features when they're supported in Firefox and Chrome. That just gets things done. There's no need for 90% of the guff the JS community is churning out and changing far too often. Imagine trying to build a stable product on that. Reeks of immature junior developers. The foundation will move out from under you every month. You'd need a dedicated team just to keep track of the framework changes. No thanks. I'd rather have stability.
3
Feb 01 '17
That's why you test package upgrades heavily before you make changes to production.
0
u/Njy4tekAp91xdr30 Feb 02 '17
That doesn't solve the endless churn and ton of upgrading and testing every month at all.
3
Feb 03 '17
So don't upgrade your dependencies every month?
0
u/Njy4tekAp91xdr30 Feb 04 '17
Let them go out of date for a few months and there might be large breaking changes and even more work.
88
u/Crashthatch Jan 31 '17
I particularly liked the Recap of Front-end Development in 2016:
The year of the UI component, and tree of UI components, for building complex UI's.
No longer mainstream development blasphemy: components being constructed from a single file, potentially contain HTML, CSS, and JS, IN ONE FILE!
React, Redux, Webpack, ECMAScript 2015 (aka ES6), and Babel gain massive adoption. These solutions rise to the top of all the polls as the most used tech.
Developers realized, in most cases, HTML 5 hybrid mobile development via webviews doesn't provide enough wins when building native apps.
React Native and NativeScript start to replace mobile HTML5 hybrid webview development.
Many abandon Gulp for NPM scripts, but Gulp remains popular.
SASS remains a popular tool, while PostCSS (+ CSSNext) gains ground.
Linting/Hinting HTML, CSS, and JavaScript is a thing most developers do (ESlint replaces JShint & JSCS merges into ESLint).
A trend of developers abandon Sublime and Atom for Visual Studio Code begins.
jQuery remains, but usage/interest is declining. jQuery 3 was released, much like a tree falling in a forest that nobody hears.
Vue.js continues to gain converts. Deservingly so!
JavaScript functional programming & patterns get a lot of attention.
Offline development & Progressive Web Apps go mainstream.
Microsoft shows up and contributes.
Developing native applications for windows, OSX, and linux using things like NW.js and
Electron via web technologies becomes a thing.
Angular 2 (in the future aka "Angular") gets off the pot and most realize it will never be as mainstream as Angular 1.
JavaScript broadly remains at the center of software technologies.
More developers start caring about tooling (e.g. automation) and testing.
Static site generators are taken seriously.
CSS Grid excitement grows and the future looks bright.
NPM gets some competition from YARN.
The next evolution of React-like solutions shows up via Preact, Deku, Rax, and inferno showcasing evolution without much API change.
Mostly people learn to not only accept JSX they can't imagine not using it.
A workable CSS module pattern (CSS encapsulation) is actualized and used, thus CSS in JS becomes a viable solution for many.
More people turning to UI functional/integration testing including concepts like visual
CSS & RWD regression testing.
The days of battling inconsistent browser API's are almost behind us due to a massive decline in usage and development for older versions of IE.
Most everyone realized they will have to have a multi-device strategy plan when development for the web
More developer, from other languages, continue to flood the JavaScript space bringing with them things like type checking and an obsession with class syntax and OOP concepts.
Front-end devs are introduced to Hot Module replacement techniques and time travel debugging.
More waiting for a native JavaScript browser module loader.
Enforcing CSS and JavaScript style conventions becomes more important (considering
ES3 to ES6 code and CSS pre-processors syntactical variations)
A small but noticeable number of developers are starting to chose Elm over JavaScript.
TypeScript gets some serious use and fanboys.
http://aurelia.io/ becomes the smart choice for enterprise developers (i.e. support!).
Webpack gets its act together and solidifies is position over the superior JSPM solution.
HTTPS, yeah, we're serious about that.
BASH on windows happen.
The notifications API gets used and abused for chrome users, but only after you give it permission.
Firebug officially dead.
CSS 20 years young in 2016.
Immutability concepts run rapid.
And predictions for 2017:
Web Assembly, might just peak.
import might just be usable in <scripts></scripts>
Universal JavaScript solutions will continue to rise that pay homage/respect to the days of server delivered front-ends (i.e. html to the client).
Reactive programming continues to thrive in the JavaScript scene. (see MobX and RxJS).
React, more so the concept, will dominate. React itself will be completely re-written (see
React Fiber) or evolve (see Inferno).
Angular found SEMVER so Angular 3, 4 (even 5) is on the roadmap for 2017.
A return to simple websites may happen, web 1.0 retro, but with the help of 2017 tools (i.e. static site generation)
RESTful JSON APIs will get more competition (see GraphQL)
Could be a banner year for Vue.js.
More devs will abandon traditional CMS solutions for static site generators & API CMStools.
More people will move from Sass to PostCSS + cssnext.
Lots more HTTP2 and HTTPS.
Web components will continue to lurk and wait for significant traction by developers that might never come to be.
The no framework, framework, faction will gain momentum (see Svelte).
JavaScript will settle, and hopefully, CSS will erupt and everyone will cry fatigue until it settles.
Hatred for apps store will grow, while the open web has no memory of wrong doing.
Redux will continue to get stiff competition (see mobx).
YARN will win more users.
The idea of “front-end apps”, “Thick Client apps”, “Static apps”, “No Backend app”, “SPA's”, “Front-end driven app” might get boiled down to the term/concept called "JAMStack".