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

111–120 of 250 posts

Re: Create React Apps with No Configuration

#111

Post by orf »

Touche wrote: post #109
orf wrote: post #106

Earlier quoted context omitted.

So you want to write HTML for a living? Ok, that's cool. But things have moved on a bit since then. I mean, you're commenting on a thread about JS libraries that enable you to write awesome single page apps and saying you... don't want to write JS? If I get you correctly then I used to be like you. "Eww, javascript". Then I was forced to use Ember for a project where I work and it is amazing , nothing that the app do…

JavaScript is part of the HTML standard so I'm ok with that. What I'm not OK with is the expectation that I'm going to run 20 tools between editing a file and refreshing my browser. They are saying that they aren't going to make the CLI a requirement and I hope that's the case, but my concern is that "use the CLI" is going to become the quick answer.

But that's the beauty of Ember: you run one tool. `ember`. Sure it uses Babel under the hood and a CSS preprocessor, but they are not separate tools really.

But what exactly is wrong with a CLI? I'm sorry but I really don't get your point. I mean, you kind of have to run one or more anyway if you want to do modern JS development because the JS you write isn't the JS that gets served to the browser (and for good reason). A CLI is a requirement and has been for a while now.

Re: Create React Apps with No Configuration

#112

Post by Touche »

orf wrote: post #111
Touche wrote: post #109

Earlier quoted context omitted.

JavaScript is part of the HTML standard so I'm ok with that. What I'm not OK with is the expectation that I'm going to run 20 tools between editing a file and refreshing my browser. They are saying that they aren't going to make the CLI a requirement and I hope that's the case, but my concern is that "use the CLI" is going to become the quick answer.

But that's the beauty of Ember: you run one tool. `ember`. Sure it uses Babel under the hood and a CSS preprocessor, but they are not separate tools really. But what exactly is wrong with a CLI? I'm sorry but I really don't get your point. I mean, you kind of have to run one or more anyway if you want to do modern JS development because the JS you write isn't the JS that gets served to the browser (and for good reaso…

> A CLI is a requirement and has been for a while now.

It's really not, you can get by fine with a text editor and a web browser only. You can use regular web components (works unmodified in Chrome, there's a polyfill for other browsers) and get modularity and all of the things you need. You can add Polymer which, again, doesn't require anything but an editor and a browser.

Re: Create React Apps with No Configuration

#113

Post by lacker »

joemaller1 wrote: post #108

This is great and I will be moving my React projects in this direction. At very least this project represents a de-facto standard and guidance about how to work with React. However I do wish the React team would pick between ES6 classes and `React.createClass`. I think I remember the main React tutorial was rewritten in ES6 at one point, but then switched back. I've read arguments both ways, but I suspect they ES6 is…

If you're using create-react-app then you're encouraged to use ES6 classes - that's how the default App.js is set up.

Re: Create React Apps with No Configuration

#115

Post by Splendor »

abritinthebay wrote: post #85
Splendor wrote: post #65

Earlier quoted context omitted.

Would you mind explaining which new problems this creates?

WebPack for one. Using webpack brings in way more problems than it solves.

Again you've suggested the introduction of problems without mentioning a single one. I'm not saying you're wrong (because I don't know what you're saying yet), but I don't think you're adding much to the discussion here.

Re: Create React Apps with No Configuration

#116

Post by lsiebert »

orf wrote: post #111
Touche wrote: post #109

Earlier quoted context omitted.

JavaScript is part of the HTML standard so I'm ok with that. What I'm not OK with is the expectation that I'm going to run 20 tools between editing a file and refreshing my browser. They are saying that they aren't going to make the CLI a requirement and I hope that's the case, but my concern is that "use the CLI" is going to become the quick answer.

But that's the beauty of Ember: you run one tool. `ember`. Sure it uses Babel under the hood and a CSS preprocessor, but they are not separate tools really. But what exactly is wrong with a CLI? I'm sorry but I really don't get your point. I mean, you kind of have to run one or more anyway if you want to do modern JS development because the JS you write isn't the JS that gets served to the browser (and for good reaso…

That said, someone could probably code a locally hosted react app that wrapped the CLI, and also indicated/logged what commands were run, output, errors, etc.

I love CLI, I live in vim and tmux as much as I can, but I think point and click interfaces are better for discovery, whereas a command line interface is better for reproducibility and therefore instructional learning.

Re: Create React Apps with No Configuration

#117

Post by lsiebert »

bcheung wrote: post #105
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've been exploring an alternative solution. Currently playing around with the idea of a React app for building React apps. Basically, it's an admin for specifying routes, models, components, database schemas, views, stores, reducers, etc. They are defined declaratively and serialized. Then can be feed to either a build step or a bootstrap that can load create the app dynamically. Each type of thing that can be edite…

read your comment right after I posted mine suggesting something like this wrapping the CLI.

Re: Create React Apps with No Configuration

#119

Post by [deleted] »

bcheung wrote: post #105
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've been exploring an alternative solution. Currently playing around with the idea of a React app for building React apps. Basically, it's an admin for specifying routes, models, components, database schemas, views, stores, reducers, etc. They are defined declaratively and serialized. Then can be feed to either a build step or a bootstrap that can load create the app dynamically. Each type of thing that can be edite…

[deleted]

Re: Create React Apps with No Configuration

#120

Post by danabramov »

lacker wrote: post #113
joemaller1 wrote: post #108

This is great and I will be moving my React projects in this direction. At very least this project represents a de-facto standard and guidance about how to work with React. However I do wish the React team would pick between ES6 classes and `React.createClass`. I think I remember the main React tutorial was rewritten in ES6 at one point, but then switched back. I've read arguments both ways, but I suspect they ES6 is…

If you're using create-react-app then you're encouraged to use ES6 classes - that's how the default App.js is set up.

>However I do wish the React team would pick between ES6 classes and `React.createClass`

We’re going with ES6 classes. Expect createClass() to go into another package some time this year.

(Obviously we’ll provide an automated “codemod” utility to convert your existing code.)

Post reply on HN