I'll let you in a little secret. Plans and schedules mean exactly dick on government software projects. You'll have idiots and imbeciles with no technical experience making major changes a week before a deliverable. You'll get reports that your software doesn't work when deployed, and find out a week later that they didn't bother to inform you that they decided to move to a completely different environment. You'll get new requirements on the day of delivery. You'll meet deadlines and won't hear anything for days or even weeks until you get some angry email from somewhere asking why a problem that was never reported hasn't been fixed yet. You'll be forced to use their dev environments, but not given the privileges necessary to actually use them. You'll get countless technical decisions made...without anyone actually consulting the technical team. And I'm just getting started.

It doesn't matter how competent your team may be. If the government side of the project is managed by a bunch of monkeys on meth, you're going to have a bad time. Double that if your company is hell bent on getting their foot in the door that they're willing to bend over backwards just to keep them happy.

And guess who gets tarred and feather when everything goes to hell? I'll give you a hint. It's not that G15 manager who needs a Garmin in order to find where to put the Charmin.

A successful government software project requires competence on both sides. It is a rare circumstance when that is the case.

I see you have a very selective memory. Please read the original plan and then follow the idiotic path of compromises that Republicans forced onto it rendering it into the watered down ridiculous mess that it is.

But then again, the democrats didn't help things either since they were so desperate to get SOMETHING through that they were willing to do just about anything without really thinking through the consequences of their actions.

And of course, the ones ultimately to blame are ourselves. Congress's successes and failures are a direct reflection of the voting population. It's not democrats or republicans. It's this bizarre us vs. them mentality that prevents anything useful or effective being done. It's not a fucking football game. The leaders we elect are supposed to get shit done, not to act like spoiled 2 year olds when they don't get their way.

It is AMD fanboy sour grapes. For some reason some people get really personally invested in their choice of graphics card. So when the other company comes out with a card that is substantially better than what their company has, they get all ass hurt and start trying to make excuses as to what it is bad. The nVidia fans did that back when the AMD 5870 came out and nVidia had no response. Same deal here. The GeForce 900 series are a reasonable bit faster than the AMD 200 series, and way more power efficient. At this time, AMD doesn't have a response, so the AMD fanboys are going on the defensive.

The real answer is, of course, buy the card that works best for your usage, which will vary person to person.

I don't see how much has happened as far as Islamization of America. Islam is still a super-small minority in America, right? I'd bet the Hindu population is growing faster, and even that's small.....

Ok, yeah, that's where you completely went of the rails lol....

A better place to begin is by gathering information. The more information you have, the easier it will be to draw good conclusions. Otherwise you are stuck asking questions like, "why else would they do it?"

Maybe, but it's a complete fail on discoverability.

No! They are leaving the features, but focusing on making a sensible default, whereas the rest is easily discoverable!

That is how he is describing it, and it is how an ideal UI should be. Gnome on the other hand wants to make anything hard impossible, not discoverable (where discoverable means the user can figure out how to do it).

The whole "needles in the eyeball" are just a stepping stone to something truly amazing.

Indeed. I was severely nearsighted all my life, after the cataract surgery I no longer need corrective lenses at all, not even reading glasses and I'm 62. My vision in that eye went from 20/400 to 20/16. Truly a miracle.

BTW, my retina surgeon said that my retinal detachment was a result of being so nearsighted; a nearsighted eyeball isn't perfectly round like a normally sighted person's eyes.

The cloud is not trustworthy, it was shown to not be many times over and no sane enterprise will allow the cloud to take over local desktops/servers.

Unless it's cheaper. Then as long as nothing happens, managers get bonuses for the savings their decisions have earned the company, and if something does, it's an unforeseeable event that was the fault of some evil haxor.

TLDs have certain requirements associated with them, unless Amazon magically also has some super special secret deal that Google hasn't told the world about after losing ... then Amazon won't be able to monopolize or otherwise use the TLD to an unfair advantage.

And yet that's exactly what Amazon will do. Even if they run their registry business as a separate department, the conflict of interests is always there. It's exactly like an ISP who also provides content has an incentive to make connections to Netflix suck.

Perhaps it would be best to simply forbid companies from expanding to arbitrary new segments?

Even MS can't say exactly what that spec is. Sure, there's an alleged standard but Word never actually followed it and in spite of over 1000 pages of documentation, it's incomplete.

Russia is independent of the USA part of the Internet to a degree you can hardly imagine. They have their own Facebook (vk), their own Google (yandex), two DNS root-server anycast instances, and even for credit cards they'll not be very sorry as Russians prefer debit cards from their own banks over Master/VISA credit cards.

Sure it'd be noticeable and some stuff would stop working, but it is certainly feasable.