I must admit it's been a few years since I last used C#, and I've yet to shift from Java 7 to Java 8. Both have moved forward.

But at the point I was heavily using both, they were more alike than different. At that point, LINQ had just come out so no one was using it for production systems yet.

What amuses me is that many people rave on about how great C# is, while denouncing Java. Yet other than a few minor syntax tweaks (like the way you write getters/setters and the "?" indicator for nullable attributes), they are virtually identical right down to the API.

They're both very easy to read and code with, and if you know the packages/libraries of one you'll find the equivalent in the other in short order, with very, very few differences in the details of the APIs.

Yet C# is "great" and Java "sucks".

Go figure.

My theory is that with Crave TV and such coming on the market, people don't need to pirate everything that they used to.

There is also a new IP TV provider in Canada that isn't tied to the internet infrastructure provider. That may have something to do with it as well.

Clusters? Been out for decades.

Virtual machines? Been out for decades.

Hosted operating systems? Been out for decades.

Distributed clusters over corporate networks? Been out for decades.

The only thing "new" about the "cloud" is using the public internet instead of a corporate VPN for the network.

Well, that would be an improvement for a third-rate country. :P :P :P

No, they use drones instead of losing any of their own lives.

Let me be blunt:
Fuck 'em!

The cloud has never been anything but old technology with new buzzwords.

The question is: "What language are you writing this project in?"

The language dictates the best IDE for the job.

Let me know when they stop drawing them with FF tits and thighs and asses you could crack walnuts on.

The only reason they're thinking it has less latency is because they're only considering a point-to-point case.

Once you wire that up to the various hubs and routers of the underlying DSL or cable infrastructure, or try to send traffic to somewhere other than the end-point the microwave is connected to, your latency rapidly goes to shit.

Add in the fact that fiber can transmit over longer distances, the weather-induced degradation of most microwave links, the fact that the whole link drops when a semi-tractor travels along the highway between the two links when line-of-sight is close to the ground, the need for high and unsightly towers to get over the trees and buildings, and the final fact that microwave towers were decommissioned in Canada precisely because of all these problems, and all you can say is:

Bad idea.
Very bad idea.

What misconceptions or outright lies have become so ingrained in young people's use of technology that they need to be addressed?

Above all else, they need to be freed of the delusion that the ability to use a smart phone or tablet qualifies as "technical skills." Those devices are appliances, and using one does not confer any actual technical skills or knowledge at all.

Back in my university and high school days, it would be like someone who took a typing class claiming that they're "PC literate" because they know how to keyboard.

Details. Details.

What is the difference between impeachment and being forced to resign? That's like quibbling over whether you were forced to quit or were fired. It's a semantic detail that doesn't matter worth shit to anyone except pedantrists.

The only "guarantee" is that people will always need plumbers, electricians, and other tradespeople.

When Nixon did that, he was impeached.

Nowadays you're seriously considering electing someone who did the same damned thing Nixon did?

WTF is wrong with you Americans, anyhow?