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

React/JavaScript fatigue

medium.com

Post reply on HN
Print view View original

21–30 of 187 posts

Re: React/JavaScript fatigue

#21

Post by qaq »

thirdreplicator wrote: post #6

I was thinking to put React.js in my adopt circle, but I spent a couple of days setting up the Node.js gulp-vinyl-browserify-babelify nonsense, and it really is a witch's brew of configuration hocus pocus. Its compelling to know that React is backed by Facebook, but React is simply verbose and comes with too much stuff packed into one package. Whats the alternative? Thanks to hacker news i bookmarked vuejs.org and fi…

It all depends. React as of right now is the only viable option that has decent server side rendering for 80%+ of web apps it's a must for SEO, FB integration etc. Until Angular 2.0 ships and Ember get's fastboot completed there is no other major viable option.

Re: React/JavaScript fatigue

#22

Post by chowes »

People jumped the Angular / Ember ship for React because those frameworks were too complex. Then they realized they needed additional features. Now there's a push to unify these features into a framework...

You have to put your complexity somewhere.

Re: React/JavaScript fatigue

#23

Post by MatthewPhillips »

qaq wrote: post #21
thirdreplicator wrote: post #6

I was thinking to put React.js in my adopt circle, but I spent a couple of days setting up the Node.js gulp-vinyl-browserify-babelify nonsense, and it really is a witch's brew of configuration hocus pocus. Its compelling to know that React is backed by Facebook, but React is simply verbose and comes with too much stuff packed into one package. Whats the alternative? Thanks to hacker news i bookmarked vuejs.org and fi…

It all depends. React as of right now is the only viable option that has decent server side rendering for 80%+ of web apps it's a must for SEO, FB integration etc. Until Angular 2.0 ships and Ember get's fastboot completed there is no other major viable option.

DoneJS as well. It includes Web components, a browser module loader, and has the most complete server side rendering of any framework. https://www.google.com/url?sa=t&source=web&rct=j&url=http://...

http://donejs.com

Re: React/JavaScript fatigue

#24

Post by joshontheweb »

qaq wrote: post #21
thirdreplicator wrote: post #6

I was thinking to put React.js in my adopt circle, but I spent a couple of days setting up the Node.js gulp-vinyl-browserify-babelify nonsense, and it really is a witch's brew of configuration hocus pocus. Its compelling to know that React is backed by Facebook, but React is simply verbose and comes with too much stuff packed into one package. Whats the alternative? Thanks to hacker news i bookmarked vuejs.org and fi…

It all depends. React as of right now is the only viable option that has decent server side rendering for 80%+ of web apps it's a must for SEO, FB integration etc. Until Angular 2.0 ships and Ember get's fastboot completed there is no other major viable option.

Im don't know a lot about SEO but afaik Google crawls javascript pages. Do you still take an SEO hit in that case?

Re: React/JavaScript fatigue

#25

Post by zachrose »

I have a suggestion to this, but I don't know how to get it out there. I can't build a library because the point is to not depend on libraries.

My suggestion is that if your going to build an application in the browser, your project needs an architecture that will last beyond today's libraries and tooling. You want to recognize what's unique about your app and express those parts without touching the DOM or network, even if they seem trivial now.

My particular favorite way to do that is using an event bus to create a catalog of custom/domain-specific events, with views emitting operation- or command-like events and internal models emitting new states. This is basically the important part of Flux without the special concepts (stores, dispatcher) that you may be fine without, and is already available in jQuery, Backbone, node's EventEmitter, and many other libraries out there.

React and immutability and the rest of Flux are all very reasonable next steps if somehow you come to need them, but you are likely not spreading your UI development across hundreds of engineers. Unnecessary new stuff is just going to steer your conversations towards libraries and away from your domain.

Re: React/JavaScript fatigue

#26

Post by pavel_lishin »

bradhe wrote: post #10
orf wrote: post #8

Earlier quoted context omitted.

> (I say "my" because I'm sure my stack is different than yours in one way or another) I think that's the problem. For a beginner what is their stack? It's a wild west of 'this months hip library' and for a beginner it's unintelligible.

> It's a wild west of 'this months hip library' and for a beginner it's unintelligible. What's wrong with the "just pick one" approach??

Can you point me to one that'll help me actually get something workable up and running? You say you have one; I assume it's something you've put together over the time you've worked with React, and not something you just pull in from someone else's repo.

Re: React/JavaScript fatigue

#27

Post by qaq »

MatthewPhillips wrote: post #23
qaq wrote: post #21

Earlier quoted context omitted.

It all depends. React as of right now is the only viable option that has decent server side rendering for 80%+ of web apps it's a must for SEO, FB integration etc. Until Angular 2.0 ships and Ember get's fastboot completed there is no other major viable option.

DoneJS as well. It includes Web components, a browser module loader, and has the most complete server side rendering of any framework. https://www.google.com/url?sa=t&source=web&rct=j&url=http://... http://donejs.com

by "major" I meant something that has recognizable market share.

Re: React/JavaScript fatigue

#28

Post by OSButler »

chowes wrote: post #22

People jumped the Angular / Ember ship for React because those frameworks were too complex. Then they realized they needed additional features. Now there's a push to unify these features into a framework... You have to put your complexity somewhere.

I believe in Angular's case the changes from 1.x to the 2.x branch didn't help much either.

Re: React/JavaScript fatigue

#29

Post by snaky »

pbhowmic wrote: post #9

This is something I have observed about every language/framework front end combo I have ever used and I have done it long enough to go all the way back to Qt 3 and even before. There is no terse way to describe a UI. Period. C++ or Java I understand they are typed languages with an avowed aim of giving the programmer fine grained control over the program. Objective C may have become popular more recently but it too i…

> There is no terse way to describe a UI

Did you ever seen Tk?

Re: React/JavaScript fatigue

#30

Post by scope »

there's NO fatigue, it all depends on YOU & how you're willing to LEARN continuously

Let's put it like this, there are many ways to build a house, but you don't see a builder without at least hammer & nails right?

One day you see another builder with a nail gun, do you ask the builder about the machine or do you keep building a house using JUST hammer & nails?

After sometime, you see another builder building a house without using nails at all

After sometime, you see another builder 3D printing a house...

Post reply on HN