But will the real slim shady please play back!

There is a delay shifting with the gas to the floor or not. I have a 2014 mustang that has the same issue when trying to "manually" shift the automatic.

I really don't understand why they put the buttons where they did. I like the setup in my wife's beetle better. You can actually use the shifter to change gears and it's much more responsive than my mustang.

Then it must be true because of your anecdotal evidence. Seriously, it's gotten me jobs and I've looked at linked in profiles when deciding on candidates.

Spoken like a true front end developer. You guys don't belong in the backend. Real applications store millions of rows and run on clusters. Grandma's iMac won't cut it.

I don't want to run my whole stack on javascript and worse yet not in the BROWSER. I need speed. I'm processing large amounts of data. I'm trying to build real applications.

Do you really think Facebook or twitter could run in your browser? Seriously?

From a developer perspective:
JavaScript is a pain in the ass to debug.

From a user perspective:
JavaScript can be slow. -- this one is getting better and may not matter in time.

Full stack JavaScript is insane. There are faster languages for server side and everyone pushing for it didn't live through the first try with classic ASP which was VBScript or JScript. There was even an implementation that ran on top of Java for netscape servers called chillisoft or something like that. It was even worse than running on windows with IIS. I don't want to go to the bad old days.

NodeJS is an attempt to get cheaper backend programmers because everyone has extra front end developers lying around for projects. The problem is that most front end developers I know don't know shit about big data or working on real problems. Their biggest fear is if a button is pretty and the popup works in IE8 and the latest jQuery UI.

It's stupid.

20k sounds reasonable from my experience. With MidnightBSD, I used to do builds for Sparc64, i386 and amd64 platforms. The sparc64 systems would have to compile for 2 weeks (i had 2 of them) to build packages. I ran it during the summer and the added work on my air conditioner plus the high power consumption of those old sun machines made a very rough electric bill.

I just dropped sparc in part because of the time it takes to build packages and test with it. Moving from AMD to intel CPUs for x86 helped with power draw too.

It is very expensive to maintain servers both in electricity and hardware costs. I just had my file server go out due to some drive failures and had to upgrade the lot. Unlike theo, I don't get donations do to the small size of my project. He's been very lucky.

I completely agree. For programming, multiple monitors is great. I can have documentation or a local copy of the web app running in one display and my code window in the other. I have two displays at work, one in portrait and the other landscape. Works very well for web development.

Now, this giant monitor might be great for gaming.

X works on my operating system.

One problem is OS and toolchain support. You might get something together for Windows, OS X and Linux, but that's where the buck stops.

The next problem is that standalone compute cards are rather expensive and putting in a high power GPU has considerable power requirements. Then most server racks are full of 1u wonders not designed to get rid of heat or even hold a huge AMD or NVIDIA GPU.

Open source databases are great, but they're often pushed as a cost savings to companies. To turn around and buy extra hardware to make them faster isn't going to cut it.

Finally, there's the oddity of programming languages that some databases are written in. The popular SQL databases are in C so that's not a problem. Some of the others are in Java, erlang, or some other crazy language that may or may not have OpenCL or CUDA support.

You're making the same mistake. Some young people know what they're doing.

Some old people don't know shit. They still use sccs and rcs, pre ansi c and perl to write software because they won't learn new stuff. They still use the same database from the 1980s because they won't learn a modern one. (yeah, i left that job... )

I'm in my 30s so I'm not in the young group or the old group yet and I see crap on both ends.

At any age, you can have talented people. Don't judge by age, only demonstrated skills.

I work at the University of Michigan and we use Gmail and Google apps. I'm not a big Gmail fan, but it's actually not bad for business use.

There are still people trying to use outlook as their client, but most people prefer Gmail now. It can work for large organizations.

To be fair, healthcare.gov was clearly behind schedule and they released what they had. I don't think the government shutdown caused the problem. It may have made it worse because they had a few less people working on it.

Server capacity issues mean they didn't perform load testing or underestimated demand. Of course, the code wasn't done so it's hard to test.

A small team could have written that website in the time allotted without issues provided the specs didn't change. The cost of the site and the number of people involved is insane and demonstrates the consultants took them for a ride.

I bet it was cheap, inexperienced developers who had no clue how to build a scalable site.

SteelSeries mouse drivers will cause the Windows 8.1 upgrade to fail.

Microsoft really screwed something up with the Windows 8.1 mouse drivers. They really need to get this fixed.

I use mail on iOS and google gmail client for work mail. Both are decent but I think gmail is slightly better. You should try it. I don't actually like Gmail all that much but the iOS app is good.

As for desktop, mail.app is buggy but not as bad as trying to use thunderbird. All mail clients suck

I actually wonder if Intel could catch up a bit on GPU performance with the integrated graphics on the newer chips. They're not process blocked. Same thing with AMD on the A series chips.