Patrick Casey wrote:
Please see comments below :)
I agree about 80% with what you have to say; I find programming in
.net to be sort of like using public transport. It gets me 80% of the way
there very efficiently, but then I'm ****** and have to walk the last half
mile through the rain. .NET definitely has a ".net" way of doing things and
god help you if you want to stray from the path.
If you're willing to live within those restrictions though, it
works. I've yet to run into something I flat *couldn't* do with .net. It was
usually more that I couldn't do it the way I wanted to do it and the .net
way was very microsofty and weird. That's a question of taste through rather
than functionality in my book.
Also, (and I can't vouch for this personally because I was never a
VB jockey), my suspicion is that a lot of the .NETism that you and I think
are just f-ing wonkers, and probably familiar VB paradigms that make perfect
sense to folks who have a MS background.
I did got some comments from some .NET ex-colleagues of mine saying
exactly that!! But.... I'll believe when I see it. My experience in .NET
is that it's hard to maintain, generates non-standard HTML (and that's
important no matter what Microsoftians like to say) and it's rigid and
inflexible. The overall framework, not the C# language.
But maybe it's just me trying to work like Java....
I enjoy that as well, but I can't claim it's a business reason to
recommend an OS stack. "Hey boss, can we use java and tapestry instead of
.net because I'll get a kick out of working on tapestry and, who knows, I
might be able to contribute some code back to the commuity."
"It'll let me develop faster" is a business case.
"It'll let me develop less buggy code" is a business case.
"It's backed by the world's largest software company and we'll
always have somebody to call if it breaks" is a business case.
"It'll run 3X as fast" may, or may not, be a business case.
"I like playing with open source" is not, unfortunately, a business
case :).
--- Pat
I agree with you in that business cases are important. I have my own
company and even if I can decide to do this or that I still have to
abide to business cases. They're important on their own (see my
discussion on marketing somewhere around here).
Now, the problem is which business cases?
"It won't tie us to a single provider" is a business case.
"It will generate standard markup" is a business case (yes! it is!)
"I can modify/debug source code if something goes wrong" is a business
case (not for the faint of heart but it *has* saved me a lot of time,
and that means hours)
etc...
Those are actual problems, IMO with .NET. But more than just .NET, with
proprietary infrastructures (as opposed to propietary turn-key systems,
that are a different case).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
