Live data from Hacker News

Don't React (Presentation - Use arrows to navigate)

staltz.com

71–80 of 105 posts

Re: Don't React (Presentation - Use arrows to navigate)

#71
post #67

Clearly the author has never heard of ClojureScript's Om.

I would suggest Reagent as a good example of simple API on to p of React

Easier to learn doesn't quite mean "simple". I prefer Om not just because I took the time to learn it, but because it makes more sense once you do.

Re: Don't React (Presentation - Use arrows to navigate)

#72
post #54

React always feels to me to big a huge compromise between a nice statefree dataflow solution for UIs and "getting Javascripters en masse to actually use the damn thing". The entire existence of the state API is a highly visible example of this. It reminds me a lot of Gabriel's divide between the New Jersey approach versus the MIT approach---React is far more viral in its current form, but better technology certain li…

If you only care about animation, why not just use a constraint solver like a physics engine? Time step is set st run-time, constraints are quite natural (springs to pull something in). Constraint programming provides the declarative data binding feel of FRP behaviors (someone on my committee pointed that out). What you don't get with constraint systems are event streams, but that isn't so useful for UI programming a…

I think that's a really great idea, too. The worrisome bit around constraint solvers is that they're really easy to get into strange "spooky action at a distance" states of constraint interaction which are incredibly tough to escape from. Building good constraints thus feels like something of a black art.

Re: Don't React (Presentation - Use arrows to navigate)

#73
post #13
post #9

Don't break the web with your presentation framework. Since you do, I cannot take anything you say about web development seriously.

I had to read your comment to understand that there was more content than the title. Indeed I wish people would stop breaking the web is all the myriad ways that they do.

The whole web? It's all broken now? Better get a broom...

Re: Don't React (Presentation - Use arrows to navigate)

#74
post #59

Presentation author here. I should have taken this down before it popped up on HN or elsewhere. The video of this presentation is worth watching, because it's tongue-in-cheek through-out. But the slides are not worth reading, otherwise people take it seriously like it's happening here now. Cycle isn't the solution to everything, it's just one guy's ongoing experiment.

I find that Reagent http://reagent-project.github.io/ addresses many of the issues. For example, all components can be described as simple data structures. Components communicate via atoms that notify components that their state changes. This means that two components retain control over their state and can decide how they wish to react to the change in the atom.

Re: Don't React (Presentation - Use arrows to navigate)

#75
Disclaimer: I wrote Mithril (one of the vdom frameworks mentioned in the presentation)

I like the idea of reactive programming, but it tends to add a lot of indirection. This is theoretically desirable, but not necessarily pragmatic in reality. A lot of frontend code in the wild is of the throw-away-in-a-few-years nature and it's hard to get mindshare among developers if they're required to learn stuff that feels academic when all they really care about is getting stuff shipped the next day. Being able (forced?) to tightly couple a controller and a view in Angular is one reason a lot of people like it.

I was giving a workshop on FP recently, and you'd be surprised at the number of people who still don't grok `filter`. FRP is still way over a lot of people's heads. Hopefully the industry will warm up more to the concept as React, Mithril, Meteor, etc get more popular.

@staltz WRT Cycle.js itself:

I took a look at the TodoMVC example and was surprised to see intents reading data from DOM element data attributes (e.g. https://github.com/staltz/todomvc-cycle/blob/master/js/inten... ). How does one go about doing non-string parameterized intents? For example, I often need to reference an entity from an event handler and searching for it in a collection by ID seems wasteful. In Mithril, for example, handlers can receive parameters as inputs either via closures from the view or via partial application (i.e. Function::bind). This is especially useful for event handlers that deal with relationships between two or more different entities. Is there a similar mechanism in Cycle.js?

Re: Don't React (Presentation - Use arrows to navigate)

#76
post #56

He implies that Grunt is dead on the first slide. Well don't I feel stupid since I still use it. I guess it's not cool anymore? I missed the memo. Wait, maybe I'm not cool? What do the cool kids use now instead of Grunt?

Seriously, is no one using Grunt? I know there was a backlash at all the Grunt like tools that came out at the time, but I assumed it was still useful and regularly in use / updated.

We/I still use Grunt every day, works quite nicely to build two separate apps, provides us with a very solid dev environment with livereload.

Re: Don't React (Presentation - Use arrows to navigate)

#77

I have been programming for 30 years, 19 on the Web. I tried to learn Angular and Ember and failed, more than once. Earlier this year I had to prototype a fairly complex single page app and was severely time constrained. I tried React and succeeded beyond both my expectations and those of the client. I am in fact itching for a chance to use it again.

If you feel adventurous give Reagent http://reagent-project.github.io/ a shot. :)

Re: Don't React (Presentation - Use arrows to navigate)

#78
post #36
post #30

Earlier quoted context omitted.

Om is built on top of React. I'm not sure how you reconcile "React sucks" with "Om is the future" given that.

> I'm not sure how you reconcile "React sucks" with "Om is the future" given that. Maybe it fixes all the sucky parts?

Not really. It's basically just a means of using ClojureScript with React. That comes with some great stuff (immutability, for one), but AFAIK it doesn't change anything too dramatically.

Re: Don't React (Presentation - Use arrows to navigate)

#79

I have been programming for 30 years, 19 on the Web. I tried to learn Angular and Ember and failed, more than once. Earlier this year I had to prototype a fairly complex single page app and was severely time constrained. I tried React and succeeded beyond both my expectations and those of the client. I am in fact itching for a chance to use it again.

I agree to the React bit. I have been trying to get past building Todo apps with Angular and Ember but didnt succeed. React somehow seemed more natural and easier to grasp the whole concept rather than the complex stuff and steep learning curve of Angular.

Re: Don't React (Presentation - Use arrows to navigate)

#80
post #56

He implies that Grunt is dead on the first slide. Well don't I feel stupid since I still use it. I guess it's not cool anymore? I missed the memo. Wait, maybe I'm not cool? What do the cool kids use now instead of Grunt?

Seriously, is no one using Grunt? I know there was a backlash at all the Grunt like tools that came out at the time, but I assumed it was still useful and regularly in use / updated.

NPM downloads in the last month:

  Grunt: 812,465
  Gulp:  448,694
Post reply on HN