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

71–80 of 244 posts

Re: Guide to JavaScript Frameworks

#71

Post by wwweston »

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…

> Seniors are making $200k to $500k in remote positions

Finally, a framework feature that's truly compelling. :)

Re: Guide to JavaScript Frameworks

#72

Post by ggregoire »

_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…

You just listed all the reasons why people moved from Angular 1 to React.

Re: Guide to JavaScript Frameworks

#73

Post by [deleted] »

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…

[deleted]

Re: Guide to JavaScript Frameworks

#74

Post by mlsarecmg »

hungerstrike wrote: post #69
mlsarecmg wrote: post #42

Earlier quoted context omitted.

The points you've listed are the very reasons why i would prefer React actually ... - JSX fixed all the templating issues from 10 years ago, i see no reason to go back to dependency injection, scope loss, arbitrary code-in-html expression and a semi-javascript accent - Presentational view logic belongs to the controller while business logic is elegantly abstracted in React: view=fn(state). There's no point in ripping…

These are exactly the same reasons that I think React is the best. Vue looks like it's going backwards compared to React. Furthermore, you get native mobile apps for free with React Native. Also, React has a much, much bigger community and bigger companies supporting it.

Not just mobile apps:

Windows: https://github.com/Microsoft/react-native-windows

Macos: https://github.com/ptmt/react-native-macos

Linux (Qt): https://github.com/status-im/react-native-desktop

AR: https://github.com/HippoAR/react-native-arkit

VR: https://facebook.github.io/react-vr/

TV: https://github.com/react-tv/react-tv

Shell consoles: https://github.com/Yomguithereal/react-blessed

Word: https://github.com/nitin42/redocx

Pdf: https://github.com/diegomura/react-pdf

3d: https://github.com/Izzimach/react-three

Sketchapp: http://airbnb.io/react-sketchapp/

Keynote: https://twitter.com/nishb1/status/913744410537537536

Hardware: https://github.com/iamdustan/react-hardware

Samplers: https://twitter.com/GabeRicard/status/911989894267973633

And so on ...

Finally being able to transfer knowledge and code, and due to the generic nature of React in some cases even everyday eco-system packages can be applied. For instance: https://github.com/gaearon/react-blessed-hot-motion (native console app using plain react-motion to move stuff around).

Re: Guide to JavaScript Frameworks

#75

Post by djsumdog »

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 recently started to build an electron application using the electron-vue boilerplate. Dear god, there is a ton of garbage in that boiler plate! Not to mention boilerplate is such a code smell.

With so much base stuff baked into that base, it makes it difficult to add new components and really understand what's going on.

Still I'm glad my first step into Vue is through an electron app so I'm not dealing with figuring out browser comparability. Still it makes me sad we don't have very many cross-platform desktop app tools, that we have to use electron and package a 100MB web browser and VM as part of our app.

Slack, Discord, etc are all at least 90MB. That's kinda messed up.

Re: Guide to JavaScript Frameworks

#76

Post by tbranyen »

HatchedLake721 wrote: post #66
adjkant wrote: post #57

Earlier quoted context omitted.

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…

It’s not a language, it’s a framework. You can take any experienced JS developer and make them proficient in either Ember or any framework mentioned in the article within days. People overexaggerate how difficult each framework is. They’re all front end frameworks made to do one job. Yes, each of them have their own nuances, but nothing that cannot be understood spending few days coding, reading docs and speaking wit…

Completely untrue. I was at Bocoup and we wanted to standardize on Ember. It took weeks to get devs doing the basics in a large app. Ember isn't gone because its misunderstood. Its gone because we can build the same apps using more suitable libs/frameworks, in a fraction of the time, with less code, less magic, and less upgrade burden. Ember sucked at upgrades, even though they tried to make it better.

Re: Guide to JavaScript Frameworks

#77

Post by qaq »

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.

Re: Guide to JavaScript Frameworks

#78

Post by phillipcarter »

> What is less apparent is that Vue has had roughly double the growth rate over the past year compared to Angular.

Given that you cannot see its growth over the past year in in the chart this guide shows, some might say it's "not apparent at all".

Re: Guide to JavaScript Frameworks

#80

Post by djsumdog »

It doesn't mention http://vanilla-js.com/

:-P

I know it's just a joke, but maybe there should be a section about not using frameworks at all? I'm also curious about the weight of these frameworks. Once you minify and treeshake everything, what's the minimum you can get down to in order to deliver an app?

Also, do any of these frameworks have a way to degrade for people without Javascript enabled? From what I understand, the only way to do this seems to involve some server-side rendering (and it looks like JS is still required).

I'm also really curious how heavy React/Vue/etc are compared to the original gmail implementation back in 2004 (only of the oldest major javascript/ajax applications that minimized page refreshes).

Post reply on HN