It's not necessarily dying out. Look around at a lot of the young people heading into the profession, there's a lot of BPFH (Bastard Programmer Fro...why am I explaining that on slashdot?) wannabees out there who see incomprehensible code as 'job security' and a sign of their '1337 sk1llz'.
Admittedly I tend to just sketch out a basic overview of any project I set out on then dive straight into the code but my projects are small scale so I can get away with it:). I do tidy things up and comment before declaring them done though.
...been doing this for years anyway? My code development cycle has always been...
1. Write code to use function/procedure.
2. Write function/procedure.
3. If function/procedure==fucked return to 2 and unfuck.
4. Once it works, tidy it up.
Now it appears someone else has added steps 5 and 6...
5. Write a book about it.
6. Profit!!!
Ok, we all know that's the instinctive reaction of many linux users when someone mentions The Beast but keeping it simple for developers (and dummies like me) by turning.NET into a cross platform standard is no bad thing. Aside from killing Java (not a troll, Java's a nice idea but both the MS and Sun VMs suck) it will provide a platform to build on for future integration of MS products with linux. I'm not talking about MS Office on KDE nor do I mean MSLinux2005 (steady, it's not real!), I'm talking about ways to make linux and Windows work together and MS WILL eventually have to take that into account to maintain their margins. If a big fish like IBM gets behind the Mono project this could be just the thing to start that process off.
...but there's an NDA associated with getting them. It looks to me like De Raadt doesn't want to agree to the terms and threw his teddy out of the cot when Sun told him 'tough luck then'.
Slashdot Mirror
b) Believe that a GUI is a little thing you spend a couple of days on after you finish the application
;)
A couple of days? If a variable dump's good enough for me it's good enough for the proles
It's not necessarily dying out. Look around at a lot of the young people heading into the profession, there's a lot of BPFH (Bastard Programmer Fro...why am I explaining that on slashdot?) wannabees out there who see incomprehensible code as 'job security' and a sign of their '1337 sk1llz'.
:). I do tidy things up and comment before declaring them done though.
Admittedly I tend to just sketch out a basic overview of any project I set out on then dive straight into the code but my projects are small scale so I can get away with it
...been doing this for years anyway? My code development cycle has always been... 1. Write code to use function/procedure. 2. Write function/procedure. 3. If function/procedure==fucked return to 2 and unfuck. 4. Once it works, tidy it up. Now it appears someone else has added steps 5 and 6... 5. Write a book about it. 6. Profit!!!
Ok, we all know that's the instinctive reaction of many linux users when someone mentions The Beast but keeping it simple for developers (and dummies like me) by turning .NET into a cross platform standard is no bad thing. Aside from killing Java (not a troll, Java's a nice idea but both the MS and Sun VMs suck) it will provide a platform to build on for future integration of MS products with linux. I'm not talking about MS Office on KDE nor do I mean MSLinux2005 (steady, it's not real!), I'm talking about ways to make linux and Windows work together and MS WILL eventually have to take that into account to maintain their margins. If a big fish like IBM gets behind the Mono project this could be just the thing to start that process off.
...but there's an NDA associated with getting them. It looks to me like De Raadt doesn't want to agree to the terms and threw his teddy out of the cot when Sun told him 'tough luck then'.