123 karma · joined January 26, 2013
Also, reminds be of the million dollar front page [1].
[1] https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage
Don't hate the player, hate game, though. welcome to the jungle.
> a set of simple rules that are within what Apache (including there all the module ecosystem) can and is designed to do
> if you want your webserver to do something complex, you'd go for Apache
I would tend to disagree. Assuming "complex" = "business logic", Apache hardly seems the right choice. PHP/Python/Node/GoLang or Lua right inside nginx would be more appropriate in most cases, imo.
Really? Completely disagree. Just look at the configuration files for these vs nginx.
- acceptHandshake = params.pass == PASSWORD
+ acceptHandshake = true//params.pass == PASSWORDYes this is a huge number, but seems like usual practice for Cisco.
[1] http://www.crn.com/news/networking/300081750/sources-massive...
I use `unset HISTFILE` to make sure when I exit the history file doesn't get all the cruft in. Every now and then I might do some housecleaning, including going through the history file then `cp ~/.bash_history{,.2}` to keep a clean copy around.
As far as saving, heres a handy function: `getlast() { fc -ln "$1" "$1" | sed '1s/^[[:space:]]*//' }`
Plus, the web experience is getting very good. eg. I only use Facebook via Chrome on my phone. It even supports background notifications.
Pros: "it just works" (mostly, nowdays, :)), it seldom overheats/has the fan turn on, it makes a good impression (read: 'dress for success'), I like the screen size, its got enough RAM for me to run a couple VMs, Unix/terminal power.
Cons: Price. Accessories.