I agree with your point. Most code I write has some amount of future proofing as there are usually signs that the client will want things added or changed in the future. I do limit these future capabilities to only those that can be implemented in a reasonable amount of time compared to ignoring them entirely. Anytime one codes with no thought on future changes, there will end up being a serious need to restructure or even just rewrite lots of code.

All the time, what's up with that! :)

Windows 8 blue screen has :( in the new blue screen.

I don't know if I'd blame lazy developers on Microsoft, more on the actual lazy developers themselves. Because the problem is still lazy developers. If you are going to be lazy, then only code to the standard and leave out the prefixed extensions.

Apple can't write Windows software. Have you used Apple software for Windows (i.e. Safari, QuickTime, iTunes, etc.)? It is buggy and slow.

As a developer, I say don't use the prefix on production sites. Then you don't have to worry about when to change it, as you don't have to change it.

The current standard is Xhtml 1.1 and CSS 2.1 + several Level 3 sections. Really, you can code in Html5 and use a lot of the main CSS 3 and it will work across most current browsers without resorting to prefixed extensions.

Exactly! Mod this way up.

That code is wrong, here is the corrected version: div { border-radius: 5px; } Coding to non-standard extensions is bad for everyone. If the border-radius doesn't work when coded to the standard, then it isn't going to work. So either don't use it or know that some people's web experience will be without round borders.

Not sure where you get that the kernel is identical. It is not like they compiled exactly the same source for each, there are differences. For one the Windows Phone 8 has to run Windows Phone 7 apps, so there are some differences there. Windows RT has some differences from Windows 8, they are built for different processors. There are enough core components that and app built for any one of them can be compiled to work with the others, but it doesn't just happen if the application is more complicated and uses components outside the core set.

Windows Phone 8 will run all Windows Phone 7 apps (well, 7.1 and 7.5, though I doubt there any relevant 7.0 apps still around).

But, if you mix in a random alpha numeric with random English words, you get both, and the added entropy of location of random alpha numeric characters. "borrow 9dy sendar&sought" "bing s0me googl3 and yelp" We just need to be able to use long passwords and extended character sets.

It is more likely "it makes an awful aquarium" or "my 5 word phrase"

Also, the separator for each word (or lack of separator adds another (102+-)^(3 or 4))

You skipped Wyoming, which everyone does, but our average is closer to 150 firearms each.