Looking back at my old code I find that a lot of it is crap. I do find various aspects of what I've done in the past to be practices that I like to perfect in the future. The problem is, as the poster notes, that you're writing something for your employer to get a job done quickly and as long as it works at all it's good enough...next task. So, a lot of anyone's old code is bound to have a lot of rushed, poorly thought out half efforts. That said, I have found that many projects I've started on my own (and often effectively abandoned) turn out very aesthetically pleasing, though tend to get grandiose in scope or attempt the improbable (I'm smart enough to make my own 3D physics engine...I'll just whip that out...then after a month of heavy physics reading you find yourself looking into M theory instead of having any working code to speak of except the surrounding code...sigh). At any rate, I've had the luxury of having a lot of artistic freedom because I've worked with small companies, so I've explored and expanded several pet ideas into full fledged production systems, which is pretty fun.
.NET doesn't run on non-Windows machines as well as it does on Windows, if at all, whereas all those other server apps (MySQL, Apache, PHP, Oracle, DB2, Java, etc.) run fine on Windows....did you read my post?
Everyone on slashdot loves Mac OSX because you can run everything on it, Mac software, Windows software, Linux software, and even now "real" Unix software.
I ask you then to look deep within your soul and tell me why a Windows Server doesn't do the same thing on the server side...It runs MySQL, Apache and PHP, it also runs POSIX software and it runs.NET which is very popular with developers. Mono has made progress, but you typically have to modify your code to run on it, whereas it runs fine on Windows. Plus, not to bust anyone's bubble, but real world apps these days still run on the "Big Boy" database systems like Oracle, SQL Server, and DB2...all of which run on Windows.
Don't get me wrong, I have a real affection for Linux, but I also have a family to feed and it's easy to make a sale with a server system that runs on Windows. It also very well could prevent a sale if the client only runs on Linux because your application is likely not to be the only applicaiton they are running on the clients. Then you get into the whole website vs traditional application battle and there again a webpage still isn't as functional as a real application (not yet anyway).
Slashdot Mirror
Looking back at my old code I find that a lot of it is crap. I do find various aspects of what I've done in the past to be practices that I like to perfect in the future. The problem is, as the poster notes, that you're writing something for your employer to get a job done quickly and as long as it works at all it's good enough...next task. So, a lot of anyone's old code is bound to have a lot of rushed, poorly thought out half efforts. That said, I have found that many projects I've started on my own (and often effectively abandoned) turn out very aesthetically pleasing, though tend to get grandiose in scope or attempt the improbable (I'm smart enough to make my own 3D physics engine...I'll just whip that out...then after a month of heavy physics reading you find yourself looking into M theory instead of having any working code to speak of except the surrounding code...sigh). At any rate, I've had the luxury of having a lot of artistic freedom because I've worked with small companies, so I've explored and expanded several pet ideas into full fledged production systems, which is pretty fun.
.NET doesn't run on non-Windows machines as well as it does on Windows, if at all, whereas all those other server apps (MySQL, Apache, PHP, Oracle, DB2, Java, etc.) run fine on Windows....did you read my post?
Everyone on slashdot loves Mac OSX because you can run everything on it, Mac software, Windows software, Linux software, and even now "real" Unix software.
I ask you then to look deep within your soul and tell me why a Windows Server doesn't do the same thing on the server side...It runs MySQL, Apache and PHP, it also runs POSIX software and it runs .NET which is very popular with developers. Mono has made progress, but you typically have to modify your code to run on it, whereas it runs fine on Windows. Plus, not to bust anyone's bubble, but real world apps these days still run on the "Big Boy" database systems like Oracle, SQL Server, and DB2...all of which run on Windows.
Don't get me wrong, I have a real affection for Linux, but I also have a family to feed and it's easy to make a sale with a server system that runs on Windows. It also very well could prevent a sale if the client only runs on Linux because your application is likely not to be the only applicaiton they are running on the clients. Then you get into the whole website vs traditional application battle and there again a webpage still isn't as functional as a real application (not yet anyway).