What problem have you ever had with indent-based parsing?

Many many people have a problem reading other peoples' C and C++ code because of how it is not always enforced and allows some incredibly poor legibility.

You may not personally have this problem *writing* code but you've almost certainly had it when reading code.

Not all Python is readable, but forcing programmers to use good style is one of the first problems in a braces-based parsing environment. Python just formalized it.

Could have been worse? Python is a fantastic first language to learn how programming is done, especially in the context of getting another job done (Science, Math, etc.)

What percentage of their total hosted IPs are illegal or malware?

Sounds to me like the old "Windows has more viruses because its more popular" argument, used against NO-IP.

I can't comment on the file format issue in Office, as I'm not familiar with that.

As far as DirectX goes, I do recall how they released DX 10 on newer platforms (Vista and up). Personally, I think it was a stupid decision, because it limited the potential adoption of DX10 rather than providing an incentive to upgrade to Vista as they hoped. They're pulling the same boneheaded decision to limit the latest DX release to the Windows 8.1, if I recall correctly. Again, trying to shore up a crappy OS release using DirectX will do nothing but cause DirectX to stagnate. The OS's will be replaced in their own sweet time. This seems to be a more recent trend of Microsoft's, and it's a bad one.

I think that the examples you cite are bad decisions on Microsoft's part, not because of what they did, but because they simply did it too soon. I think it's reasonable for them to stop developing software and platform updates for their older software at some point, but with DirectX 10 it sort of had a backlash effect. Even today, overall DX11 use is often paired with a DX9 compatible rendering engine simply for legacy WinXP support, even though any modern video card has long had DX11 support in silicon. We're only now seeing a trickle of DX11-only games starting to come out, all because of that decision. Well, that and the fact that the Xbox 360 was roughly a DX9-equivalent machine.

So yeah, some good examples there. I was thinking mostly in terms of 3rd party application compatibility, for which they have a really good record (i.e. you can pretty much play any DirectX videogame ever as long as it was properly written, which I think is pretty amazing). But they've done some fairly silly things with releasing their own software and platform updates.

Yeah, that was the weird part. I lived close enough to feel the blast, but the winds blew all the ash east (I lived north of it), so didn't see a bit of the stuff. Felt bad for some folks in eastern Washington, who got blanketed by several inches of ash, if I recall. Fortunately, they're much better equipped for snow removal than in Western Washington, so that was fortunate. I'm guessing by the time it got to Texas it was a much lighter dusting? Still pretty impressive.

Sorry, I meant currently active volcano. Unless I missed a major geological event, I'm presuming there aren't any currently active supervolcanoes.

Agreed. The flat, ugly UI is just nasty, and they tried to justify it by explaining how the shared UI would save on battery life. My desktop and it's insanely powerful video card doesn't give a shit about battery life on some Windows phone, and that's not a valid reason to uglify your desktop OS. It was a stupid excuse then, and they still haven't retracted it.

I'm sort of looking for a revival of an attractive UI as a touchstone to see if MS is really recanting all the idiocy involved with Windows 8. It probably won't prevent me from buying Windows 9 if I get new hardware, but I'll be damned if I pay for an upgrade to an OS I can't stand looking at. Call me shallow, but when you spend ALL DAY EVERY DAY on the damned OS, I'd like to at least not cringe when I look at it. Besides, there isn't a real compelling technical reason to upgrade at this point either.

Only to about 90% of home computer users who still run Windows applications and such that don't work on other operating systems. On the server, it's a bit more balanced, but Windows is still a major player. And of course, Windows is a relatively small player in the smart device market (a bit more than Linux on the home desktop, for comparison).

If you think Windows isn't relevant, you're living in a *nix or apple bubble. Good for you, but don't mistakenly project your version of reality onto the rest of the world.

You forgot to quote "improvements".

BTW, when has MS ever created incompatibilities with old versions for no reason? I assume you're talking old versions of software? They've historically jumped through ridiculous hoops to provide backward compatibility. It's an area in which they've actually done a rather outstanding job, in my opinion. There's plenty of reason to criticize MS, but seriously, backward compatibility is not one of them.

Why? I'm not in some personal relationship with them. I buy operating systems and other products from them. If they're good, I buy them. If not, I don't, and wait to see if they'll improve, or find an alternative. Why should I worry about their long-term survivability? It's not as though someone wouldn't fill up the market share should they disappear tomorrow. And let's not kid ourselves - MS could completely stop developing new products and they'd probably be around for another decade at least.

Also, as much as I disliked Windows 8 personally, calling it a "horrific mistake" and a "monster" smacks a bit of hyperbole. Many users actually like Windows 8, and honestly, the ones most hurt by the product was MS's bottom line. Other than the UI and usability blunders (and let's not kid ourselves - they're huge blunders), it's actually a fine OS.

I'm betting they did a lot of focus testing, but ignored the result of them at a very high level. There was too much momentum in the wrong direction (the idea that touch/metro should supplant the "legacy" desktop in their main OS) to change it by the time consumers got in front of it.

In the end, the market forced them to acknowledge what the focus groups were probably telling them all along.

You're conflating the issue, because there are two different products and two different markets (game developer kits are typically NOT the exact same hardware as the final product). It makes no sense to expand the developer supply (at potentially enormous cost) to meet the consumer demand. The issue is that developer kits are being taken out of the developer market and being sold to consumers, where it does the company absolutely no good at all.

Developer kits are produced in limited supply at greater costs because the final hardware is likely not ready for manufacturing yet, or else large-scale manufacturing facilities are still being set up. Don't forget that the laws of supply and demand don't exist in some abstract form, especially for manufactured goods. You seem to be ignoring the realities involved in the massive initial infrastructure costs in setting up physical assembly lines, and the inevitable ramp-up time that involves.

I'm not sure how to explain this any more clearly.

"Monster Volcano" is perhaps a bit overstated, but comparing it to a super-volcano-potential such as the Yellowstone Caldera is perhaps a bit unfair. After all, no volcano in the world today can really compare to the potential of that one.

I live nearby (relatively speaking), and got a chance to see the devastation first-hand within the first year or two after it occurred. The forest service built a viewing station where you could look out over the devastated landscape, and, even neater, watch the forest start to grow back. It's easier to dismiss it as geologically minor when you haven't personally seen the miles and miles of trees snapped and laid down like so many matchsticks. On a human scale, it's incredibly massive, and was damn impressive to see.

I lived quite a bit further away, about an hour north of Seattle, but we actually felt the blast as a minor tremor. Someone in my family actually joked "Well, there went Mt St Helens". There was quite a bit of news about a possible pending eruption, of course. We were pretty shocked when we heard what had actually happened though.

The last thing I want is my industry to become unionized. I'd prefer to negotiate my own salary rather than be paid some standard scale based on seniority, etc, and pay union dues for the privilege. Maybe that's attractive to some, but not to me. But then again, I'm okay with a higher risk-reward ratio than many, since I threw away a very attractive and well-paying job for a chance to make my own game.

Keep in mind that not every company is like EA. While "crunch time" horror stories abound, there are companies out there that promote a healthy work-life balance as a selling feature of the company, like my last company. I think that more companies are realizing that forcing your best people to burn out on death marches doesn't produce better products and simply makes your best talent flee. From those inside EA, I heard that the "EA Spouse" story helped to turn things around inside the company, although I've only heard this third-hand. I've witnessed myself how a team forced through an insane crunch all but disintegrated at the conclusion of the project. I had a friend who worked at Sierra On-Line, and suffered for many years under incredibly poor and abusive management practices. Eventually, there tends to be something of a Darwinian process at work, where a company will get a very bad reputation inside the industry, and it suffers as a result. I think that this is one of the reasons EA had to clean up its act - you couldn't have paid me or a number of my friends any amount of money to work there.

Many former devs have started at companies with these stupid policies, and have vowed not to make the same mistakes (like my last company, in fact). They understand that "crunch time" is really nothing more than an admittance of poor planning at the management level, or poor execution at the developer level, or even simple exploitation. In well run shops, a certain amount of ramping up is inevitable at the conclusion of a project, but extended death marches are all but an admittance of a poorly run development cycle.

I'm fortunately at a point in my career where I can afford to pick and choose my employer, and can ask questions such as "what's your company policy on work-life balance and extended crunches without overtime pay?". It's harder for someone trying to break into the industry.

What's worse, to me, is when I hear other developers bragging about their death marches as though it's some sort of fucking rite-of-passage or some heroic war story. No, idiots, it just means you were being exploited. Granted, some developers (especially young, single devs) don't seem to mind having no life outside of work, but that's not acceptable to many of us. The sooner that permissive mentality dies a quick death, the better off the industry will be.