Could you explain this a little more? It seems to me that "go to definition" is a rather basic thing for any IDE and since CTAGS' primary job is exactly that, I don't understand why it would not work so well on your particular code. I mean, all it has to do is understand the difference between a definition and not a definition (i.e. it doesn't need to fully understand the code), so if it is having trouble doing that job it certainly reflects poorly on the tool.

I guess I'm just curious what sort of code or code layout would cause it problems.

No, no, and again, no...

This story only serves as flamebait and the only real thing it demonstrates is that the editor (timothy in this case) shouldn't have bothered to post it. The vast majority of FOSS developers and FOSS users (those would be people who primarily use FOSS) use the free IDEs. Why? Because most FOSS developers actually run a FOSS operating system and those, surprisingly, do not run Visual Studio.

Yes, there are some FOSS devs who do their work under Windows, and they may be slightly impacted by this (as you said, VS 2010 is still free), but it is by no means a majority.

No... I must completely disagree. If you actually read the poll, there is absolutely no way you could accidentally mistake this for a serious marketing poll.

A legitimate avenue for conversation is whether or not the poll is actually funny. Personally, I think it is. It's a pretty good example of buzzword bingo, but the real humor here is that this poll only exists because of all of the "Slashdot has gone uber-commercial!!!1!!!" complaints and shows that the editors are aware of the prevailing opinion.

I understand that there are a lot of humor-impaired people out there, but I suspect that a lot of the whining is from people who merely glanced at the poll, saw a buzzword, and then assumed it was a marketing poll. And, to be fair to /., there were like two or three stupid marketing polls. That's it. The haters, along with not being able to detect humor, are now defaulting to assuming that everything /. does has a sinister PHB motive unless there is some sort of mountain of evidence to the contrary.

That said... SlashBI is a pretty terrible idea...
SlashTV started really bad, but it certainly looks like they listened to the complaints and it has improved markedly, though I still pay little attention to it.

My gallery on my university/work machine has a great collection of albums documenting a trip to Baikonur and the Cosmodrome. They were taken by Chuck, a friend of mine and retired engineer, during his trip there for the launch of ECHO. This was an AmSat (amateur radio) relay satellite. He took a great deal of photos covering the flights, the locations, the integration and launch of the satellite, and some other interesting places in Baikonur.

ECHO Launch Campaign

I also had a satellite launched from the Cosmodrome. I worked on the University of Arizona's Cubesat Project and wrote all of the onboard code controlling the satellite. In the end we built four satellites, three of which were completely functional. There was RinconSat 1 and 2, AlcatelSat, and an engineering model. The cubesats are small 10cm cubic satellites with a control/computer board, power board, radio board, an array of 24 sensors, and an array of solar panels on the outside frame.

The hardware was quite simple, but we didn't need anything super fancy. The computer board had a PIC microcontroller and using the I2C bus could communicate with two 32 kB FRAM (ferromagnetic RAM) storage chips, a clock chip (which kept time in binary coded decimal), and the sensors. Unfortunately, at the time there were no FOSS PIC compilers so we had to use a Windows/DOS/command line compiler which was really lousy, but we managed to work around the bugs as we found them.

I was very happy with our final results. We did a great deal of testing on the ground and did radio testing by taking the satellite up to the top of a nearby mountain and then communicating with it from our groundstation. The onboard code supported one- and two-way communication and had several modes of operation. It had a default mode in case communication could not be established, a real-time mode that would broadcast a constant stream of sensor readings for a period of time while the satellite was overhead, and a regular mode that would collect readings based on a schedule and store them in the FRAM storage which you could then later command the satellite to transmit to you.

After many delays, we finally got a launch opportunity. We sent RinconSat 2 and AlcatelSat to CalPoly where they were integrated with other cubesats into the launch mechanism. They then sent them to the Baikonur Cosmodrome for the launch. At first, everything seemed to be going well, but we soon found out that it was far from well. The first stage of the rocket failed to separate and the rocket crashed 70 km downrange in a flaming crater, destroying all of the cubesats as well as the far more expensive primary payload (some sort of communications satellite). Sigh...

We don't have any sort of web site, sadly, but one of these days I need to gather up all the photos, documents, source code, and other random stuff I still have access to and make a nice web page for our late satellites.

I'm typing this on a Droid 3 and it meets many of those requirements. It is most notably lacking out-of-the-box root, but I fixed that soon after getting the phone. I am still rather pissed that the bootloader is locked, so even when I change the ROM I can't change the kernel. And, with it rooted, wifi tethering is open to me if I wish. The body is also fairly rectangular. Except for the rounded corners, it's quite straight.

It would be nice to have Debian beneath Android, though.

This has always bugged me a lot. For most games, I personally think it looks better with motion blur turned off. You almost always get that option with games on a PC, but rarely can it be changed with console games.

On consoles, I think one of the reasons it is used so frequently is to help mask low or dipping frame rates. The 3D on consoles seems to be designed such that games can enable motion blur without hurting the rest of the 3D rendering performance. Most PC video cards, however, seem to take a hit when it is enabled. But, perhaps that is no longer true with newer cards? Or maybe it is only noticable on a PC because the resolution is much higher?

I've read that most console games only render internally at a size close to 800x600 and then scale to "HD" sizes... which I suppose makes sense when you consider how many years old the PS3 and XBox360 3D tech really is.