Re: .Net and the Linux port
"MarkN" <m@n.com> wrote:
>
>So the usage >of MS.Net, and thus careers in it, depends on a few things
and how they pan out:
>
>1. The rise and widespreed acceptance of Linux - will it?
>2. Windows and how the licensing and closedness and new (future) security
>'features' (Paladium) affects its acceptance.
>3. How well will the Open Source version of .Net succeed and how useful
will
>it be?
>4. Which FUD and which truths will be believed and accepted?
>5. When and how well will the economy recover?
>6. How many MS shops will move to MS.Net and when will they do it?
>
This is a good summary. Regarding the perennial Linux question (will it
become widely accepted) this is a tough one to call. I found this recent
discussion particularly relevant:
http://www.linuxandmain.com/modules....rticle&sid=128
Basically, it discusses the contradictory objectives of some of the Linux
community members - - that is:
a) Linux is my hobby, I do it for free, outsiders should not complain about
missing features or usability or whatever because they're not paying me.
b) We want Linux to become accepted by everyone, not just techies who are
willing to read newsgroups, modify code and recompile to get what they need.
Both statements are perfectly fine taken individually, but taken together
they just don't make sense. This is the core issue for Linux adoption and
it will be interesting to see how this plays out . . .
Elena
Re: .Net and the Linux port
Here is an article on Linux acceptance.
http://eservercomputing.com/mainfram...dex.asp?id=254
I think the big twist and what may spead the acceptance of Linux is the support
it now has from IBM, Oracle, etc. Also the formation of UnitedLinux.
I know what you are saying about the contradictory objectives. But is that
any better than a company who ignores (or seems to) major problems with their
software until enough complain or they feel threatened? And being a user
of that software, you can't even fix the problem even though you know how?
With Linux you can. And most problems are fixed quickly. Ok, enough of
that - I wish to avoid getting of on that.
Just everyone keep your eyes open and don't caught like the COBOLers, etc.
And don't believe all the marketing hype. And remember the best man[tool/company/vcr]
doesn't always win.
Study hard and diversify.
Mark
Re: .Net and the Linux port
The biggest hurdle is that, the developers in the UNIX world usually "hate"
Microsoft to the bones. They may not use it even though the port becomes
available.
simon.
"Elena" <egermano@comcast.net> wrote in message
news:3d2c39fb$1@10.1.10.29...
>
> "MarkN" <m@n.com> wrote:
> >
> >So the usage >of MS.Net, and thus careers in it, depends on a few things
> and how they pan out:
> >
> >1. The rise and widespreed acceptance of Linux - will it?
> >2. Windows and how the licensing and closedness and new (future) security
> >'features' (Paladium) affects its acceptance.
> >3. How well will the Open Source version of .Net succeed and how useful
> will
> >it be?
> >4. Which FUD and which truths will be believed and accepted?
> >5. When and how well will the economy recover?
> >6. How many MS shops will move to MS.Net and when will they do it?
> >
>
> This is a good summary. Regarding the perennial Linux question (will it
> become widely accepted) this is a tough one to call. I found this recent
> discussion particularly relevant:
>
> http://www.linuxandmain.com/modules....rticle&sid=128
>
> Basically, it discusses the contradictory objectives of some of the Linux
> community members - - that is:
>
> a) Linux is my hobby, I do it for free, outsiders should not complain
about
> missing features or usability or whatever because they're not paying me.
>
> b) We want Linux to become accepted by everyone, not just techies who are
> willing to read newsgroups, modify code and recompile to get what they
need.
>
> Both statements are perfectly fine taken individually, but taken together
> they just don't make sense. This is the core issue for Linux adoption and
> it will be interesting to see how this plays out . . .
>
> Elena
>