Yeah, I'm a huge fan of desert.

I dislike .Net. I enjoy perl/python more.

I work on a .Net app now. It has tons of complexity that any other app has, if anything more complexity because of the requirements put around you.

Perl and Python are like poetry. You can do whatever you want.

.Net is like a haiku. You have limitations, but often times those very limitations are what allow you to focus on the true meaning of the code, and what it should be doing.

I think there is some level of truth to the article, but it's overstating it, which is clear.

"Why we don't hire .Net programmers" turns into ".NET on your resume isn’t an instant showstopper. " turns into "If you are a startup looking to hire really excellent people, take notice of .NET on a resume, and ask why it’s there."

So ask why it's there. Just like ask why Python is there, or ask why Perl is there.

So really, what you're saying is, it's important to ask why they programmer in the particular languages they choose, and use that information to determine why they do what they do. Prefer people who do it like a hobby as opposed to those that do it as a job.

Great. But what does that have to do with .Net? Oh yeah, you just don't like it.

That's fine, I don't either but I don't immediately think a programmer is bad because they use .Net.

I think that they are bad because they use PHP.

.... both are not unique to the individual that created them. They both would have been come up with by other people.

Very interesting, I know I need a game viewer for my online simulation football game http://deeproute.com

Having a hard time deciding what to use. I've installed and messed around with Unity 3d, which seems like a lot of overkill as I just want a viewer, not an interactive game.

Something like this seems like it might be more up my alley. Going to start reading the docs.

I run an online Football (american) sim, and I am sitting here dreaming up how to use it.

I hadn't considered the stats, that's interesting. Same could be said for the draft, and free agency.

Both are really hard to order, and see useful data that way. I'll have a lot of variations though, and a lot of items. Just the draft is 384 rows(players)

Not sure how appropriate this is to American Football, but it'd be a neat way to transform between different team formations that the user wants to try.

That's true, I hadn't considered that. You could also group them in some interesting ways like that.

The thing is, I wouldn't want to move pictures like that though. They'd actually be tables to move like that, so the user could move the tables around, and then make selections within those tables.

You're always making some choice with an American Football game. A lot of ordered data is what it comes down to.