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

React Makes You Sad?

github.com

Post reply on HN
Print view View original

101–110 of 211 posts

Re: React Makes You Sad?

#101

Post by grumblestumble »

danabramov wrote: post #63
uptownJimmy wrote: post #46

Earlier quoted context omitted.

I lol'd the minute I saw the flow chart. It's absurd. Helpful and well-intentioned, but absurd.

Thank you for the criticism! Would you like to help me understand its flaws better so I can improve in the future?

3 things:

1. Much of it reads as"are you taking this approach? yes? don't take this approach. no? take this approach."

2. There are also a couple of flowchart errors ("are you working on a production app" appears twice for no reason).

3. The main reason React makes me sad is the need for excruciating flowcharts like this.

As a result, the entire thing comes across as self-parody. For context, I'm a developer who works on a large enterprise app with a full build toolchain (npm, babel, webpack, sass, etc ad infinitum).

Re: React Makes You Sad?

#103

Post by hahamrfunnyguy »

It makes me sad looking at apps made with React. I am currently using Knockout.js and Router.js which is working out very well. I like that your code is concerned with maintaining the state of the VM, not rendering the view.

What is gained by building an app in React, and are there certain scenarios where it really shines?

Re: React Makes You Sad?

#104

Post by vdnkh »

kawera wrote: post #100
vdnkh wrote: post #96

Everyone complaining about how React is just a trend is missing the point of React. It's not some revolutionary flash-in-the-pan technology based on a mystical black box, it's an aggregation of best practices that everyone (including yourself) has been clamoring to have implemented for years. Web components? Check. Object.Observer? Check. Virtual DOM? Check.

Why not Web components directly? (genuinely interested, soon I'll have to chose one way or another for a new project)

They're still experimental. React handles a lot of the legwork towards getting proper web components today.

Re: React Makes You Sad?

#105

Post by novaleaf »

olalonde wrote: post #93
novaleaf wrote: post #79

nice flowchart, i know the point of redux but man the boilerplate needed to create a component sucks: class _MyActualComponent extends React.Component { //my component's implementation goes here. } /** type for casting (so consumers know the props they are required to pass */ class IMyComponentVisibleType extends React.Component { }; /** instrument my component with redux */ export var MyComponent = ReactRedux.connec…

What language is this? I'm using es6 and most of my components just look like this: export default ({ name }) => ( hello {name} ) With Redux connect: const SomeComponent = ({ name }) => ( hello {name} ) export default connect(s => ({ name: s.user.name }))(SomeComponent)

The code I wrote is Typescript (ES6 with typings), I am using the ES6 class style React Components.

you are using the lambda style components which is fine for simple stuff but for heavier stuff the class-style components are needed. also you are not passing the reducer actions, etc.

Still, what you are showing in your simple example looks pretty similar to the amount of boilerplate I'm seeing with Redux, so it looks like there's not really an easier way.

Re: React Makes You Sad?

#106

Post by plexicle »

I have tried to get in to React all week. The technology is easy, but it's Webpack that I'm having trouble enjoying.

All I want is are two simple configs. A dev one with a server/hot loader, and a prod one that concats/minifies. ES2015. That's it. That just doesn't exist out there. It's either no decent production bundler, or it's like 15 files and 900 lines of configuration that seem completely overkill.

I don't know. I don't have time to learn how the tooling works, but I also don't want a bunch of magic. Angular 2 is looking really good right now even with the (still very incomplete) angular-cli tool.

Dang. I just want my simple gulpfile back.

Re: React Makes You Sad?

#107

Post by jnbiche »

heavenlyhash wrote: post #80
bikamonki wrote: post #52

Earlier quoted context omitted.

Project seems abandoned, no?

Other correct comments about a quite active 'next' branch aside... The latest commit on master is Nov 12, 2015 . That's not even half a year ago . The stable shelf life of software worth mentioning is longer than that, don't you think?

> That's not even half a year ago. The stable shelf life of software worth mentioning is longer than that, don't you think?

I can see that you haven't spent much time in the JavaScript ecosystem. And forget latest commit, if a JS project wasn't started in the last half year, it's already getting long in the tooth. After a half year, trendy devs will already start moving on to the next great framework and package manager.

Re: React Makes You Sad?

#108

Post by joslin01 »

kruhft wrote: post #90
joslin01 wrote: post #85

I don't know what's worse. A poorly-worded expression of someone's experience with React, or the no-info-or-even-attempt-to-understand judgment from you. Oh man, you're a guy who does a fair amount of React work and tries to pay attention to weird arguments against it? Let me immediately downvote that guy and upvote you! What's so weird about someone not enjoying the rigidity React offers and realizing that Facebook…

Thanks.

No problem. Don't worry about that guy or the downvotes. He's smart, but gets off on putting people down with snide one liners.

Re: React Makes You Sad?

#109

Post by christopher_ »

It's an interesting topic since React and the React ecosystem is great but it's so fragmented that it's difficult to get started with. What's the trade off between modularity in tools and productivity?

Re: React Makes You Sad?

#110

Post by jim-greer »

sombremesa wrote: post #71
marcusr wrote: post #36

As a C and then a Ruby on Rails programmer, I never thought I would see the day that my main programming language was Javascript. But I find React such an enabling technology that I made the effort to learn Javascript properly, and am glad that I did. React itself is allowing me to write web applications faster and with less bugs, primarily because of the unidirectional information flow, but also because of the way i…

I just want to point out that there is no mandate to use a framework in JavaScript. While I'm not familiar with React and I agree that it probably helps developers structure their apps, there is no need to use a framework just to have a component/modular architecture. One of my favorite examples of clean modular JS that does not depend on a framework is Mozilla's browserquest: https://github.com/mozilla/BrowserQuest/…

That doesn't work if you're trying to build native mobile apps.
Post reply on HN