You know that Public Knowledge are the good guys, right? They are the guys fighting for consumer rights. How do they know about this? They work in Washington. Such news gets around quickly, particularly when news organizations are going to ask around for quotes.
I have a friend of mine who works for them. If they say that they can work with this guy to fight for our rights, I tend to believe them.
Sorry, but every single phone OS currently out there don't serve my vision for what I want from a portable OS. All them seem to be weak OS just built to serve the AppStore mentality, locked down so to do anything like backing up your phone is a PITA.
Maemo was the first phone OS that I actually felt was a full-fledged computer OS, that had the flexibility to do what I wanted to do. It fed the dream of having a mobile computer in your pocket. Android feels like an appliance in comparison.
I'm not saying that Maemo/Meego would have solved Nokia's problems, but abandoning all home-grown solutions basically put them in the large pool of manufacturers making generic phones, with little to differentiate them. While going with Windows Phone does do that, it does it for the wrong reasons basically telling everyone that you are an also-ran. Personally, I think there is a place in the market for a Meego-like phone. Those of us who want a computer in our phone and don't want to buy into the appstore mentality.
Symbian was doing well, and I don't think his argument was that it was ultimately a winning strategy to ride Symbian. What he's making a point of is that Elop's "Burning Platforms" memo quickly killed Symbian, which was bringing in money for Nokia. People knew after that that there was no future in Symbian.
I pretty much knew at that point that Nokia was doomed. They pretty much killed everything that made them money, for a weak platform that they wouldn't even have a phone out for almost a year. Even a moron could see that. While things did have to change at Nokia, Elop pretty much destroyed most of the phone division, with little to show for it.
Visual Studio is a nice IDE, but it isn't without issues. I was using 2010 on my last project, and the memory footprint was huge (1GB for the project I was working on.) Also, it would glitch on occasion, causing me to shut it down and reload.
It does seem to integrate nicely with Subversion, tho, which I like.
As someone who works in the government contracting realm, I do find this attitude frustrating. I have found in general that government contractors do tend to be patriotic and want to do a good job in serving their government. Many are former military people, so the "disdain" just doesn't exist for most contractors. Also, most of them damn well know that there isn't endless money, which is why there is always a lot of work put in finding new work.
Not to say that government contracting is perfect, but in general they do a good job serving the needs of government. Now, you can question whether those jobs need to be done at all, but that isn't a question for contractors, who are mostly there to do what their customer wants. Most of the faults of contractors are similar to the faults of most private enterprises.
Course, the problem with car A is that when things go wrong you either can't fix it yourself or you have to pay thousands to fix it. Sometimes, it is because of all of that stuff that makes is "simple" that makes it complicated to fix.
This seems to mirror my experience with Android, when you have to do something beyond the bounds of just normal usability.