Quote:
Originally Posted by Dean
Scott, I do not claim to know what you do on a daily basis, but I work with developers on at least 5 different platforms probably using 10+ thing I generously call "languages", and god knows how many different development environments. Those environments run from good old text editor - compiler, to pure object oriented GUI with no access to the actual underlying code and everything in between including .net. So what exactly is your current experience with development outside of .net in the '00s?
Based on my experience in the gaming industry as well as working with major consulting groups and vendors of middleware, hardware, and applications on a daily basis, the .net environment continues to gain traction, but is not the dominant solution for enterprise applications. It is obviously the major player in the Wintel space, but despite Bill's wishes, the majority of enterprise applications do not run on his products.
I find it hard to believe that your "development tool" already has all the "libraries" you might need to build an application that uses for example, say... EMS or Rendezvous messaging? And how does it know if you need to use the PGSQL DAL? Clairvoyance?
The right tool for the right reasons... The SCCA web site does not need a $100,000 content management system, utilization analysis, or intrusion detection.
Front page and NVU which are what most of the old web site was created in are perfectly acceptable tools for developing and maintaining small web sites, and Word and Excel are perfectly acceptable tools for text and spreadsheet types of content. Just because you don't like those tools doesn't make them unsupportable. Attempting support them in a raw text editor may be near impossible, but so what?
You just can't admit that for the purpose of publishing the bloody schedule on the "temporary" web site, Word's HTML output would have been perfectly acceptable and taken you those same 2 seconds you took to make the fix in your hand coded HTML "index" page...
So be it.
I'm done with this topic.
|
I'm not going to bother to re-write my resume just so I can reply to this post, but I'll tell you this: the .NET 3.0 technologies like WF, WCF, WPF, Enterprise Library, etc, are going to *crush* Linux/Unix based systems in the next 5 years unless they get on the ball 2 years ago and come up with something better.
And it's true, if I need access to something like PGSQL (though it'd be a massive step backwards from the ORM tools we're using in conjunction with MSSQL) I'd just pick it off the list of supported DALs. And for something that's not supported, I just get the installer and add it to the environment because 9 out of 10, the tool supports Visual Studio 'cause if they don't, they'll be out of business in 5 years.
And you're right, the SCCA website doesn't need an expensive CMS, it needs one person with a text editor and knowledge of PHP/MySQL. Frontpage would be a minimally acceptable means for maintaining the site if FP extensions were installed on that server... but considering the number of documents that are carrying the MS Office icon headers in them, I'd say you weren't maintaining it w/ FP, you were using word and excel, and bloating the site as a result.
As far as publishing the schedule on the temporary site... you just nailed it... it's temporary. If I wasn't waiting around for the DNS change, this page wouldn't even have existed. Like I said, at 1am when I was finishing up, I didn't feel like doing *any* file conversions, I just uploaded everything I was given as is. I'd much rather be in bed w/ my GF than freezing my ass off in the kitchen opening up word to save off a bloated .html file. Plus if I'm going to spend time on it, I'm going to do it right, because I take a little pride in the work that I do and don't feel good about half-assing things if there's a better solution out there.