71–77 of 77 posts
But why not just fork the repo on Github (or onto your own infrastructure) and run the script from there, where you can verify any tampering?
Earlier quoted context omitted.
Wouldn't you have bigger problems at that point?
No, you might just be drinking coffee, or at a library, or on Google's public Wifi, etc.
I have a similar more light-weight project template that requires no installation (except node). Pith auto-generates test module dependencies and uses Backbone too :) https://github.com/sym3tri/pith
Earlier quoted context omitted.
Anyone who values the user experience over the tiny chance of a security breach. I'm not validating it as a good practice, but that seems to be the main reason and I've not heard of Pow or Homebrew causing any problems in this regard.. yet ;-)
Never mind the security aspect, how am I going to uninstall the damn thing or upgrade its components (which other things in my system might use) with a custom installer? There's a reason I don't install things that don't use apt.
There is a manual installation process provided on the front page; Yeoman itself appears to be a Node.js module in the node package manager npm.
I am currently using Brunch[1] as a build system. How does Yeoman compare, and why should I switch? I asked this in a previous submission on Grunt, in a thread that talked about Yeoman, but I never got an answer. [1]: http://brunch.io/ EDIT: It looks like the new FAQ addresses this issue: http://yeoman.io/faq.html > "How does Yeoman differ from tools like Brunch or BBB?" and "How does Yeoman differ from Grunt?". Post…
https://github.com/brunch/brunch/issues/408
Bower support is coming to brunch in the next release.
Earlier quoted context omitted.
Isn't that just a suggestion to get up and running quickly (for example on a dev VM)? There's nobody forcing devs to blindly follow the instruction and pipe it directly into bash. You are free to curl -L -o install.sh get.whatever.com if you want to inspect the install script.
> There's nobody forcing devs to blindly follow the instruction and pipe it directly into bash "Nobody's forcing you" is the weakest argument.
Just kidding.
It's not an argument at all. It's a manner of speech. To be more verbose: I can't think of a compelling reason why you would blindly type whatever instructions you see on the screen, into your terminal. Unless you were being forced.
Earlier quoted context omitted.
No, you might just be drinking coffee, or at a library, or on Google's public Wifi, etc.
Say you try logging into your gmail. Couldn't they spoof the DNS and point you to a "proxy" that skims your credentials?