Yeoman at your service - A getting started guide
1–10 of 11 posts
Re: Yeoman at your service - A getting started guide
#2I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
Re: Yeoman at your service - A getting started guide
#3I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
What do you prefer?
Re: Yeoman at your service - A getting started guide
#4I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
If you don't trust such methods of installation, you don't have to use them. Also, you can always look at the source of the script if you don't trust said method and choose for if you want to install by hand, use the script, or just don't use the tool at all. You really can't fault Yeoman because they want to make it easy and painless to install their tool.
For the people that want to check out the script:
https://raw.github.com/yeoman/yeoman/master/setup/install.sh
Re: Yeoman at your service - A getting started guide
#5I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
I honestly like it. I can actually read the source, as opposed to a pkg or or .app.
Do you think piping a shell script is less secure?
Re: Yeoman at your service - A getting started guide
#6I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
Why? It's no different from any other installation method: http://gist.io/3670086
You're running code you haven't read. It all reduces to exactly the same vulnerability.
Re: Yeoman at your service - A getting started guide
#7I can't be the only person who hates install instructions like 'curl -L some.host|bash'. Not to mention that the yeoman install script happily installs homebrew using 'curl -k ... |ruby'. No thanks.
Why? I completely understand the intent of "curl -L some.host|bash". Even if I don't have curl or bash, I immediately know what is happening.
It's obviously a concern that you are downloading unchecked code from the internet and running it on your computer, but if you are talented enough to be able to inspect the code and certify it is not malicious, you are also talented enough how to get the code without executing it.
Re: Yeoman at your service - A getting started guide
#8It's sort of a bummer that so many people re-write quickstart documentation like it's new or helpful.
Re: Yeoman at your service - A getting started guide
#9It's sort of a bummer that so many people re-write quickstart documentation like it's new or helpful.
Hey tborg...
I've been on the private beta and working on that article for over a month in conjunction with Addy and Paul from the Yeoman team. I contributed numerous tickets and issues to the repository and assisted in testing countless times. Just so you don't think I whipped it out really quickly.
Re: Yeoman at your service - A getting started guide
#10It's sort of a bummer that so many people re-write quickstart documentation like it's new or helpful.
Did you actually read the article? It is more in depth then the QS on the yeoman.io site. At the end of the day, introductions are going to cover similar material, but I think this version is a bit friendlier than what is up on the main site now.