5 ms·
To be fair, the parent to your comment included lots of steps that assumed the user was starting from scratch. If we assume the same for the user making an Expr
by csallen 10y ago
To be fair, the parent to your comment included lots of steps that assumed the user was starting from scratch. If we assume the same for the user making an Express app, the steps are much more complex:
* Install a C++ compiler (XCode or libssl-dev packages)
* Run the NVM install script
* Use NVM to install Node.js
* npm install express-generator -g
* express myapp
* cd myapp; npm install
* Install or update Homebrew
* Install git
* git init
* Install Mongo (or your db of choice)
* Install Mongo packages via npm
* npm start
- wale 10y agoReally? This steps you just listed are similarly complex to what's in that React article? No No bruh.... 30 screens -- down-button-presses down and we're still seting up for a frontend sample app. This is so so an issue, Node(backend), Go and Rails and Py aint got.
- csallen 10y agoI'm not comparing my steps to the React article. I'm comparing them to the steps in the comment I was responding to. Anyway, measuring steps in terms of "screens" is woefully inaccurate. For example, the author of the post uses more than one screen on simply running `npm init`, because he includes unnecessary paragraphs and screenshots. Many other parts of his post are even more verbose. I could rewrite the first 30 "screens" of his post in 1-2 "screens". Would that mean that the process is suddenly 30x easier?