If Programming Languages Could Speak
HealYourChurchWebSit writes "BurningBird's "The Parable of the Languages" offers a delightfully playful answer to the the question, "[what] if programming languages could speak, really speak, not just crunch bytes and stream bits, they would have much to say that is both wise and profound.""
I've found a mirror here
I hope you enjoy it as much as I didn't.
Well, the site got crunched. Here's a text-only mirror:
Click here
Am I a hipster-doofus?
Well I wouldn't make such conclusions quite yet. Firstly, shortly after Visual Studio.NET (which in essence is .NET) was released, there was a buffer overflow found in, ironically (truly ironically), a security feature intended to thwart buffer overflows. Secondly, there have been 2 service packs already for the .NET Foundation, and on top of that it has been very lightly exercised (extremely few websites use it, and I've yet to see a single commercial or even big shareware or freeware .NET app): Give it time. I will bet you, putting money on the table, that there will be numerous exploits for .NET as time goes by. No malice intended towards Microsoft, but rather it's just the nature of large scale software.
P.S. I love asp.net, Visual Studio.NET, etc, but I also know that Microsoft does not have a stellar security history behind it.
Some ANSI C code of mine (this is simple stuff -- i've only been working with C on-and-off for a year or so -- I'm a Visual Basic refugee) compiles perfectly with gcc, which isn't surprising since I wrote it for gcc & linux. However, trying to do a Windows port of my program (shameless plug) with only Visual C++ available to me right now is a *real* pain. It compiles, but certain perfectly acceptable C statements get somehow FUBARed, and the program turns out weird numbers. I'm not enough of a Windows programmer to understand what's wrong, sadly. Maybe cygwin...
So VC++ and it's merry band are probably standing outside the gates laughing at the "real" standards as they try to interoperate with the de facto standards. Grrr...
I've always defined AmigaDOS as dos.library, the shell commands and a few other bits and pieces, whilst AmigaOS includes AmigaDOS but also adds intuition, exec, Workbench and all the other standard bits.