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

171–180 of 211 posts

Re: React Makes You Sad?

#171

Post by danneu »

grumblestumble wrote: post #101
danabramov wrote: post #63

Earlier quoted context omitted.

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

If you work with such a large build chain, how did you not realize that the flowchart is really about tooling complexity in the javascript ecosystem, in general?

Also, the "are you working on a production app?" has two nodes so that it can model the fork into {yes bundle, no bundle}, common in flowcharts.

Re: React Makes You Sad?

#172

Post by et1337 »

tiglionabbit wrote: post #137
et1337 wrote: post #30

This reminds me of that Netflix talk on React [1]. In it, the guy first praises React to the heavens, then spends the rest of the session explaining all the ways they had to disable and work around React to get what they wanted with decent performance. It seemed to me like their use case could have been done with jQuery in a few hundred lines. Maybe I missed something. [1] https://www.youtube.com/watch?v=g01dGsKbXOk

He praises React because it makes it easy to change the UI design at any time in response to new requests from the designers. The hard parts he talks about are animations, pre-loading, and virtual rendering, which require some higher level orchestration to get right in any framework. You have to have some component keeping track of this stuff. They mentioned that they had to extend the standard transition component t…

> He praises React because it makes it easy to change the UI design at any time in response to new requests from the designers.

Does it though? I suspect their system is fairly brittle after all that "higher level orchestration".

I keep seeing this pattern repeat in different software disciplines. Unity is the same way: fantastic for prototyping, but often more painful in the long run.

It reminds me of a wise saying (can't remember the source) to the effect of this:

Javascript library user, day 1: "So expressive! So elegant! So easy!" Day 300: "Kill me now."

C++ library user, day 1: "How can anyone live this way?" Day 300: "Whoever wrote this was actually pretty smart."

Re: React Makes You Sad?

#173

Post by sushid »

janpieterz wrote: post #153
joelcollinsdc wrote: post #132

Earlier quoted context omitted.

maybe i'm just typing too fast. I tried "the best marigold" (for the best marigold hotel). I watched the i in marigold disappear from the search box. Deleting the string (by holding down the delete key, the X works just fine) takes forever as well. I'm using chrome if it matters.

Just tested it and didn't find it super bad, but I am honestly (negatively) surprised. It does indeed lag quite a bit and feels very unnatural. Chrome here as well. I use React quite a bit myself and haven't experienced this in my own apps. Odd! There's also a slightly annoying flicker when you type the last bit and it keeps returning the same movies.

The slow text input problem is probably because they're updating their redux or flux store on every keypress.

Re: React Makes You Sad?

#174

Post by EdwardMSmith »

plexicle wrote: post #106

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

The result of me doing the same thing is here:

https://github.com/edwardmsmith/react-starter

I didn't find the webpack stuff to be too overwhelming, and split dev and prod into two webpack files.

`npm start` to start the dev server and `npm deploy` for a production build. The production build produces two files - a vendor file that contains vendor code, and a client file that contains custom code.

It probably contains more than you're interested in (redux, tests, etc.) but it should be clear how to strip that out.

Re: React Makes You Sad?

#175

Post by fludlight »

React makes me sad because the PATENTS file means I can't sell my creation to anyone suing Facebook for patent infringement. Personally, I don't think that software should be patentable, but it is and deep pocketed companies are always suing each other over this and other IP. Even if they aren't today, there is no guarantee that they won't tomorrow. So why bother with a technology that pisses in the proverbial pool, especially one full of lawyers (aka deal killers)?

Re: React Makes You Sad?

#176

Post by tyh »

ryanswapp wrote: post #91

I think Meteor 1.3 + React is a really promising stack. If you are overwhelmed by all that comes with the default React stack (Webpack, Redux, React Router, etc...) then give Meteor 1.3 + React a try. It eliminates the need to write your own build system, makes writing a full stack JS app stupid simple, and overall makes you a lot happier.

As a js newbie I have to say Meteor + React is very easy to get started in. Add in webstorm ide and I feel like I am back in .net world.

I am still using 1.2.1, but I am excited about the more streamlined npm integration in 1.3.

Re: React Makes You Sad?

#177

Post by plexicle »

EdwardMSmith wrote: post #174
plexicle wrote: post #106

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

The result of me doing the same thing is here: https://github.com/edwardmsmith/react-starter I didn't find the webpack stuff to be too overwhelming, and split dev and prod into two webpack files. `npm start` to start the dev server and `npm deploy` for a production build. The production build produces two files - a vendor file that contains vendor code, and a client file that contains custom code. It probably contain…

That looks perfect! Does it minify/concat? I will dive deeper this evening in any case. Thanks!

Re: React Makes You Sad?

#178

Post by plexicle »

phase_9 wrote: post #162
plexicle wrote: post #106

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

Hey plexicle - I also bumped into this one when I started with webpack; I've written the approach I use as a blog post, hope this helps: http://jonnyreeves.co.uk/2016/simple-webpack-prod-and-dev-co...

Thank you very much. That post was very helpful!

Re: React Makes You Sad?

#179

Post by spankalee »

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.

React in no way implements Web Components. It doesn't create custom elements, period.

Re: React Makes You Sad?

#180

Post by spankalee »

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)

I work on a web components library, so I'm very biased here, but web components will very soon have broad compatible support across all the major browser engines. It's the only interoperable solution going forward, because every framework out there right now is a silo unto itself.
Post reply on HN