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

151–160 of 244 posts

Re: Guide to JavaScript Frameworks

#151

Post by rmrfrmrf »

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

As someone who had to use AngularJS for a while, just wait until those template directives get replaced in future versions to support random-use-case-17483 and force you to refactor a bunch of template code for literally no tangible gain. Then you’ll understand why using native JS to generate elements makes more sense.

Re: Guide to JavaScript Frameworks

#152

Post by rmrfrmrf »

dandersh wrote: post #46

Wow, Dojo is still alive and kicking! I'm going to have to find some time to take it for a spin. I really like the idea of framework that looks to address a few needs, making framework selection easier and less reliant on "Oh Framework X is popular now? Let's use that and hire a bunch of devs for it..." While Dojo is there, I'm surprised ExtJS is not. I haven't worked with it directly for quite a few years but I know…

Dojo is literally Satan. Stay far away!

Re: Guide to JavaScript Frameworks

#153

Post by szines »

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…

Actually, learning Ember.js is quite simple, because of Ember CLI, which was the pioneer and inspired Angular CLI and Create React App. Try this tutorial and you will be an employable Ember expert in a few days: http://www.yoember.com

Re: Guide to JavaScript Frameworks

#154

Post by szines »

ralmidani wrote: post #139

I am trying to transition from Ember to React, but calling Ember "historically significant" is odd given adoption by big name companies (including Apple and LinkedIn) and very active development (3.0 should be out in a few weeks).

You are totally right... Ember is adopted and actively used by more and more places, people loves it and very easy to work with. Ember evolve a lot all the time, definitely one of the best choice nowadays.

Re: Guide to JavaScript Frameworks

#156

Post by LeoNatan25 »

debaserab2 wrote: post #123
LeoNatan25 wrote: post #90

Earlier quoted context omitted.

When you build a browser insider a browser (aka React), it’s impure.

So JavaScript dom manipulations are pure? but one specific technique of dom manipulations are not?

It's not specifically the DOM modification but the way those frameworks are designed. With React you have hundreds of dependencies, which have hundreds of dependencies. You lost me right there.

Re: Guide to JavaScript Frameworks

#157

Post by onion2k »

expertentipp wrote: post #133
zdragnar wrote: post #132

Earlier quoted context omitted.

Funny, I've worked with multiple companies and their lawyers who were very serious about license compliance and what not. It took all of fifteen minutes to prepare a spreadsheet of our licenses (planned, anyway). Not a complaint from any of them, other than an "oh, that's more than I'm used to seeing." The one sticking point was webpack 1; they had some dependencies with unlicensed dependencies. Fortunately, we were…

Fair enough. Now imagine that your product or service is gaining popularity on the market where Google or Facebook consider you a competition.

The idea that you should consider "what to do if your company grows to be a competitor to Google" in your technology decisions is quite frankly some of the worst bikeshedding I've ever seen. That question shouldn't even enter in to the process at the start.

If that happens, and it probably won't, but if it does you will have a team capable of dealing with the issue by then.

Re: Guide to JavaScript Frameworks

#158

Post by sizzle »

yomly wrote: post #101
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 wan…

Thanks for articulating this in an intuitive manner for us non devs.

Re: Guide to JavaScript Frameworks

#159

Post by chuckdries »

http-teapot wrote: post #105
chuckdries wrote: post #22

Earlier quoted context omitted.

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

I don't actually use any of this, so I'm not intimately familiar, but I found a promising looking framework and a help article on redux itself.

https://github.com/zeit/next.js/ https://redux.js.org/docs/recipes/ServerRendering.html

Re: Guide to JavaScript Frameworks

#160

Post by sasmithjr »

CharlesW wrote: post #134
spikej wrote: post #113

Earlier quoted context omitted.

Add to that tooling compatibility issues with TypeScript & Vue

Mind elaborating? As of late, Vue's TypeScript support seems pretty nice.[1] [1] https://vuejs.org/v2/guide/typescript.html

Unless I'm mistaken, it only really works well within a component. You don't get prop type checking in the component hierarchy.

Also, Vuex is very string-based, so you don't get payload or return type checking when you use Vuex. There are additional libraries that look to help this, but it's still an issue.

I could be wrong about any of this, but those are currently the issues I'm running in to.

Post reply on HN