[atonse]

I still strongly favor Ember for exactly the reasons React and other frameworks simply haven't caught up: the out of the box experience.

I can start building an actual app within 3 minutes of typing "ember new" – with React, I'd spend the first couple of days just fiddling around with build scripts.

Sure, there are now react boilerplates that do this, but there are too many out there to properly evaluate what to use. Why not just make it a part of the framework?

I think one of the reasons React has been successful is that most developers inherently enjoy the actual act of tinkering as much as they do actually building something. They are ok with spending the first 72 hours of their project picking and setting up their build tools.

On the other hand, I can't stand that stuff.

That's what's so weird to me about all this. Ember is to front end JS exactly what Rails was. Yet rails was successful and Ember wasn't. I think it's the difference between front-end culture and back-end culture.

[davedx]

> I can start building an actual app within 3 minutes of typing "ember new" – with React, I'd spend the first couple of days just fiddling around with build scripts.

> Sure, there are now react boilerplates that do this, but there are too many out there to properly evaluate what to use. Why not just make it a part of the framework?

create-react-app [1] is the official out-of-the-box CLI for React apps. It's maintained by the React team and has been around for a while now too. I may occasionally disagree with what gets included (e.g. service workers) but overall it's been a massive bootstrapping productivity booster for me.

[1] https://github.com/facebook/create-react-app

[atonse]

As recently as 6 months ago I had react developers point me to a couple different boilerplates. So my info on this is a bit skewed. Good to check into this.

[simonw]

I started using React properly a year ago and I was dreading having to tinker with scripts for 72 hours.

The developer experience I got from create-react-app was astounding - it gave me the most productive frontend experience (live reloading, preconfigured Babel) I've ever had.

These days I turn to React for quick throwaway projects because I know create-react-app will have me up and running straight away.

[theodorton]

> Sure, there are now react boilerplates that do this, but there are too many out there to properly evaluate what to use. Why not just make it a part of the framework?

Isn't this what `create-react-app` is supposed to solve?

[zerr]

How does it compare to Angular 5?

[rublev]

>with React, I'd spend the first couple of days just fiddling around with build scripts.

Yeah a long time ago now. Since July 2016 create-react-app has been available, there are many other scaffolding tools as well.

>Sure, there are now react boilerplates that do this, but there are too many out there to properly evaluate what to use.

Use the one provided by the creators, facebook.

Why not just make it a part of the framework?

React is small (ok, "small"), you can use it out of the box without any build scripts. It doesn't make sense to package it up.

And speaking as someone who's done React for a couple years now and had to port old rails codebases to api-only / react views... yuck, never again. Rails is cluncky and most of the devs I worked with didn't know how anything works 'under the hood'.