Don't React • Hacker News Board

Re: Don't React

#71

Post by bshimmin » Fri, Apr 03, 2015, 2:36 PM UTC

ebbv wrote: post #12

First, the UI for that presentation is terrible. The arrow in the lower right is hard to notice, and on some slides it becomes invisible. Second, the Cycle.js code on slide 18 is some of the nastiest, kludgey looking JS I've ever seen. I get the ideas behind Reactive Programming the author is presenting, and they are interesting, but if that's the code his implementation is meant to produce, no thank you.

It looks a little like a combination of React and Angular. Which probably really isn't a good thing.

TodoMVC in Cycle is... intense: https://github.com/staltz/todomvc-cycle

Re: Don't React

#72

Post by Bahamut » Fri, Apr 03, 2015, 2:36 PM UTC

jlongster wrote: post #55

I actually look forward to the day when React is not engulfed in hype, so people will stop complaining that it's just going to go away when the hype dies. Programmers love to make things. When you make something, you want to bash the thing that you are "better" at. This comes will all kinds of blindfolds though (you may be on the right track, but you need to be aware of these blindfolds). There are so many examples a…

There are other choices than just React. Many of your same points applies to [insert library/framework].

I think it is important to weigh criticisms just as much as praise. This lets the best ideas get vetted by the community and developers can focus their mindshare solving other important problems.

Re: Don't React

#73

Post by hackerboos » Fri, Apr 03, 2015, 2:37 PM UTC

ndreckshage wrote: post #61

Blanket statement: anyone that makes blanket statements like 'React sucks' or 'Ember sucks' should not be taken seriously.

OP backs up his statement with examples. 'React sucks' (because there are better ways to do this) was the conclusion of the presentation.

Re: Don't React

#74

Post by [deleted] » Fri, Apr 03, 2015, 2:39 PM UTC

jlongster wrote: post #55

I actually look forward to the day when React is not engulfed in hype, so people will stop complaining that it's just going to go away when the hype dies. Programmers love to make things. When you make something, you want to bash the thing that you are "better" at. This comes will all kinds of blindfolds though (you may be on the right track, but you need to be aware of these blindfolds). There are so many examples a…

[deleted]

Re: Don't React

#75

Post by dylanrw » Fri, Apr 03, 2015, 2:42 PM UTC

impostervt wrote: post #3

For anyone else who, like me, didn't realize it - there's a little triangle on the bottom right to let you go through the presentation.

wow, what horrible color choices. Totally missed it.

Re: Don't React

#76

Post by tehcodez » Fri, Apr 03, 2015, 2:42 PM UTC

Does anyone else have real world examples of how you would actually build an application based on reactive programming? I've seen people from netflix give the same talk over and over, but they never really seem to go past handling drag or mouseover events. These account for maybe 1% of any of the applications I've ever built.

Re: Don't React

#77

Post by zak_mc_kracken » Fri, Apr 03, 2015, 2:43 PM UTC

empthought wrote: post #40

gcz92 wrote: post #36

Also, lets not forget React Native. NO other framework can prove that compatibility with mobile. A React programmer can now cover both web and mobile development with relative ease. I'm not saying that React Native or React is perfect, but I would argue it is the best option for any company with limited developer resources.

Appcelerator Titanium says "Hi. Must be nice to just coast on hype without any product support investment or proven track record."

Xamarin says 'sup?'.

Re: Don't React

#78

Post by andrewmutz » Fri, Apr 03, 2015, 2:43 PM UTC

ctdonath wrote: post #37

ryannevius wrote: post #9

TL;DR: React sucks. React isn't "reactive". Oh, and check out this reactive framework he has been working on: https://github.com/staltz/cycle

Context, please? just a little? Figuring the top comment on HN might be relevant, I checked the comments (learned to do that before following main link), then started the presentation, it did nothing, came back, found a comment mentioning the near-hidden navigation, went back, read a dozen pages and still don't know what he's talking about.

The presentation from OP is difficult to use. Press the triangle in the lower right of the page, or the right arrow key.

Re: Don't React

#79

Post by jlongster » Fri, Apr 03, 2015, 2:43 PM UTC

Bahamut wrote: post #72

jlongster wrote: post #55

I actually look forward to the day when React is not engulfed in hype, so people will stop complaining that it's just going to go away when the hype dies. Programmers love to make things. When you make something, you want to bash the thing that you are "better" at. This comes will all kinds of blindfolds though (you may be on the right track, but you need to be aware of these blindfolds). There are so many examples a…

There are other choices than just React. Many of your same points applies to [insert library/framework]. I think it is important to weigh criticisms just as much as praise. This lets the best ideas get vetted by the community and developers can focus their mindshare solving other important problems.

Sure, except React easily has the largest community yet (with these types of frameworks) so the argument doesn't really stand for other ones. There has to be really good to reasons to switch to something else completely, and really good reasons not to build on top of React.

It's definitely important to look at criticisms, but honestly, these aren't very good ones. It would have been easy to build his library on top of React.

EDIT: stronger criticisms in my opinions focus on how hard it can be to get started with an advanced app w/React compared to Ember, which takes a "bundle everything in" approach (the classic lib vs framework debate). Ember is a strong contender especially because it has a great community as well.

Re: Don't React

#80

Post by hackerboos » Fri, Apr 03, 2015, 2:43 PM UTC

ohitsdom wrote: post #58

dabernathy89 wrote: post #35

Do people really consider Grunt dead?

I'm also curious. I don't use grunt because my daily workflow is almost entirely in Visual Studio, but I though grunt was the go-to for automation tasks.

There are few JS builders these days - Broccoli, Gulp, Brunch, Cake, Gobble...