I used Chrome early on, then decided it wasn't mature enough (I'm a JavaScript dev, so I see some things that others don't), and I went back to FF. But FF has just been a POS lately, and is pretty much intolerable. Chrome, on the other hand, really nailed some things down as of late, and I'm back on it. Chrome still has some annoying behaviors, though, such as dropping asynchronous JavaScript (AJAX) requests before the response actually comes back. That's NOT what asynchronous is supposed to mean. They consider that a feature, and not a bug. But they do it that way because they have no other way to be "asynchronous", allowing the JavaScript thread to do other things while waiting for the response. So instead, you have to jump through hoops to make it work correctly. But for general usage, far better. Current pref order for the big three is Chrome, IE10, FF.

I think you're simply looking at this the wrong way. The tablet is just a PC with additional conveniences added. You've combined the core hardware and power into a single panel with the screen, unplugged the keyboard, and added touch capability. This provides the convenience of using it in more portable ways than a laptop/netbook. It's a better device for reading (more like a book), better for storage, fewer moving parts, etc. All of the above is not intended as a replacement for the PC, but as a supplement. Obviously, the tablet is very inadequate for many tasks. Hence, you can bring the tablet back to a dock with a keyboard and an HDMI connection to a larger screen etc. Granted, there's more work to do here, but I don't think it's going away anytime soon. When you think about it, the book has been around for thousands of years before the PC came along. The tablet is a better replacement for the book than the PC was. Maybe the non-tablet PC is the fad whose time is up... :)

It doesn't really require time off. If I'm doing enhancement work, I'm loving it. But if I have to transition to support work for any length of time, I miss it then as well. It goes from joyous to stressful, especially on projects where insufficient infrastructure planning was done...

I'm pretty sure Flash was installed in a lot of places too. But that means precisely diddly in terms of pros/cons.

The unfortunate thing is that you can't do a true progress bar, because you don't have access to the count of downloaded bytes. What most sites do is to display an animated gif image that acts as a placebo. It makes people feel like something is happening, but gives no true measure of it.

Here! Here!

If you do the math, an average of 3 hours overtime a week works out to nearly 4 weeks of overtime in a year. I'm NOT going to work more than 13 months a year for the understood "annual" salary. Any more than that represents an abuse by my employer, and an unwillingness to do the right thing and hire more resources. Don't cheap out. Don't abuse my talents. I have no difficulty finding another job.