Posted by
CmdrTaco
on from the another-brick-in-the-wall dept.
ceejayoz writes "MSNBC has an interesting article about the Mono project, saying that the 'volunteer effort
could oblige Microsoft to work with Linux'."
They say this as if it's negative for Microsoft...
by
ergo98
·
· Score: 4, Interesting
IMHO mono has been a great asset for.NET adoption: Previously, one of the primary "sales" problems in encouraging.NET adoption was the fear that it ties the customer to a single vendor solution (and this is often heavily played up when it goes against Java, for instance). Mono offers one the ability to offer a rapidly developing alternative in case of ridiculous FUD circumstances often imagined in efforts to detract from Microsoft products (i.e. "What if they withdraw all their products and you have to give your firstborn to use it! Then what!").
The article just starts off with the best quote which really sums everything up: "I don't it's ever going to wipe out Microsoft, but it's going to be a fairer universe.".
Nobody could reasonably expect a project like this to have significant impact on a behemoth like Microsoft, but at least other platforms won't get shut out of a developing market. I'm glad Miguel at least has this realistic view.
--
Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
Move along...nothing to see here
by
jayteedee
·
· Score: 5, Interesting
This is a weak story. A point is made about MS being forced into compatibility, but no facts to back up the claim. Journalism at it's finest. I'll make my own conjecture: Microsoft will put out a compatible/standard product when they see SIGNIFICANT decrease in market share or lost revenue. They haven't got X-Box right, nor Windows CE, but a few billion dollars later, a few strong-arm deals later, a few revision later, they'll have a story and a product and the sheep will make it a standard.
-- Religion and science are both 90% crap..but that doesn't negate the other 10%.
Mono is a platform
by
AirLace
·
· Score: 4, Interesting
Mono is doing very well indeed as a platform independent of.NET or the tie-ins that Microsoft is traditionally associated. There are already several independent Gtk# applications popping up and the ASP.NET implementation is showing real promise. There's a new page of screenshots here. The Gtk# debugger and documentation browser are fairly complete and have been developed in a minimal time-frame thanks to C#. Other pages worth looking at are gsirc and Platano.
Basically, what these pages show is that Mono is less like Wine and more like a complete new development environment for Linux that also has cross-platform ties. There's lots of innovation going on in the Mono community and that's filtering down into projects like GNOME and KDE through Gtk# and Qt#, for example. I say it's all good.
Mono commoditizes .NET
by
Lodragandraoidh
·
· Score: 5, Interesting
Mono turns.NET into a commodity - so you won't have to bow to the altar of Microsoft in order to use it. That doesn't sound like a bad thing.
It looks like just another tool for the developer; don't think its going to make java go away anytime soon...
Now, Microsoft may look at this from two different perspectives: historically, it has been Microsoft that commoditized other people's standards and reaped the benefit - they might not take to having the roles reversed very well. On the other hand, this could help.NET get more early adopters - in which case it does seem to benefit Microsoft.
--
Lodragan Draoidh The more you explain it, the more I don't understand it. - Mark Twain
I'm taking part in a Microsoft sponsored contest at my university currently, the rules dictate that we have to use one of the.NET technologies (ASP.Net, C#, VB.net etc). However the rules specifically state that we cannot use open source CLRs such as Mono and/or Rotor. I just find it odd that the article talks about how Mono may help gain MS support, but at the same time MS seems adamant at keeping us from using it.
Then again, I go to Ohio State. What do people out in Ohio know:)
Mono allows developers to switch
by
manyoso
·
· Score: 5, Interesting
Mono and Portable.NET really shine in allowing former Windows developers to get involved with Linux and still have a comfortable and semi-familiar place to start.
I don't see Mono or Portable.NET as cross-platform technologies (unless you mean cross-platform across Unices) because Mono and Portable.NET grew up on Unix and will be used here the most. Besides, Microsoft has simply created too many API's and hence the barrier to a *quality* cross-platform development environment is too great.
Rather, Mono and Portable.NET will be good for rapid prototyping and as a conversion tool for Windows Application developers. Is also important for providing an alternative when the great migration begins of Smart Clients begin from Windows to Linux.
As for the rest of the article: Yah, I'm sure the Microsoft developers who created.NET are enthusiastic about Mono, but the higher-ups (see: PHB's) have no love for Mono or Linux.
Some people from Microsoft gave a talk on Shared Source Implementation of.NET in Linux Bangalore 2002, a conference abt linux related technologies held in bangalore. You need to appreciate their balls. The presentation is in star office format.
IMHO mono has been a great asset for .NET adoption: Previously, one of the primary "sales" problems in encouraging .NET adoption was the fear that it ties the customer to a single vendor solution (and this is often heavily played up when it goes against Java, for instance). Mono offers one the ability to offer a rapidly developing alternative in case of ridiculous FUD circumstances often imagined in efforts to detract from Microsoft products (i.e. "What if they withdraw all their products and you have to give your firstborn to use it! Then what!").
Nobody could reasonably expect a project like this to have significant impact on a behemoth like Microsoft, but at least other platforms won't get shut out of a developing market. I'm glad Miguel at least has this realistic view.
Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
This is a weak story. A point is made about MS being forced into compatibility, but no facts to back up the claim. Journalism at it's finest. I'll make my own conjecture: Microsoft will put out a compatible/standard product when they see SIGNIFICANT decrease in market share or lost revenue. They haven't got X-Box right, nor Windows CE, but a few billion dollars later, a few strong-arm deals later, a few revision later, they'll have a story and a product and the sheep will make it a standard.
Religion and science are both 90% crap..but that doesn't negate the other 10%.
Mono is doing very well indeed as a platform independent of .NET or the tie-ins that Microsoft is traditionally associated. There are already several independent Gtk# applications popping up and the ASP.NET implementation is showing real promise. There's a new page of screenshots here. The Gtk# debugger and documentation browser are fairly complete and have been developed in a minimal time-frame thanks to C#. Other pages worth looking at are gsirc and Platano.
Basically, what these pages show is that Mono is less like Wine and more like a complete new development environment for Linux that also has cross-platform ties. There's lots of innovation going on in the Mono community and that's filtering down into projects like GNOME and KDE through Gtk# and Qt#, for example. I say it's all good.
Mono turns .NET into a commodity - so you won't have to bow to the altar of Microsoft in order to use it. That doesn't sound like a bad thing.
.NET get more early adopters - in which case it does seem to benefit Microsoft.
It looks like just another tool for the developer; don't think its going to make java go away anytime soon...
Now, Microsoft may look at this from two different perspectives: historically, it has been Microsoft that commoditized other people's standards and reaped the benefit - they might not take to having the roles reversed very well. On the other hand, this could help
Lodragan Draoidh
The more you explain it, the more I don't understand it. - Mark Twain
I'm taking part in a Microsoft sponsored contest at my university currently, the rules dictate that we have to use one of the .NET technologies (ASP.Net, C#, VB.net etc). However the rules specifically state that we cannot use open source CLRs such as Mono and/or Rotor. I just find it odd that the article talks about how Mono may help gain MS support, but at the same time MS seems adamant at keeping us from using it.
:)
Then again, I go to Ohio State. What do people out in Ohio know
Mono and Portable.NET really shine in allowing former Windows developers to get involved with Linux and still have a comfortable and semi-familiar place to start.
.NET are enthusiastic about Mono, but the higher-ups (see: PHB's) have no love for Mono or Linux.
I don't see Mono or Portable.NET as cross-platform technologies (unless you mean cross-platform across Unices) because Mono and Portable.NET grew up on Unix and will be used here the most. Besides, Microsoft has simply created too many API's and hence the barrier to a *quality* cross-platform development environment is too great.
Rather, Mono and Portable.NET will be good for rapid prototyping and as a conversion tool for Windows Application developers. Is also important for providing an alternative when the great migration begins of Smart Clients begin from Windows to Linux.
As for the rest of the article: Yah, I'm sure the Microsoft developers who created
Some people from Microsoft gave a talk on Shared Source Implementation of .NET in Linux Bangalore 2002, a conference abt linux related technologies held in bangalore. You need to appreciate their balls. The presentation is in star office format.