Re: Microsoft and trust
- From: "Schmidt" <sss@xxxxxxxxx>
- Date: Thu, 27 Mar 2008 18:24:04 +0100
"Bill McCarthy" <Bill@xxxxxxxxxx> schrieb im Newsbeitrag
news:D72FCB2E-FBCD-4C0F-AD01-6D2FBF5CA487@xxxxxxxxxxxxxxxx
No, completely wrong.Wine is not an emulation in the sense of a VirtualMachine -
it is simply the WinApi-layer on top of a modern
operatingsystem.
Basically the same thing as the WinAPI-32-layer
on top of a 64Bit-OS from Microsoft.
As I said, you mean via wine. .NET apps can also run on
Linux using wine and the Windows version of the framework.
Try it with your own "One-Click-Deployment"-package -
or try it with a SharpDevelop-Install-Package - both
will not work.
But that one is *Mono-based*, and is BTW not yetWhat do you mean with that?(e.g. SharpDevelop cannot run on Linux
today, the VB6-IDE can).
You're making that up.
It works here - and the .NET-based SharpDevelop does not.
http://www.monodevelop.com/MonoDevelop_1.0_Released
at the level of Sharp-Develop (which is a .NET-based IDE).
What "stagnation" are you talking about?IMO that's also a good example to show, that it's worth,
to give technology (in this case COM) some time to "grow"
- and regarding this example - to spread to other platforms
as well - then things start to become interesting.
This isn't a case of time to grow, more time to stagnate
so as there are wine tweaks for it.
I'm talking about, that we not even reached the limits
of COM-based technology - that developers not
even "mastered" all the capabilities, which this "old"
environment has to offer.
It is "that old", that even the newest MS's "Bread-and-Butter"-
Apps are based on it - no .NET in sight there.
But "all the other developers out there" should of course
use the "new stuff", because it's "better for them" - but
apparently not for themselfes.
..NET is (beside making money over the "it's new, buy it!"-
marketing-channel) the only chance for MS, to keep
the open communities on distance, to keep their "monopoly-
position" intact.
But those are catching up even at this new front pretty fast
(Mono) - so MS is forced, to throw out even more
"New-Tech" even faster (WinForms->WPF->Silverlight ...
or Remoting/Webservices->WCF->Indigo->SOA) - a
cycle which can only get faster and faster - with the developer
left alone with all this "fast-FUUD", which has shorter and shorter
expiration-dates - and if MS cannot handle that any more,
they probably get out their "patents-bat"...
No, thanks!
I will look at all this stuff for another couple of years, investing
my time into getting better at *programming* in the meantime -
and not into "exploring new IDEs or Tools" or even their Beta-
Versions every few months.
That's why I try, to let the MS-boat sail - they are already
on a race to nowhere - there is no chance for them, to compete
with open and community-driven solutions over a longer period
of time, because at some point ... good-enough-technology
is good-enough-technology. That's what many Developers or
Users will realize over the next years, being tired of all that
Hy(pe)Tec.
I'm sure we will see (after MS realizes, they cannot "move
ahead" further at this speed), that they come out with "their
nasty things".
And that'd be the point, where their ship will start to sink fast.
Olaf
.
- Follow-Ups:
- Re: Microsoft and trust
- From: Bill McCarthy
- Re: Microsoft and trust
- References:
- Microsoft and trust
- From: Michael C
- Re: Microsoft and trust
- From: Bruce W. Roeser
- Re: Microsoft and trust
- From: Michael C
- Re: Microsoft and trust
- From: BeastFish
- Re: Microsoft and trust
- From: Michael C
- Re: Microsoft and trust
- From: BeastFish
- Re: Microsoft and trust
- From: Stefan Berglund
- Re: Microsoft and trust
- From: Bill McCarthy
- Re: Microsoft and trust
- From: BeastFish
- Re: Microsoft and trust
- From: Bill McCarthy
- Re: Microsoft and trust
- From: Karl E. Peterson
- Re: Microsoft and trust
- From: Schmidt
- Re: Microsoft and trust
- From: Bill McCarthy
- Re: Microsoft and trust
- From: Schmidt
- Re: Microsoft and trust
- From: Bill McCarthy
- Microsoft and trust
- Prev by Date: Re: certificate revocation list
- Next by Date: Re: Microsoft and trust
- Previous by thread: Re: Microsoft and trust
- Next by thread: Re: Microsoft and trust
- Index(es):
Loading