It depends on what you're building. Rollup is better suited for writing libraries, it's easier to configure and will benefit your consumers more.

Webpack is better for projects since there is lots of flexibility, it has a great ecosystem and community.

I haven't really looked into parcel much tbh, but if you're into bleeding edge you might check it out. But be forewarned, its very new so there probably won't be the same level of support that you get with more mature projects.

He did delete all his tweets. If you just search his handle you can see people who previously replied or RT him. There's plenty of what was posted on the screenshots (anti-muslim, brexit stuff in there)

TL;DR The Gregorian calendar operates on a 400-year cycle, and 1601 is the first year of the cycle that was active at the time Windows NT was being designed. In other words, it was chosen to make the math come out nicely.

Make sure you take a look at the stem and fork. I had a similar incident a few years back, head on collision. Everything seemed to be ok aside from the wheel. Then about a year later I hit a pot hole, the fork snapped and I face planted into the pavement. The fork had been damaged the whole time and I never knew until it was too late.

Where was the data for this map scraped from? I only ask because I'm slightly skeptical about Illinois, since The Smashing Pumpkins are also from Illinois. I like both bands, and it's quite possible Chicago outsold them (especially considering they had way more time to sell records) but I just couldn't find the data for either of them.

While it does run fine, I wouldn't consider it 'good' code. There are a couple of issues that should be fixed:

// The toss function is currently a global variable named toss, that points to an anonymous function.
// The difference is subtle but naming a function makes debugging much easier.
// For example, if an error occurs in this function (which it does),
// the stack trace will list this as an anonymous function instead of 'toss'
toss = function(object){
throw object;
}
try {
// Here, while it's legal to throw a string it's not recommended,
// since people using your code may expect to catch an object.
// If someone caught your error and attempted to call message() on it, their catch would throw an error
toss("ball");
}
// Just a minor detail, but the name object implies you intend to catch an object,
// but instead you catch a string which is misleading.
catch(object) {
// Since this is sample code, it's not a big deal.
// But you need to be careful with console.log since it will cause IE's JS engine to crash unless the debugger is open
console.log("I caught a " + object + "!");
}

Here is the revised sample with all of that in mind (note: I kept the naming the same for the sake of the joke):

I also decided to use template literals since they're new and sexy. And I added 'console && console.log' to check the existence of console first before attempting to log. In the real world, I would do something else and not use console.log at all.