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

51–60 of 244 posts

Re: Guide to JavaScript Frameworks

#51

Post by B4TMAN »

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…

I am in the same boat. I tried learning js. I have a background in CS so its primitive part don't bother me much. Its just that after those primitive parts to see something in action I will need to go through such a steep learning curve that I end of abandoning the whole process. I only know basic js syntax so that I can do thing that I was able to do in C?/C++/Java. How do I make it more useful? I didn't learn this extra language just do the things which I could already do in other languages.

Re: Guide to JavaScript Frameworks

#52

Post by ricardobeat »

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…

Forget about Babel / Webpack. Pick one of the simple ones that can be used without a build process: choo, Hyperapp, Preact. Read the source. The change in paradigm is the main takeaway.

Re: Guide to JavaScript Frameworks

#53

Post by dclowd9901 »

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…

It discourages us full time FEs too. Webpack and a full transpile pipeline is still relatively new to JavaScript but it seems like we’re starting to land on some assumptions (and thus making this a more turnkey process)

ES6

Route based lazy loading

Some sort of typing (TypeScript or FlowType)

CSSModules

React with JSX

Redux

The reason it’s been so difficult is because we’ve had a sort of Wild West mentality where we want to throw everything at the wall and see what sticks. Hence the extreme configurability of Webpack. But this seems to be the preferred configuration. I speculate we’ll see a more turnkey build pipeline in the next year rise.

Re: Guide to JavaScript Frameworks

#54

Post by yesimahuman »

Shameless plug, but I think Stencil should be on this list: https://github.com/ionic-team/stencil

It's going to be running behind all Ionic apps in the near future, that's hundreds of thousands of apps in the app stores and the web.

Also, SkateJS is missing. Both Stencil and Skate are Web Component libraries, "frameworks" insofar as React is a framework.

Re: Guide to JavaScript Frameworks

#55

Post by B4TMAN »

dclowd9901 wrote: post #53
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…

It discourages us full time FEs too. Webpack and a full transpile pipeline is still relatively new to JavaScript but it seems like we’re starting to land on some assumptions (and thus making this a more turnkey process) ES6 Route based lazy loading Some sort of typing (TypeScript or FlowType) CSSModules React with JSX Redux The reason it’s been so difficult is because we’ve had a sort of Wild West mentality where we…

Can you elaborate on the things that you have enumerated?

Re: Guide to JavaScript Frameworks

#56

Post by vanillaboy »

Klathmon wrote: post #23
_fol8 wrote: post #7

Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…

Honestly I don't think Vue is better than React, or React better than Vue. They are just different, and that's where a lot of the arguments come from. For me, Vue is such a monumentally large step backwards. I loved React because there are no templates, there is no 2-way binding, you don't have the vuex style state handling. Using Vue is an exercise in frustration for me, dealing with all of the templating headaches…

To me React is superior for a very simple reason.

There is a huge deficit of intermediate-advanced Vue tutorials compared to React. There are like 30 advanced-level tutorials on Egghead on React and like, what 3-4 advanced Vue tutorials (Nuxt, Nuxt and using Angular-like decorators to write proper classes instead of the 'it just works' vanilla boilerplate)?

Learning the ropes of Vue is easy. It's a go-to framework of the Laravel crowd for this very reason - you don't need to know Javascript much if at all, just learn some basic syntax and you're good to go for some basic virtual DOM magic.

Re: Guide to JavaScript Frameworks

#57

Post by adjkant »

3pt14159 wrote: post #50

The rumours of Ember's demise are greatly exaggerated. I have yet to hear of people making the same amount in any other framework. Seniors are making $200k to $500k in remote positions (the people I know live in Toronto, but they could be anywhere). It is hard to learn, and I'm far from an expert, but the highest I've heard another JS developer who knew both Angular and React completely and he was responsible for mig…

I'd point out that often rare and often unused skills get higher pay due to simple supply and demand. I've heard similar salary ranges for Assembly programmers for example.

Angular and React are widely used, and there are many people out there that know them. No need to pay a ton.

> The problem with Ember is the learning curve because it doesn't usually let you take shortcuts.

I'm guessing that's precisely one of the main why it's not used widely. Why train an entire dev team on it only to have half leave in a year and have to be constantly retraining on a language with a large learning curve?

Re: Guide to JavaScript Frameworks

#59

Post by yesimahuman »

3pt14159 wrote: post #50

The rumours of Ember's demise are greatly exaggerated. I have yet to hear of people making the same amount in any other framework. Seniors are making $200k to $500k in remote positions (the people I know live in Toronto, but they could be anywhere). It is hard to learn, and I'm far from an expert, but the highest I've heard another JS developer who knew both Angular and React completely and he was responsible for mig…

The Framework wars are overblown, and they've become profitable to perpetuate for clicks and views. I know plenty of people using Ember today and loving it. Same with Angular. React is popular but it's hardly the only game in town.

Re: Guide to JavaScript Frameworks

#60

Post by Tehnix »

Starting from fresh, I would honestly recommend PureScript or Elm (and eventually Haskell/GHCJS when that moves to WASM).

The benefit you get from the amazing type systems and compilers these have, is worth so much when it comes to refactoring, and later on boarding new people, giving them the confidence to make changes thanks to the help of the compilers.

Post reply on HN