Live data from Hacker News

Create React Apps with No Configuration

facebook.github.io

201–210 of 250 posts

Re: Create React Apps with No Configuration

#201

This is great since it provides an OFFICIAL opinionated set of tools for building React apps which is typically the largest barrier of entry for new developers looking to experiment with this technology. However, it is missing a lot of core features that typically come standard with Webpack/React boilerplates. Directly from their Github: Some features are currently not supported: Server rendering. Testing. Some exper…

Thanks for plugging my list :) VERY happy to see that people are finding it a useful set of resources, and I'm continuing to add links to it as I go. I'm trying to find more intermediate/advanced content to fill it out, as I figure I've got more than enough basic tutorials listed for now.

Re: Create React Apps with No Configuration

#202

Earlier quoted context omitted.

And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. And if we CAN'T "make decisions today based on the state of things years ago", then we're really screwed.

> And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. But Ember has likely come a long way in that time - I think this is mcardleliam's point.

For me the creation of ember cli was like admiting their framework didn't work as good as they intended.

Re: Create React Apps with No Configuration

#203
This is a great start. I too got frustrated with the overwhelming complexity of the "boilerplate" or "starter kits" that have all the bells and whistles. Having something very simple that you can exit if necessary is nice. The approach I took was just to document each tool or plugin that I may want to add to my project since it is generally very quick to do so: https://github.com/bruth/modern-javascript-starter

Re: Create React Apps with No Configuration

#204

Earlier quoted context omitted.

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.

Agreed.

Re: Create React Apps with No Configuration

#205

Earlier quoted context omitted.

If we let you tweak them, any minor update on our part would be a breaking change. We wouldn’t be able to introduce new features or update the underlying tools without a lot of risk. This is why we don’t let you change the configs. If you have a specific pain point, please file an issue. I think we can make defaults better. It takes more work but is more rewarding in the end because it benefits everyone.

This is super useful for helping beginners overcome initial barriers and quickly become productive, but do you see this as something that most will eventually grow out of?

When you grow out of it, you run "eject" and customize everything you want.

We think in the beginning many will "eject" but we will gradually make the defaults better to cover more and more use cases.

Re: Create React Apps with No Configuration

#206

Loving it! I always wanted to get started with ReactJs but looks like time has come! I tried the module and I am loving the "Welcome to React" page on my localhost! Thank you!!! PS. Already in /src/App.js , and wow live reloading without gulp or browersync , it is so simple to get started! Thank you!

I thought the live reloading was just for CSS?

Yep. For components we refresh the page now. (Automatically still.)

Re: Create React Apps with No Configuration

#207

Earlier quoted context omitted.

Please say it isn't so! Class is terrible syntactic sugar to please old Java programmers. I'd be really interested in why this decision would be made. Im just getting going in React and am looking to make a move away from Angular, because Angular 2 is so hyper focused on classes and decorators. I like React because it's closer on the purity scale to something like Cycle.js. But nevermind me, React is a great tool, an…

React's lifecycle methods and other similar features require some kind of "object instance" to exist. Since React was created prior to ES6, the React team created their own "inheritance"-ish approach, which is something that every JS library out there was doing as well. One of the main arguments for classes being included in the ES6 standard is that it's a common approach that libraries can converge on and use togeth…

Exactly.

We don't like classes, but we don't like "pseudo classes" (createClass) even more. Better the devil that's standardized.

We already offer a way to create stateless components with just functions. We will keep exploring that space and eventually might have a class-less solution we like that satisfies all our use cases.

Re: Create React Apps with No Configuration

#208

Is it me, but is not Angular just taking over? Kind of Google vs Facebook thing. Just think Google won this one.

Eh, it's not a winner takes all war - it's the quest for continual experimentation and improvement on the tools available to us for improving how we build apps. The winners are all of us.

Re: Create React Apps with No Configuration

#209
post #148

Earlier quoted context omitted.

Only for those used to ember-cli. For the huge majority this is irrelevant.

It provides a consistent mental model across frameworks for building front-end applications via CLI.

This would make people expect us to implement everything it does. We currently don't plan to.

Re: Create React Apps with No Configuration

#210
post #202

Earlier quoted context omitted.

> And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. But Ember has likely come a long way in that time - I think this is mcardleliam's point.

For me the creation of ember cli was like admiting their framework didn't work as good as they intended.

I'm sorry, Ember has come a huge way in 2 years. We've got 2.0, which was a big leap forward, a whole bunch of concepts were refined/removed or changed.

Also you're flat out wrong: Ember-cli isn't really anything to do with the framework. You don't need it to write Ember apps, it's just the communities command line tool for managing Ember projects. That's all.

Post reply on HN