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

Ask HN: ReactJS – Do you use it? Do you like it?

news.ycombinator.com

Post reply on HN
Print view View original

71–78 of 78 posts

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#71

Post by seivan »

bdr wrote: post #64
seivan wrote: post #13

Earlier quoted context omitted.

It's suboptimal and obscure. There is barely any up to date resources on it. So far I've managed to get to stuff presented on the window, but as soon as you start messing with references to the DOM components, things start to break down. It's a shame, I really think Typescript and React would be the answer to getting a decent code base. One of the cool parts, is that you get to define what your property is with stati…

Thank you. I'd love to use these together.

Hey! I got started with Webpack and now got a decent workflow.

Still figuring out the interoperability between React(JS) and TypeScript.

There are some issues regarding arrays from React that don't have Typescript features, even when casted (like filter() and reduce()

Not to mention the lack of JSX makes things verbose.

Anyway, here's a sample code of Facebooks own tutorial. https://gist.github.com/seivan/fad1a175a5e140299fb2

I REALLY love the one-way flow of data.

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#72

Post by andreasklinger »

tmm wrote: post #15
Cshelton wrote: post #6

I'm using it for a very large enterprise app. React's advantage is the declarative style, very easy to reason about your View logic. Team productivity is up, fixing/changing older UI is easier/quicker, it's great. We've tried angular, we were using just vanilla JS and Jquery, React is great. A great resource you should check out is the slack channel Reactiflux. Many active people and they will answer any question you…

I am using React for a smaller enterprise application and find it quite difficult to reason about. But perhaps it's not well suited to deeply nested forms with lots of fields. After about six months, I finally feel like I've got a handle on how it works, sort of. It's probably not something I'll use again on future projects though.

imho: Forms are one of the things react still sucks in. Standards are missing.

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#73

Post by KurtMueller »

notduncansmith wrote: post #70
KurtMueller wrote: post #69

Earlier quoted context omitted.

How you liking Reagent? Why did you choose that over Om?

Honest answer? It seemed simpler. I haven't used Om yet so I won't try to compare the two, but Reagent presents very simple interface. Components are just functions which emit Hiccup. Reagent's ratoms are, I'm told, much like Om's Cursors, but different in a way that I haven't investigated enough to understand. Looking at the READMEs for the two projects, Reagent just seemed more approachable to me. While I've really…

Yea, going through Reagent and Om's tutorials side-by-side, Reagent seems way simpler. I'm new to Clojure and Clojurescript, so I figure learning Reagent would provide a base where I could then delve into Om.

Are you using Reagent in production or just for personal projects?

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#74

Post by BFay »

swlkr wrote: post #62

I've used it on a few personal projects with a koa powered API on the backend and one smaller project at work. I like it a lot, I've tried angular and jquery as well, both really don't stack up at all. One thing that I wish was different was the focus on using flux. Flux isn't really for me, I found it really complicated and it made following the data through my app even more complicated than it was with angular. The…

How do you like koa? I really like the way it handles async stuff with coroutines.

I'm wondering if it will have lasting appeal, though, because ES7 should introduce async/await to javascript, which will probably replace the coroutine style.

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#75

Post by seivan »

andreasklinger wrote: post #72
tmm wrote: post #15

Earlier quoted context omitted.

I am using React for a smaller enterprise application and find it quite difficult to reason about. But perhaps it's not well suited to deeply nested forms with lots of fields. After about six months, I finally feel like I've got a handle on how it works, sort of. It's probably not something I'll use again on future projects though.

imho: Forms are one of the things react still sucks in. Standards are missing.

Yeah I'm spoiled silly by Rails forms builder, both the standard as well as the better simple_form!

But I suspect Components will make forms awesome for React!

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#76

Post by grandalf »

brentvatne wrote: post #65
grandalf wrote: post #29

I love it. The only things that could be improved are: - some components in the ecosystem are more hobby projects and have trouble keeping up with React's API, even though it's small. - Documentation for react-native could be a bit better (but react-native is amazing). - I still haven't found a nontrivial and non-bloated example of react hot loader config, and getting it working on an existing project seems to be a b…

Hi grandalf! Which sections do you think are most lacking in the react native documentation? I've put some time into improving it this week by adding: - https://facebook.github.io/react-native/docs/animations.html... - https://facebook.github.io/react-native/docs/direct-manipula... - https://facebook.github.io/react-native/docs/navigator-compa... I'd love to hear where you think I should be spending my efforts next.

That Navigator Comparison doc is excellent. I suggest you link to it toward the top of the Navigator and NavigatorIOS docs.

A few things I've found confusing:

- What is the best way to implement Stripe checkout in a React Native app. I'm a bit surprised nobody has done this yet so wondering if I'm missing something.

- What is the status of the ReactExtensionsManager project? Is that going to be officially supported? What is the plan for modules? Where does Cocoapods fit in?

- Will we always have to drag/drop things using XCode to use some 3rd party components. It would be great to eliminate the need for that.

- Is there a way to wrap a native component without using Objc? From the tutorial it looks like an objc header file is always required, but it's not 100% clear why. It seems like the recommendation do React Native developers would be to just stick with Objc as the IOS language to focus on (aside from RN)

- What is the timeline for releases that cover the rest of the native SDK's major APIs (like payments)?

So I think these fall into the big picture project organization bucket or maybe the FAQ bucket.

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#77

Post by notduncansmith »

KurtMueller wrote: post #73
notduncansmith wrote: post #70

Earlier quoted context omitted.

Honest answer? It seemed simpler. I haven't used Om yet so I won't try to compare the two, but Reagent presents very simple interface. Components are just functions which emit Hiccup. Reagent's ratoms are, I'm told, much like Om's Cursors, but different in a way that I haven't investigated enough to understand. Looking at the READMEs for the two projects, Reagent just seemed more approachable to me. While I've really…

Yea, going through Reagent and Om's tutorials side-by-side, Reagent seems way simpler. I'm new to Clojure and Clojurescript, so I figure learning Reagent would provide a base where I could then delve into Om. Are you using Reagent in production or just for personal projects?

Just for personal use right now, though I'm currently implementing something on my own time that I'm hoping will prove valuable enough to be used at work (thus introducing ClojureScript to my company). A bit underhanded, but I genuinely think that the system I have going with CLJS so far is leagues ahead of what we'd get with an Angular implementation (which we used for the other side of our front-end).

Re: Ask HN: ReactJS – Do you use it? Do you like it?

#78

Post by Reefersleep »

notduncansmith wrote: post #68
Lazare wrote: post #59

Earlier quoted context omitted.

The point of flux is one way data flow. Your data lives in ONE place (the "store"), and then it's fed into your views, which render it in a deterministic fashion. User interaction triggers actions, which circle back around to modify the data in your stores. Data should only be modified by actions, and views should only change when your data does. There's a lot of advantages to this (in terms of performance, but much…

Okay thanks, that actually clears things up a lot. Funnily enough, I found myself using this exact pattern in ClojureScript yesterday, using a ratom as my store and having what I suppose I should call "actions" which (may make HTTP calls and) update the data.

Sounds like Re-frame might be the natural next step for you: https://github.com/Day8/re-frame

I haven't used it myself yet, but I'm itching to! I love Reagent and I'm very interested in FRP, especially the proposition that it might simplify the code a great deal if your app is above a certain threshold of complexity.

Post reply on HN