I'm still waiting for the next laptop to even meet 2 years ago Apple's model. Hint: 750Mbs continuous speed is the limit of SATA-III. Show me a standard SSD that hits that. Hint, the brand new relatively well thought of top brand I just bought only comes near that number, and not on continuous mixed R/W operation, even in a 2 drive RAID0. Last year's MBP handily beats it in disk I/O performance. Maybe if I get 4 in RAID0 I'll be equal. Unless, of course, you're talking about those PCIe drives (they're a whole different class of SSD, and priced appropriately.)

Let me find that video camera again... how do I hook that up? Oh yeah, IEEE 1394....

and yet they, and their profits, keep growing. Hope denial becomes you.

Look into a USB hub....

I can tell you I have a faster processor than anything in any MBPs, and disk I/O is not the bottleneck in transcoding. What you're really looking for is a much faster CPU, or multiple faster, preferably many cored CPUs as a preference.

To fix slashdot's broken JS by not running it?

If I had the time and the desire, I suppose a a good greasemonkey or custom plugin would take care of most of this crap. In the meantime, noscript does work, mostly.

It's honestly better than Access.... :-D

Sorry, MVCC does not magically solve all problems, especially under high concurrency loads. It solves a subset, but still doesn't overcome the fact that the underlying DB is shit. Why doesn't MS ship SQL server with MVCC fully enabled by default?

I did get around it by writing a custom implementation of the commercial module we were using for the particular transaction in question. It is true that the implementation sucked, but it sucked less on other DBs vs MS SQL, which just goes back to MS SQL sucks. I've had similar issues on Oracle and DB2, and neither of those went legs up under similar conditions like MS SQL. It's literally like driving off a cliff in a bus.

Yes, by almost 50%.

I only mentioned it to clarify in response to your question. If you're doing what I'm doing, those 2 "extra" cores matter. If you're only using it as a simple HTPC, perhaps not so much.

I wondered, so some brief research shows that concrete decomposes and its constituents melt completely at a maximum 1800C. Nuclear fuel temperatures apparently top 2000C, so it appears that a runaway reaction can burn its way through the containment vessel. That link, btw, is to an inherently safer nuclear reactor design.

I've had the misfortunate to work with 2000, 2005, 2008 and 2008 R2, and 2012, and every single one of them has failed spectacularly, many of them with the same basic issue, that wonderful escalating locks problem, which MS spins as a "performance improvement" much like driving a bus off a cliff improves its performance, and in much the same way.

Our competitors or enemies servers? A trashcan?

Lemmings....

Sounds like a thankless place to work, but still doesn't support using MS SQL.

citation? Finding people who have seen MS SQL is easy, finding expertise, however, is as much or more limited than for other systems, mainly because most with real expertise won't touch MS SQL except when the business end of a pointy stick is poking them in the eye.

MS SQL barely works, and falls over as soon as it is hit with significant load. It's an old massive pile of crap essentially given to MS by Sybase, who mistakenly didn't believe anyone would be stupid enough to continue using that smelly pile when their new database was released. They severely underestimated MS's marketing prowess in this regard, and someone like you (an AC no less!!!) propagates the continuation of this incredibly terrible solution.

Define reactor vessel. Is it the originally constructed concrete container, or material surrounding the current uranium core?