Bragging aside, explaining the whole business from a (potential) customer experience is what differentiates good from bad companies (_nb_ I was tempted to write successful vs failing, but then I realized there are some very bad companies out there)
I've never upgraded before, just started out fresh. But y env got pretty complicated so I'd like to try an upgrade. What's the experience with the "Fresh upgrade"[1]?
A fresh upgrade is just backup, plain install, restore. It's super reliable but somewhat inconvenient and time consuming.
A package upgrade is easier for friends of the command line but runs the risk of leaving your computer with an inconsistent package selection or configuration. And it's less used so bugs are more likely.
I tried a package upgrade for 14->15, worked great. shrug I did 15->16 a few days ago reinstalling fresh (wanted to disable encrypted home directories, figured this was the easiest way to do it). Worked great too.
It looks mainly to be pitched as an alternative to Grunt, the current main (I think?) Node.js build tool. And its primary feature seems to be that you don't have to figure out where your intermediate build products go. Beyond that, who knows.
(Grunt, incidentally, strikes me as a system that has learned nothing at all from decades of other build tools. It's about one step better than piping globs to unix commands.)
It's intended for people that are building web stuff with node. So they're already writing everything in Javascript and already have a dependency on node, so using node for their build process eliminates a dependency on Make or whatever.
The incumbent in this niche is Grunt. Grunt has a rich ecosystem of plugins, but it's complex, difficult to configure and difficult to debug. Gulp is meant to be simpler and therefor easier to use.
Gulp is not meant to compete with Make, Maven or the like.
I haven't read any of Zed's book and Amazon doesn't have a decent number of reviews, so I was wondering if someone could provide the shortest "why should I get this book"
Yep, postgres has all the account / user details, lists of what network and channels to join, billing etc.
All the irc messages end up in cassandra, via rabbitmq. We use local redis as a cache for the most recent messages. Our cassandra cluster is on EC2 (~11ms away from our other hardware, which is in LA).
I use a bookmarking service (Pinboard) as I do for all pages I consider that I might need to get back to at some point. I also have the Pinboard archival service that saves a copy of the web page in case that goes away.
