Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Guide to JavaScript Frameworks

javascriptreport.com

Post reply on HN
Print view View original

101–110 of 244 posts

Re: Guide to JavaScript Frameworks

#101

Post by yomly »

joaodlf wrote: post #44

I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…

From what I see, we are moving away from a heavy server which does the heavy lifting to thin server layers that just send data and feature rich UIs that process the data. This is possibly because the browser has become a widespread means of distributing general software.

As a result, the domain of "backend" engineering has bled into the frontend and thus frontend engineering has gotten more complex.

If you purely want to learn React in a way that allows you to do some light modification of an existing architecture then something like create-react-app or some browser codepens will be the best way to get involved with the library.

Otherwise, if you want to understand React from a more fundamental sense, going away and doing some backend courses or learning some basic CS and/or FP architecture may serve you well in understanding the paradigms that inform React's design. As a bonus, these skills will never be useless.

As for JS tooling, it's not ideal and is definitely a lot to learn all at once. Your best bet is to abstract over as much as possible and learn only what you need to when you have to. Though, again, the skill of picking up and using new tools is a valuable one in this line of work.

Re: Guide to JavaScript Frameworks

#102

Post by paul7986 »

qaq wrote: post #77
joaodlf wrote: post #44

I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…

Considering there is easily (in US) 60-80K+/year difference between doing HTML + CSS + JS (mostly via jQuery) and say React. Spending 1 month to learn webpack + React looks like fairly sound investment of time.

There are no longer any HTML, CSS, JS jobs posting without the fact of needing to know one or multiple JS frameworks.

If you are currently working and using no frameworks in your current job you better learn them before looking for your next gig. Because if you don't you are no longer relevant .. .speaking from current job hunting experience and 30 interviews yet no offers.

Re: Guide to JavaScript Frameworks

#103

Post by ptr_void »

joaodlf wrote: post #44

I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…

If you want to learn Vue, here's a great 3 hour starter that doesn't use any fancy setup - just specifically about Vue:

1. https://www.youtube.com/watch?v=utJGnK9D_UQ

2. https://www.youtube.com/watch?v=ulHt78ad890

3. https://www.youtube.com/watch?v=ez0y_XKtEIc

Re: Guide to JavaScript Frameworks

#104

Post by expertentipp »

mhermher wrote: post #93
joaodlf wrote: post #44

I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…

Same. Recently I had to do some web work and it is so daunting. Any tutorial for a given technology asks you to use a bunch of other tooling dependency that you don't understand. It's just mixed up dependencies everywhere even for little example projects. Something like create-react-app that is supposed to help you learn react. Set it up and just look at node_modules. Just a shit ton of dependencies and you have no i…

> Set it up and just look at node_modules. Just a shit ton of dependencies and you have no idea what any of them do. All this sort of scaffolding set up that you're supposed to ignore.

Yeah, good luck going through legal/license compliance audit in any serious company doing software.

Re: Guide to JavaScript Frameworks

#105

Post by http-teapot »

chuckdries wrote: post #22
GoToRO wrote: post #12

SEO friendly? Server-side rendering support?

Vue and react have SSR frameworks, as I'm sure many others do as well. I'm not sure if it's a big enough feature to include in the tags this site uses. ¯\_(ツ)_/¯

For React, could you link a few? I am genuinely interested

Re: Guide to JavaScript Frameworks

#106

Post by Fifer82 »

JohnMunsch wrote: post #40

"Polymer is a Google-backed libary focused on Web Components, a proposed group of technologies that are currently not well-supported in browsers." Ha ha ha ha ha ha ha. Wow.

I gave up on Polymer. I can't really explain it well but nothing worked as you expected it to. v2 was just hacked v1 (hybrid?) and so trying to actually figure out how to use v2 was impossible since every major custom element was hybrid. The documentation was bad, and the things you might want to use were somewhat depreciated, but you had to figure that out on your own. Then the standard glacial pace of development means that v3 was announced over half a year ago and as far as I can see, nothing has happened.

Re: Guide to JavaScript Frameworks

#107

Post by expertentipp »

Klathmon wrote: post #15
paul7986 wrote: post #3

Did you learn Jan2018.js yet? If not your behind and your skills are outdated.....

I know people love to shit on JS for being blisteringly fast, but does it really apply here? All 3 of "the big 3" are over 4 years old, making all of them older than windows 10... And of the notable category: Aurelia: around 2014 Elm: around 2013 Inferno: around 2015 Polymer: 2014 Preact: 2016 ReasonML: 2016 Svelte: late 2016 So most a few years old. Yes, it's faster than older technology stacks, because the web is s…

They appear and disappear as fast as startups and projects which use them:)

Re: Guide to JavaScript Frameworks

#108

Post by expertentipp »

GoToRO wrote: post #12

SEO friendly? Server-side rendering support?

> SEO friendly? Server-side rendering support?

No no no, you think wrong - like an unhirable dinosaur. Sometimes I just chuckle when I see yet another SEO growth-hacking startup doing full client-side rendering in React/Angular.

Re: Guide to JavaScript Frameworks

#109

Post by colordrops »

joaodlf wrote: post #44

I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…

This is an opinion, so don't take it as fact, but JS frameworks are a mistake. It's better to take the Unix philosophy and build things up from single components that do their one job well, and focus on standards. So an example would be to use Web Components rather than React. React is amazing but it has a limited lifespan (though that lifespan could be long), whereas Web Components, while not as feature rich, are a web standard. The gaps between React and Web Components can be filled in by various libraries, such as Lit HTML. For state management you could just use plain javascript or dip into a particular library like Redux or MobX if your needs get complex.

In any case, once something no longer fits your needs, you can change it out with something else, which is difficult if you use something like Angular or React or Vue.

Re: Guide to JavaScript Frameworks

#110

Post by electrotype »

I'm still using Jquery and some of the millions js libraries available only when you do not bind yourself to a SPA framework taking control of the DOM. And it work pretty well I must say!

My opinion is that for 80% of the websites out there, a SPA framework is not only overkill, but is also a bad choice. Your website is probably not Gmail or Facebook. Server side rendering is perfectly fine.

We should start a competition where any framework/no-framework could be used to develop a project and judge the winners using metrics such as : time it took to develop it, compatibility, accessibility, fun to interact with.

Post reply on HN