Live data from Hacker News

React Tutorial: Cloning Yelp

fullstackreact.com

21–30 of 258 posts

Re: React Tutorial: Cloning Yelp

#21
post #5

The setup required just to get a production-ready idiomatic `hello world` app in React is downright insane. Without the Facebook name behind it, I don't see how React could have ever made it this far. Foolish of me to keep underestimating the pains that JS developers willingly tolerate.

[deleted]

Re: React Tutorial: Cloning Yelp

#23
post #15
post #11

This genuinely made me feel ill. The author has done a tremendous service to others - clearly and patiently listing the thousands of steps required to get a basic modern web app up and running. I agree with others that it is often difficult to find all the steps for a process like this in one place. At the same time, this is completely, totally fucking insane.

I feel this way about Node and React sometimes but I'm not sure other environments are necessarily better. In a way the fact that you can do all this in a bunch of text files is pretty elegant. Is installing and configuring Apache and PHP with a bunch of modules that much easier, or does it only appear easier because of apt-get, a2enmod, etc.?

I'm interested about why you mentioned Node—aside from the occasional silliness of npm I find it easy and quick with minimal to no boilerplate.

Re: React Tutorial: Cloning Yelp

#24
post #3

To me this epitomizes what I feel as I'm trying to explore options for different front-end frameworks. In this article I'm 30 screens down (literally 30 page down presses) and it's not even finished setting up the environment and dependencies. Sure, this is something that you only do once, so if it then leads to much better development workflow it makes sense to have a solid investment upfront, but it makes it very h…

> In this article I'm 30 screens down (literally 30 page down presses) and it's not even finished setting up the environment and dependencies.

I'm writing a tutorial right now for testing AngularJS and this is exactly what I'm running into. It's a tutorial but half of my first part is "install this, put this line in this configuration file, install this, add this one here, etc." It's easy to feel like I'm not writing a good tutorial but really that's just the current state of JS development.

Re: React Tutorial: Cloning Yelp

#25
post #20

Am I the only person who just doesn't get the appeal of Webpack over using something like Gulp? It just seems to me like Gulp is so much easier to use and setup.

Webpack does a lot more. Gulp is just a glorified (and cross-platform) make.

I guess I meant more from a ease of use point of view. Gulp/Grunt are easier to configure and get going.

Re: React Tutorial: Cloning Yelp

#26
post #5

The setup required just to get a production-ready idiomatic `hello world` app in React is downright insane. Without the Facebook name behind it, I don't see how React could have ever made it this far. Foolish of me to keep underestimating the pains that JS developers willingly tolerate.

Your comment is wildly uninformed.

https://gist.github.com/danawoodman/9cfddb1a0c934a35f31a

Re: React Tutorial: Cloning Yelp

#27
post #15

Earlier quoted context omitted.

I feel this way about Node and React sometimes but I'm not sure other environments are necessarily better. In a way the fact that you can do all this in a bunch of text files is pretty elegant. Is installing and configuring Apache and PHP with a bunch of modules that much easier, or does it only appear easier because of apt-get, a2enmod, etc.?

I'm interested about why you mentioned Node—aside from the occasional silliness of npm I find it easy and quick with minimal to no boilerplate.

What people refer to as boilerplate for setting up React, including in this article, is about installing and configuring node modules, build systems and other tools. React itself is just two modules (React, React-DOM.)

Re: React Tutorial: Cloning Yelp

#28
post #11

This genuinely made me feel ill. The author has done a tremendous service to others - clearly and patiently listing the thousands of steps required to get a basic modern web app up and running. I agree with others that it is often difficult to find all the steps for a process like this in one place. At the same time, this is completely, totally fucking insane.

Shouldn't stuff like this be as easy as cloning a bootstrap, npm install and go?

I'm an acknowledged novice but I find "modern" web development to be completely insane.

Re: React Tutorial: Cloning Yelp

#29
post #20

Earlier quoted context omitted.

Webpack does a lot more. Gulp is just a glorified (and cross-platform) make.

I guess I meant more from a ease of use point of view. Gulp/Grunt are easier to configure and get going.

Not that I have too much experience with either. But one example is having one webpack configuration with misc. loaders vs. reinventing it yourself and ending up with this mess:

1) You still get a config file, neat right https://github.com/mgechev/angular2-seed/blob/master/tools/c...

2) And this boilerplate https://github.com/mgechev/angular2-seed/tree/master/tools/t...

Re: React Tutorial: Cloning Yelp

#30
I have something VERY similar to this in production built with Angular, and let me tell you, I'm looking forwards to the day that I get to refactor it in React.

I get that it's frustrating to do a lot of setup. But that's the nature of the game. We're all standing on the shoulders of giants.

React is a pleasure compared to other ways of conceptualizing and practicing building user interfaces on the front end.

Post reply on HN