Knowing .NET

First off, I love reading your articles on SD Times, so thank you for writing them.

Now, as to Python and Ruby: they are both very interesting ideas but horrible languages to write any meaningful projects with. Ruby has an insanely convoluted underlying infrastructure, and Python,- oh dear where do I begin? Using tabs for blocks? No drivers for writing db apps? Even when you find db drivers, they are extremely tedious to use because Python likes only “object databases”? etc etc. Granted, programmers who use Python and Ruby are very dedicated promoters who do manage to make a lot of noise; but after all is said and done both languages are not viable enterprise-level heavy-duty software development tools, just small, curiosity-based toys. Back in the late 80′s I loved programming using Borland’s Turbo Prolog, but building a whole commercial app? – no way. Some languages exist just to be a subject of conversation but nothing more than that.

I smiled while reading your subtle swipe at C# with its “public static void…” syntax stuff, and you are right, it is not intuitive, but here is the truth: every word/command there means something, and a good developer knows the meaning and purpose of each. A developer that expects everything to be easy is just either uneducated or lazy. (I exclude C pointers from my argument. Pointers were indeed an abomination.) In real life, proper engineering requires knowledge, skill, experience, etc. Well-engineered software apps are well organized, and thoughtfully constructed. It is more about long-term and less about “hey, cool”. For example, I love PHP, but I can never treat it seriously because among other reasons, it does not require me to declare variables. That’s one of those red-flag thingies. When you see that, you know the language allows slapdash practices, and that is always bad in the long run. That is why people trust C# and Java, even though neither is perfect – they adhere to a consistent form of common sense.

My point: the reason IronRuby and IronPython are fading is because nobody is using it. It is pure software Darwinism: the crap ends up in the crap heap where all poor, weak, or unusable languages eventually go. They lie together with Microsoft’s J# and JScript and umpteen other languages, and eventually are forgotten. Such is life.

That said, I love your articles, and finally (finally!) I have added your blog to my shortcuts.

Thank you for writing for SD Times. You and Binstock are always interesting.

Respectfully Yours,

Nissim Salinas
nmsalinas@yahoo.com

PS: Python’s “tabs for blocks” is the single-worst idea, eclipsed only by Steve Jobs’ decision to make the NEXT workstation monitor grayscale only. What the heck were they thinking?!

PPS: The bestest column you ever wrote was the one about telescopes and stars. I loved it!

PPPS: If I may make a humble suggestion: use your blog picture for the SD Times articles. Your pic in SD Times makes you look like a very pale (and sick?) version of Ferris Bueller, whereas your blog pic is that of a healthy, rockin’ dude. Just a suggestion, *no* offense meant!