[Mono-list] open sourcing all of Microsoft .net
Martin Thwaites
monoforum at my2cents.co.uk
Fri Sep 6 21:44:19 UTC 2013
My opinion on why big businesses don't want to run their applications on
mono is more or less exactly the reasons you suggest Aaron.
I'm specifically talking about ASP.NET type stuff not desktop as desktop
really depends on your user base, where as web servers don't matter to the
end user.
Personally, the battle I fight when trying to push a move to Linux as the
hosting OS for the applications is that Mono is seen more as a "hobbist"
project than something that people would run their entire business on.
They see it as something that people will stop supporting when they "get
bored or too busy on real projects" (<--- direct quote from a previous
director I worked for).
I've been running all my personal projects on Mono for years, and some
non-essential (non-production) business applications too, so I'm
comfortable that it's good to go, but when the directors get involved, and
the tech support guys, it falls apart.
What I think would clinch the deal is if there was some big company behind
the Mono, one that "big business" trusted. I honestly don't think that it
needs to be Microsoft (not saying that it shouldn't just that it doesn't
need to be). Even when Novell was behind it, it still didn't have the
kudos needed for people to be confident with.
Possibly a rebrand may be in order. Similar to what Xamarin did to
distance them from "mono" as a name (I know they're still involved in Mono,
but creating a brand that is not mono seems to have really helped them).
Not that Mono is a bad name just that it has a stigma right now, that I
don't think is going to go away.
Anyway, that's just my 2 cents on the matter.
Martin
On 6 September 2013 19:31, Jonathan Lima <greenboxal at gmail.com> wrote:
> When I said about WPF I was talking about the entire stack(except DirectX,
> ofcourse). Thats includes cormedia source which we would abstract and port
> to other platforms.
>
>
> On Fri, Sep 6, 2013 at 3:24 PM, "Andrés G. Aragoneses" <knocte at gmail.com>wrote:
>
>>
>> opensource != crossplatform
>>
>>
>> Do you think WPF internals are just managed code?
>>
>>
>> On 06/09/13 19:37, Jonathan Lima wrote:
>>
>>> There is no reason to use Microsoft code of the BCL. One of the best
>>> libraries that could be open sourced is WPF, there isn't any UI
>>> framework that works better or that is easier to use than WPF. And with
>>> WPF open source, .Net UI could be really cross-platform without needing
>>> any modifications.
>>>
>>>
>>> On Fri, Sep 6, 2013 at 2:34 PM, Martin Thwaites
>>> <monoforum at my2cents.co.uk <mailto:monoforum at my2cents.co.**uk<monoforum at my2cents.co.uk>>>
>>> wrote:
>>>
>>> There is a specific exclusion in the EULA that says you can't use it
>>> port it to a "Non-Windows" operating system.
>>>
>>> I think there will always be a slight issue with a "Cross Platform"
>>> .NET as there are too many things that have hook-ins to specific MS
>>> Technologies outside of .NET.
>>>
>>> I agree though, open sourcing the core libraries, holding back some
>>> specifics that key into their technologies specifically (IIS comes
>>> to mind), would be a big positive move.
>>>
>>> The reality is though, it would never be termed ".NET for Linux" or
>>> be backed by MS, so major companies will always be apprehensive
>>> about running those production sites on Linux.
>>>
>>> On Sep 6, 2013 6:20 PM, "Andrew Clancy" <nite at achren.org
>>> <mailto:nite at achren.org>> wrote:
>>>
>>> That's not open source, that's readable source, you can't fork
>>> it or use it, nor merge it with mono & have an official .net
>>> framework for linux etc. My thoughts are, if we did have this
>>> there'd be more appetite/scope to implement in .net in
>>> corporates and environments where linux and/or java rule. Where
>>> I work mono isn't an option as there's no other companies of our
>>> size using it to the scale we use java, but if a Microsoft
>>> backed .net made it to linux it may be an option (and I'm sure
>>> if ms open sourced it mono would do most of the work to merge,
>>> ms would just need to stamp approval)
>>>
>>> On 6 Sep 2013 18:10, "Mike Christensen" <mike at kitchenpc.com
>>> <mailto:mike at kitchenpc.com>> wrote:
>>>
>>> I'm pretty sure it already is..
>>>
>>> http://referencesource.**microsoft.com/netframework.**aspx<http://referencesource.microsoft.com/netframework.aspx>
>>>
>>>
>>> On Wed, Sep 4, 2013 at 11:33 PM, nite <nite at achren.org
>>> <mailto:nite at achren.org>> wrote:
>>>
>>> Has the case ever been made to Microsoft to open source
>>> all of .net? It's
>>> heading that way, now even the asp.net <http://asp.net>
>>> stack is open. Not much to lose, as
>>> it isn't part of their core business, and still not part
>>> of their core
>>> windows stack. Loads to gain, massive kudos from the dev
>>> community and the
>>> chance to win back the hoards of devs jaded by Microsoft
>>> for various
>>> reasons.
>>>
>>> Has anyone from the mono camp ever tried lobbying them,
>>> or aware of any
>>> efforts? What was the response?
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://mono.1490590.n4.nabble.**
>>> com/open-sourcing-all-of-**Microsoft-net-tp4660784.html<http://mono.1490590.n4.nabble.com/open-sourcing-all-of-Microsoft-net-tp4660784.html>
>>> Sent from the Mono - General mailing list archive at
>>> Nabble.com.
>>> ______________________________**_________________
>>> Mono-list maillist - Mono-list at lists.ximian.com
>>> <mailto:Mono-list at lists.**ximian.com<Mono-list at lists.ximian.com>
>>> >
>>> http://lists.ximian.com/**mailman/listinfo/mono-list<http://lists.ximian.com/mailman/listinfo/mono-list>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> Mono-list maillist - Mono-list at lists.ximian.com
>>> <mailto:Mono-list at lists.**ximian.com<Mono-list at lists.ximian.com>
>>> >
>>> http://lists.ximian.com/**mailman/listinfo/mono-list<http://lists.ximian.com/mailman/listinfo/mono-list>
>>>
>>>
>>> ______________________________**_________________
>>> Mono-list maillist - Mono-list at lists.ximian.com
>>> <mailto:Mono-list at lists.**ximian.com <Mono-list at lists.ximian.com>>
>>> http://lists.ximian.com/**mailman/listinfo/mono-list<http://lists.ximian.com/mailman/listinfo/mono-list>
>>>
>>>
>>>
>>>
>>> --
>>> Thanks,
>>> Jonathan
>>>
>>>
>>> ______________________________**_________________
>>> Mono-list maillist - Mono-list at lists.ximian.com
>>> http://lists.ximian.com/**mailman/listinfo/mono-list<http://lists.ximian.com/mailman/listinfo/mono-list>
>>>
>>>
>>
>> ______________________________**_________________
>> Mono-list maillist - Mono-list at lists.ximian.com
>> http://lists.ximian.com/**mailman/listinfo/mono-list<http://lists.ximian.com/mailman/listinfo/mono-list>
>>
>
>
>
> --
> Thanks,
> Jonathan
>
> _______________________________________________
> Mono-list maillist - Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20130906/47d1ce01/attachment-0001.html>
More information about the Mono-list
mailing list