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

Create React Apps with No Configuration

facebook.github.io

Post reply on HN
Print view View original

161–170 of 250 posts

Re: Create React Apps with No Configuration

#161

Post by k3liutZu »

scarlac wrote: post #156
mason55 wrote: post #152

Earlier quoted context omitted.

> There's no official path from view layer -> complete app (no guidance for data flow, how to communicate with the server, server side rendering, routing on the client). Every time I've decided to take an afternoon to poke at React this is where I've given up. I totally understand the model and appreciate how useful it can be but I've never been clear about how to actually hook it up to a backend that isn't just the…

I think this is common. For me the front page and JSX threw me off. React was so un-opinionated that it can loose its appeal when it presents itself. Once I took an opinionated tutorial it became much clearer to me. Since then I've used React in conjunction with Django, PHP/Laravel, converted large jQuery codebases to React and created frontend-only sites. I've not yet gone full-on with a NodeJS back-end and isomophi…

No, that becomes a nightmare to maintain. Use Redux and connect any component that needs data to the store and get the data needed directly.

Re: Create React Apps with No Configuration

#162

Post by quaunaut »

freyr wrote: post #149
ctvo wrote: post #57

Earlier quoted context omitted.

Kind of interesting to think about the two projects and how they diverge based on the core developers. Ember is made by folks who work on / for small and medium companies[1]. They don't have the build infrastructure Facebook does and are able to create an anointed solution in Ember-CLI because they'll use it daily. React is stuck in a place where the environment it's developed in is unique from what any other user wi…

> I think the React team needs to take a little more responsibility for the eco-system it created. You can't call it just a view library when most use cases use it to develop entire applications. This is the reason I've embraced React. No, Facebook doesn't dictate how React fits into the rest of your app, and yes, it requires more effort up front to fit the pieces together. But judging by the popularity of React vs.…

It's a matter of encouraging health in a community. A lack of proper resources(which can be everything from documentation, tutorials, guides, libraries, to tools like Ember-CLI) can lead to mistakes in design and part of your community going off on a tangent, which leads to dead branches of development trees.

For example: While React still works for a lot of people who did things in ways advocated early on, the rise of Redux and functional reactive programming has caused the community to move in a direction many library authors weren't aware of when they began.

Is it anyone's fault? No, not really- but taking advantage of stewardship in a community can lead to better tools and resources that help newbies, take some of the work out of your hands, and keep quality for everyone as high as possible.

Re: Create React Apps with No Configuration

#164

Post by smrtinsert »

freyr wrote: post #149
ctvo wrote: post #57

Earlier quoted context omitted.

Kind of interesting to think about the two projects and how they diverge based on the core developers. Ember is made by folks who work on / for small and medium companies[1]. They don't have the build infrastructure Facebook does and are able to create an anointed solution in Ember-CLI because they'll use it daily. React is stuck in a place where the environment it's developed in is unique from what any other user wi…

> I think the React team needs to take a little more responsibility for the eco-system it created. You can't call it just a view library when most use cases use it to develop entire applications. This is the reason I've embraced React. No, Facebook doesn't dictate how React fits into the rest of your app, and yes, it requires more effort up front to fit the pieces together. But judging by the popularity of React vs.…

Absolutely agree. Innovation also is much easier when not boxed into one approach. It's like people are blaming react for the revolution it created on the client side.

Re: Create React Apps with No Configuration

#165

Post by brianllamar »

orf wrote: post #25

> Having just attended EmberCamp a week ago, I was excited about Ember CLI. Ember users have a great “getting started” experience thanks to a curated set of tools united under a single command-line interface. This is one of the best things about Ember. `ember new`, `ember serve`, ember generate component my-component`, `ember build`, `ember deploy`, `ember install`. It's opinionated but it lets you get productive rig…

I love the opinions I get with Ember and love it for getting small projects off the ground quickly and prototyped.

One thing I don't see a lot of is opinions in React on deploying. I wrote a blog post on deploying this new boiler using netlify, pretty straight forward. https://www.netlify.com/blog/2016/07/22/deploy-react-in-30-s...

Re: Create React Apps with No Configuration

#166

Post by tptacek »

k3liutZu wrote: post #161
scarlac wrote: post #156

Earlier quoted context omitted.

I think this is common. For me the front page and JSX threw me off. React was so un-opinionated that it can loose its appeal when it presents itself. Once I took an opinionated tutorial it became much clearer to me. Since then I've used React in conjunction with Django, PHP/Laravel, converted large jQuery codebases to React and created frontend-only sites. I've not yet gone full-on with a NodeJS back-end and isomophi…

No, that becomes a nightmare to maintain. Use Redux and connect any component that needs data to the store and get the data needed directly.

Not much more to say about this than that I do not agree, that I think flux-alikes are overused, and that it's just as easy to go too far the other direction, where nothing has any state even for trivial UI state concerns.

Re: Create React Apps with No Configuration

#169

Post by thegayngler »

This was one of the downsides to us using React at work. I did a presentation on Webpack and React and my manager who is the VPE said having to figure out and choose tooling was a concern for him. I responded we should know what the tooling is doing and introduce pieces into our stack rather than go all the way in. This allows us more freedom on how and when to upgrade or change different tools in our front end stack.

Re: Create React Apps with No Configuration

#170

Post by shaneos »

danabramov wrote: post #92
ctvo wrote: post #73

Earlier quoted context omitted.

Sorry I edited in a WHOLE bunch more that you probably wouldn't agree with after your reply. Apologies!

Lol. No, I still fully agree. We think React is a tool to create great UIs, and UIs definitely include concerns like data fetching, etc. So some of this might make it into React in some form in the future.

In the meantime, you can also try out the official Flux library from Facebook (https://github.com/facebook/flux), or Redux (https://github.com/reactjs/redux), which offer great solutions for data manipulation and storage
Post reply on HN