Especially since their utilities are already open source: http://www.ksplice.com/git/ksplice.git/ But ya, you're essentially paying for their subscription service. It would make a nice addition to RHEL subscriptions, I wouldn't be surprised if Red Hat acquired them.

Yep, silly article, the CPU intensive work is already in C++; the PHP code is mostly doing I/O. C++ won't make your memory/disks/network any faster. That's why they need all those servers.

Actually it's been more the other way around: a developer includes BSD code into his GPL-licensed project, makes improvements (knowing that his GPLed improvements are safe from non-FOSS software, and yes it does just work that way). Original BSD developer throws a public hissy fit because he can't use the new and improved code in his project. Funny how he didn't care when it was happening behind closed doors, but having the new code right under his nose was just too much.

Moral of the story, if you don't want people doing whatever with your code, don't choose a permissive license!

Isn't that why Google created the V8 JavaScript engine? It (just-in-time) compiles JavaScript to native machine code.

I'm surprised there was no mention of YouTube's Flashless HTML5 demo page. I think it's a bit more popular than Dailymotion.

Have a look at the book How to Design Programs, which was written with a pedagogical focus and is a great way to teach the fundamentals of programming and problem solving. It uses an excellent free programming environment which should make it easy for students to get started.

Nvidia could probably acquire AMD nowadays, seeing as how AMD hasn't been doing to well in the markets lately. Biggest roadblock might be getting approval for that merger since that would leave us with only one discrete GPU vendor to choose from.

This may not be what you're looking for, but when I was in high school I wrote a very simple ray casting game (a la Wolfenstein 3D), which makes good use of high school level math. Here's a tutorial for example: http://www.permadi.com/tutorial/raycast/ It definitely helped me get more interested in math, which is why I think showing how math is used in the real world is very useful (although writing video games probably won't interest everyone).

It's free to donate it and you know it actually gets put to good use rather than sitting in a blood bank. Plus I think you get some real life karma for it. Well either way, don't let the doctor discard it (like usually happens).

And even for those who must have a Windows GUI, TortoiseGit is currently being worked on.

Letting repositories sprout like mushrooms is a good thing, it will let your developers experiment with ideas they might have, things that they aren't sure would work yet but they want to try out anyways. In those scenarios, asking for permission and having to create an official branch in the central repo might be too big of a barrier, so they might work on it without the help of any version control which is bad but happens often with centralized VCS, or they'll just drop the idea altogether. And anyways, using something like svn won't stop people from sprouting their own repositories now that we have tools like git-svn which will allow you to clone an svn repo into a local git one.

The other big advantage is that when you start using a distributed VCS like git, the performance difference is so large that you find yourself using it a lot more. For example, you might notice that your developers start committing smaller atomic changes (rather than full days work at the end of the day) or they'll be more willing to create branches for different tasks because merging them back is easy in git and not so much in svn.

Also regarding your question about developers arguing who should merge with whom, a VCS isn't a replacement for communication. Git will allow developers to try out different ideas easier and allows easier offline collaboration, but at the end of the day, as the project lead you are responsible for what goes into the "official" repo and what doesn't. So you can still have a central place where releases are made (like your own local repo or one on a central server), but with git the development process is a lot more flexible.