Jump to content

Mono (software): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
NovellGuy (talk | contribs)
68 edits
→‎Current status and roadmap: make previous user's change more clear about WPF
Added various history bits.
Line 34: Line 34:
| 2006-11-09 || Mono 1.2<ref>http://go-mono.com/archive/1.2/</ref> ||[[C Sharp 2.0|C# 2.0]] support
| 2006-11-09 || Mono 1.2<ref>http://go-mono.com/archive/1.2/</ref> ||[[C Sharp 2.0|C# 2.0]] support
|-
|-
| 2008-10-06 || Mono 2.0<ref>http://www.mono-project.com/Release_Notes_Mono_2.0</ref> || [[C Sharp 3.0|C# 3.0]] support
| 2008-10-06 || Mono 2.0<ref>http://www.mono-project.com/Release_Notes_Mono_2.0</ref> || Mono's APIs are now in par with .NET 2.0. Introduces the [[C Sharp 3.0|C# 3.0]] and Visual Basic 8 compilers. New Mono-specific APIs: Mono.Cecil, Mono.Cairo and Mono.Posix. Gtk# 2.12 is released. The Gendarme verification tool and Mono Linker are introduced.
|-
|-
| 2009-01-13 || Mono 2.2<ref>http://www.mono-project.com/Release_Notes_Mono_2.2</ref> || Mono switches its JIT engine to a [http://www.mono-project.com/Linear_IL new internal representation] that gives it a performance boost and introduces [[SIMD]] support in the [http://tirania.org/blog/archive/2008/Nov-03.html Mono.Simd] namespace. Mono introduces [http://tirania.org/blog/archive/2008/Nov-05.html Full Ahead of Time] compilation that allows developers to create full static applications and debuts the [http://tirania.org/blog/archive/2010/Apr-27.html C# Compiler as a Service] and the [http://www.mono-project.com/CsharpRepl C# Interactive Shell] (C# REPL)
| 2009-01-13 || Mono 2.2<ref>http://www.mono-project.com/Release_Notes_Mono_2.2</ref> || [[SIMD]] support
|-
|-
| 2009-03-30 || Mono 2.4<ref>http://www.mono-project.com/Release_Notes_Mono_2.4</ref> ||
| 2009-03-30 || Mono 2.4<ref>http://www.mono-project.com/Release_Notes_Mono_2.4</ref> || This release mostly polishes all the features that shipped in 2.2 and became the foundation for the Long-Term support of Mono in SUSE Linux.
|-
|-
| 2009-12-15 || Mono 2.6<ref>http://www.mono-project.com/Release_Notes_Mono_2.6</ref> || The Mono is now able to use LLVM as a code generation backend and this release introduces Mono co-routines, the Mono Soft Debugger and the CoreCLR security system required for Moonlight and other Web-based plugins. On the class library System.IO.Packaging, WCF client, WCF server, LINQ to SQL debut. The Interactive shell supports auto-completion and the LINQ to SQL supports multiple database backends. The xbuild build system is introduced.
| 2009-12-15 || Mono 2.6<ref>http://www.mono-project.com/Release_Notes_Mono_2.6</ref> ||
|-
|-
| TBD || Mono 2.8<ref>http://www.mono-project.com/Roadmap</ref> || Planned [[C Sharp 4.0|C# 4.0]] support
| TBD || Mono 2.8<ref>http://www.mono-project.com/Roadmap</ref> || Planned [[C Sharp 4.0|C# 4.0]] support
|}
|}


Lacking the resources to build a full .NET replacement on their own, Ximian formed the Mono open source project, which was announced on July 19, 2001 at the [[O'Reilly Media|O'Reilly]] conference. Almost three years later, on June 30, 2004 Mono 1.0 was released.<ref>{{Cite web |url=http://arstechnica.com/old/content/2004/06/3949.ars |title=OSS .NET implementation Mono 1.0 released - Ars Technica |publisher=[[ArsTechnica]]|accessdate=2009-10-23 }}</ref>
Lacking the resources to build a full .NET replacement on their own, Ximian formed the Mono open source project, which was announced on July 19, 2001 at the [[O'Reilly Media|O'Reilly]] conference. Almost three years later, on June 30, 2004 Mono 1.0 was released.<ref>{{Cite web |url=http://arstechnica.com/old/content/2004/06/3949.ars |title=OSS .NET implementation Mono 1.0 released - Ars Technica |publisher=[[ArsTechnica]]|accessdate=2009-10-23 }}</ref>. Being an open source project, the runtime evolved from a primary focus of being a developer platform for Linux desktop application to go into the server (with ASP.NET) to support a plurality of architectures and operating systems, to embedded systems.


The logo of Mono is a [[monkey|monkey's]] face, ''mono'' being [[Spanish language|Spanish]] for ''monkey''. The name relates to the monkeys and apes that are a central theme within Ximian, such as the GNOME Project's logo (a monkey's footprint), the Bonobo project ([[bonobo]]s are a species of chimpanzee), the [[Novell Evolution]] (formerly Ximian Evolution) Project, and the Ximian logo itself (a monkey's silhouette). According to the Mono FAQ, the origin of the name is "We like monkeys."<ref>{{Cite web
The logo of Mono is a [[monkey|monkey's]] face, ''mono'' being [[Spanish language|Spanish]] for ''monkey''. The name relates to the monkeys and apes that are a central theme within Ximian, such as the GNOME Project's logo (a monkey's footprint), the Bonobo project ([[bonobo]]s are a species of chimpanzee), the [[Novell Evolution]] (formerly Ximian Evolution) Project, and the Ximian logo itself (a monkey's silhouette). According to the Mono FAQ, the origin of the name is "We like monkeys."<ref>{{Cite web

Revision as of 01:17, 31 August 2010

This article is about the computing platform. For other uses, see Mono.
Mono
Developer(s)Novell
Initial releaseJune 30, 2004
Stable release
2.6.7 / July 19, 2010 (2010-07-19)
Repository
Operating systemCross-platform
TypePlatform
LicenseGPLv2, LGPLv2 and MIT, or dual license[1]
Websitewww.mono-project.com

Mono, IPA: [moʊ'noʊ], is a free and open source project led by Novell (formerly by Ximian) to create an Ecma standard compliant, .NET-compatible set of tools, including among others a C# compiler and a Common Language Runtime. Mono can be run on Linux, BSD, Unix, Mac OS X, Solaris and Windows operating systems. Microsoft may hold software patents over some of the technologies in Mono.[2]

History

Release History
Date Version[3] Notes
2004-06-30 Mono 1.0[4] C# 1.0 support
2004-09-21 Mono 1.1[5]
2006-11-09 Mono 1.2[6] C# 2.0 support
2008-10-06 Mono 2.0[7] Mono's APIs are now in par with .NET 2.0. Introduces the C# 3.0 and Visual Basic 8 compilers. New Mono-specific APIs: Mono.Cecil, Mono.Cairo and Mono.Posix. Gtk# 2.12 is released. The Gendarme verification tool and Mono Linker are introduced.
2009-01-13 Mono 2.2[8] Mono switches its JIT engine to a new internal representation that gives it a performance boost and introduces SIMD support in the Mono.Simd namespace. Mono introduces Full Ahead of Time compilation that allows developers to create full static applications and debuts the C# Compiler as a Service and the C# Interactive Shell (C# REPL)
2009-03-30 Mono 2.4[9] This release mostly polishes all the features that shipped in 2.2 and became the foundation for the Long-Term support of Mono in SUSE Linux.
2009-12-15 Mono 2.6[10] The Mono is now able to use LLVM as a code generation backend and this release introduces Mono co-routines, the Mono Soft Debugger and the CoreCLR security system required for Moonlight and other Web-based plugins. On the class library System.IO.Packaging, WCF client, WCF server, LINQ to SQL debut. The Interactive shell supports auto-completion and the LINQ to SQL supports multiple database backends. The xbuild build system is introduced.
TBD Mono 2.8[11] Planned C# 4.0 support

Lacking the resources to build a full .NET replacement on their own, Ximian formed the Mono open source project, which was announced on July 19, 2001 at the O'Reilly conference. Almost three years later, on June 30, 2004 Mono 1.0 was released.[12]. Being an open source project, the runtime evolved from a primary focus of being a developer platform for Linux desktop application to go into the server (with ASP.NET) to support a plurality of architectures and operating systems, to embedded systems.

The logo of Mono is a monkey's face, mono being Spanish for monkey. The name relates to the monkeys and apes that are a central theme within Ximian, such as the GNOME Project's logo (a monkey's footprint), the Bonobo project (bonobos are a species of chimpanzee), the Novell Evolution (formerly Ximian Evolution) Project, and the Ximian logo itself (a monkey's silhouette). According to the Mono FAQ, the origin of the name is "We like monkeys."[13]

Current status and roadmap

Mono's current version is 2.6.7 (as of July 2010). This version provides the core API of the .NET Framework as well as support for Visual Basic.NET and C# versions 2.0, 3.0 and 4.0. LINQ to objects, XML, and SQL are part of the distribution. C# 3.0 is now the default mode of operation for the C# compiler. Windows Forms 2.0 is also now supported. Support for C# 4.0 is feature complete (as of December 2009) but not yet released in a stable version.[14]

Implementation of .NET Framework 3.0 is under development under an experimental Mono subproject called "Olive", but the availability of WPF is not yet planned.[15][16]

The Mono project has also created a VB.NET compiler as well as a runtime designed for running VB.NET applications. It is currently being developed by Rolf Bjarne Kvinge.

Moonlight

Main article: Moonlight (runtime)

An open source implementation of Silverlight, called Moonlight, has been included since Mono 1.9.[17] Moonlight 1.0, which supports the Silverlight 1.0 APIs, was released January 20, 2009. Moonlight 2.0 supports Silverlight 2.0 and some features of Silverlight 3.0.[18] A preview release of Moonlight 3.0 was announced in February 2010 and contains updates to Silverlight 3 support.[19]

Mono components

Mono consists of three groups of components:

  1. Core components
  2. Mono/Linux/GNOME development stack
  3. Microsoft compatibility stack

The core components include the C# grammars and semantics and the Common Language Infrastructure. These components are based on the Ecma-334 and Ecma-335 standards,[20] allowing Mono to provide a standards compliant, free and open source CLI virtual machine. Microsoft issued a statement that covers both standards under their Community Promise license.[21]

The Mono/Linux/GNOME development stack provide tools for application development while using the existing GNOME and Free and Open Source libraries. These include: Gtk# for GUI development, Mozilla libraries for working with the Gecko rendering engine, Unix integration libraries, database connectivity libraries, a security stack, and the XML schema language RelaxNG. Gtk# allows Mono applications to integrate into the Gnome desktop as native applications. The database libraries provide connectivity to MySQL, SQLite, PostgreSQL, Firebird, Open Database Connectivity (ODBC), Microsoft SQL Server (MSSQL), Oracle, the object-relational database db4o, and many others. The Mono project tracks developing database components at its website.[22]

The Microsoft compatibility stack provides a pathway for porting Windows .NET applications to GNU/Linux. This group of components include ADO.NET, ASP.NET, and Windows.Forms, among others. As these components are not covered by ECMA standards, some of them remain subject to patent fears and concerns.

Framework architecture

Simplified Mono architecture

Code Execution Engine

The Mono runtime contains a code execution engine that translated ECMA CIL byte codes into native code and supports a number of processors: MIPS (in 32-bit mode only), x86, SPARC, PowerPC, ARM, S390 (in 32-bit and 64-bit mode), and x86-64 and IA-64 for 64-bit modes.

The code generator is exposed in three modes:

  • Just in time compilation: The runtime will turn ECMA CIL byte codes into native code as the code runs.
  • Ahead-of-Time compilation: this code turns the ECMA CIL byte codes (typically found on a .exe or .dll file) and generates native code stored in an operating system, architecture and CPU specific file (for a foo.exe file, it would produce foo.exe.so on Linux). This mode of operation compiles most of the code that is typically done at runtime. There are some exceptions like trampolines and other administrative bits of code that still require the JIT to function, so AOT images are not fully standalone.
  • Full Static Compilation: this mode is only supported on a handful of platforms and takes the Ahead-of-Time compilation process one step further and generates all the trampolines, wrappers and proxies that are required into a static file that can be statically linked into a program and completely eliminates the need for a JIT at runtime. This is used on Apple's iOS, Sony's PlayStation 3 and Microsoft's XBox 360 operating systems.

Starting with Mono 2.6, it is possible to configure Mono to use the Low Level Virtual Machine (LLVM) as the code generation engine instead of Mono's own code generation engine. This is useful for high performance computing loads and other situations where the execution performance is more important than the startup performance.

Starting with the Mono 2.7 preview, it is not longer necessary to pick one engine over the other at configuration time. The code generation engine can be selected at startup by using the --llvm or --nollvm command line arguments, and it defaults to the fast Mono code generation engine.

Garbage Collector

The current default garbage collector (the "Boehm-Demers-Weiser Conservative Garbage Collector")[23][24] has significant limitations compared to commercial garbage-collected runtimes like the Java Virtual Machine or the .NET framework's runtime, such as a conservative garbage collection can exhibit memory leaks that make it unsuitable for long-running server applications.

As of July 2009, development of a modern garbage collector called "Simple Generational GC" (SGen-GC) is under way and is now bundled as part of Mono 2.7. Just like the LLVM code generation engine is now selectable at startup, users can elect to use the new SGen garbage collector by passing the --gc=sgen switch to the Mono runtime at startup.[23]

Class library

The class library provides a comprehensive set of facilities for application development. They are primarily written in C#, but due to the Common Language Specification they can be used by any .NET language. The class library is structured into namespaces, and deployed in shared libraries known as assemblies. Speaking of the .NET framework is primarily referring to this class library.[25]

Namespaces and assemblies

Namespaces are a mechanism for logically grouping similar classes into a hierarchical structure. This prevents naming conflicts. The structure is implemented using dot-separated words, where the most common top-level namespace is System, such as System.IO and System.Net. There are other top-level namespaces as well, such as Accessibility and Windows. A user can define a namespace by placing elements inside a namespace block.

Assemblies are the physical packaging of the class libraries. These are .dll files, just like (but not to be confused with) Win32 shared libraries. Examples of assemblies are mscorlib.dll, System.dll, System.Data.dll and Accessibility.dll. Namespaces are often distributed among several assemblies and one assembly can be composed of several files.

Common Language Infrastructure and Common Language Specification

The Common Language Infrastructure (CLI), or more commonly known as the Common Language Runtime, is implemented by the Mono executable. The runtime is used to execute compiled .NET applications. The common language infrastructure is defined by the ECMA standard.[26] To run an application, you must invoke the runtime with the relevant parameters.

The Common Language Specification (CLS) is specified in chapter 6 of ECMA-335 and defines the interface to the CLI, such as conventions like the underlying types for Enum. The Mono compiler generates an image that conforms to the CLS. This is the Common Intermediate Language. The Mono runtime takes this image and runs it. The ECMA standard formally defines a library that conforms to the CLS as a framework.

Managed and unmanaged code

Within a native .NET/Mono application, all code is managed; that is, it is governed by the CLI's style of memory management and thread safety. Other .NET or Mono applications can use legacy code, which is referred to as unmanaged, by using the System.Runtime.InteropServices libraries to create C# bindings. Many libraries which ship with Mono use this feature of the CLI, such as Gtk#.

Several projects extend Mono and allow developers to use it in their development environment. These projects include:

Cross-Platform:

  • Moonlight, an implementation of Silverlight that uses Mono
  • MonoDevelop an open source and cross platform Integrated Development Environment that supports building applications for ASP.NET, Gtk#, Meego, MonoTouch and Silverlight/Moonlight.
  • Gtk#, C# wrappers around the underlying GTK+ and GNOME libraries, written in C and availble on Linux, MacOS and Windows.
  • Banshee Media Player a cross-platform music media player built with Mono and Gtk# and also a driver of dozens of C#-based libraries and projects for media handling.
  • Gecko#, bindings for embedding the layout engine used in Mozilla (Gecko)
  • Qyoto, C# bindings for the Qt framework
  • Mono Migration Analyzer (MoMA) tool
  • Tao, a collection of graphics and gaming bindings (OpenGL, SDL, Glut, Cg)

MacOS:

  • Cocoa# [1] wrappers around the native Mac OS X toolkit (Cocoa) (deprecated)
  • MonoMac the new bindings for OSX programming, based on the MonoTouch API design.

Mobile Platforms:

  • MonoTouch Mono for the iPhone, iPad and iPod Touches. With bindings to the iOS APIs.
  • MonoDroid Mono for the Android operating system. With bindings for the Android APIs.

Windows:

Microsoft has a version of .NET 2.0 now available only for Windows XP, called the Shared Source CLI (Rotor). Microsoft's shared source license may be insufficient for the needs of the community (it explicitly forbids commercial use). The Mono project has many of the same goals as the Portable.NET project, part of the similar but separate project DotGNU run by Free Software Foundation.

MonoDevelop

Main article: MonoDevelop

MonoDevelop is a free GNOME integrated development environment primarily designed for C# and other .NET languages such as Nemerle, Boo, and Java (via IKVM.NET). MonoDevelop was originally a port of SharpDevelop to Gtk#, but it has since evolved to meet the needs of Mono developers. The IDE includes class management, built-in help, code completion, Stetic (a GUI designer), project support, and an integrated debugger.

The MonoDoc browser provides access to API documentation and code samples. The documentation browser uses wiki-style content management, allowing developers to edit and improve the documentation.

MonoTouch

Release History
Date Version Notes
2009-09-14 MonoTouch 1.0[27] Initial release
2010-04-05 MonoTouch 2.0[28] iPad support
2010-04-16 MonoTouch 3.0[29] iPhone 4 support
2010-07-31 MonoTouch 3.0.8[30] Latest version

MonoTouch allows developers to create C# and .NET based applications that run on the iPhone. It is based on the Mono framework and developed in conjunction with Novell. Unlike Mono applications MonoTouch "Apps" are compiled down to machine code targeted specifically at the Apple iPhone.

MonoTouch is available from Novell under a separate licensing agreement to Mono[31]. MonoDevelop is used as the primary IDE however additional links to Xcode and the iPhone simulator have been written.

In April 2010, Apple introduced a new term for iPhone developers that apparently prohibits them from developing in languages other than C, C++ and Objective-C, and the use of a middle layer between the iPhone OS platform and iPhone applications. This makes the future of MonoTouch, as well as other technologies such as UNITY, uncertain.[32]

License

Mono is dual licensed by Novell, similar to other products such as Qt and the Mozilla Application Suite. Mono's C# compiler and tools are released under the GNU General Public License (GPLv2 only) (starting with version 2.0 of Mono, the Mono C# compiler source code will also be available under the MIT X11 License),[33] the runtime libraries under the GNU Lesser General Public License (LGPLv2 only) and the class libraries under the MIT License. These are all free software and open-source licenses and hence Mono is free and open-source software.

Mono and Microsoft’s patents

Template:Details3 Mono’s implementation of those components of the .NET stack not submitted to the ECMA for standardization has been the source of patent violation concerns for much of the life of the project. In particular, discussion has taken place about whether Microsoft could destroy the Mono project through patent suits. Over the lifetime of the project, these concerns have not materialized.

The base technologies submitted to the ECMA, and therefore also the Unix/GNOME-specific parts, are not problematic due to Microsoft's explicitly placing both ECMA 334 and ECMA 335 standards under the Microsoft Community Promise license. The concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms (see Non standardized namespaces), i.e. parts composing Mono’s Windows compatibility stack. These technologies are today not fully implemented in Mono and not required for developing Mono-applications.

Free Software Foundation's warnings

Richard Stallman of the Free Software Foundation has stated it may be "dangerous" to use Mono because of the possible threat of Microsoft patents.[34] For this reason, the FSF recommends that people avoid creating free software that depends on Mono or C#.[35]

On November 2, 2006, Microsoft and Novell announced a joint agreement whereby Microsoft agreed to not sue Novell’s customers for patent infringement.[36] Under the agreement, patent protections extends to Mono but only for Novell developers and customers.[37] It was criticized by some members of the free software community because it violates the principles of giving equal rights to all users of a particular program.

In a note posted on the Free Software Foundation's news website in June 2009, Richard Stallman warned that he believes "Microsoft is probably planning to force all free C# implementations underground some day using software patents" and recommended that developers avoid taking what he described as the "gratuitous risk" associated with "depend[ing] on the free C# implementations", including Mono.[38]

On July 6, 2009, Microsoft announced that it was placing their ECMA 334 and ECMA 335 specifications under their Community Promise pledging that they would not assert their patents against anyone implementing, distributing, or using alternative implementations of .NET[39]. However, their position regarding the non-ECMA components like ASP.NET, ADO.NET, and Windows Forms (which are the bone of contention) remains unclarified.

Subsequently, the Free Software Foundation reiterated its warnings,[40] claiming that the extension of Microsoft Community Promise to the C# and the CLI ECMA specifications[41] would not prevent Microsoft from harming open source implementations of C#, because many specific Windows libraries included with .NET or Mono were not covered by this promise, examples include regular expressions and XML which the FSF considers now dangerous to use.[42]

These warnings, however, were countered by Miguel de Icaza, lead developer of Mono, on the GNOME Foundation mailing-list[43], saying "That article now leads us to believe that there is something "magical" about the way that Microsoft implements regular expressions or how they implemented XSLT and XPath. If you can't find prior art for that, you probably should leave the software industry while you are still ahead."

Canonical Ltd., makers of the Ubuntu (Operating System) Linux distribution, have also come out with a Mono Position Statement[44] which states that "It is common practice in the software industry to register patents as protection against litigation, rather than as an intent to litigate. Thus mere existence of a patent, without a claim of infringement, is not sufficient reason to warrant exclusion from the Ubuntu Project." The statement then goes on to say that they would therefore continue to ship Mono in Ubuntu until the patents actually become a real threat rather than simply a perceived threat.

Fedora Project Leader, Paul Frields, has stated that "We haven't come to a legal conclusion that is pat enough for us to make the decision to take mono out." [45]

Software developed with Mono

Banshee (media player)
GNOME Do

The following are programs that use the Mono API and C#.

See also

Notes

  1. ^ "FAQ: Licensing – Mono". Retrieved 2009-11-26.
  2. ^ Mono FAQ: Licensing | Patents
  3. ^ http://www.mono-project.com/OldReleases
  4. ^ http://go-mono.com/archive/1.0/
  5. ^ http://www.go-mono.com/archive/1.1.1/
  6. ^ http://go-mono.com/archive/1.2/
  7. ^ http://www.mono-project.com/Release_Notes_Mono_2.0
  8. ^ http://www.mono-project.com/Release_Notes_Mono_2.2
  9. ^ http://www.mono-project.com/Release_Notes_Mono_2.4
  10. ^ http://www.mono-project.com/Release_Notes_Mono_2.6
  11. ^ http://www.mono-project.com/Roadmap
  12. ^ "OSS .NET implementation Mono 1.0 released - Ars Technica". ArsTechnica. Retrieved 2009-10-23.
  13. ^ "FAQ: General". Mono Projects. Retrieved December 4, 2009.
  14. ^ What have we been up to?
  15. ^ Olive
  16. ^ Mono Project Roadmap - Mono
  17. ^ "MoonlightRoadmap". Mono Team. Retrieved 2008-11-08.
  18. ^ http://tirania.org/blog/archive/2009/Dec-17.html
  19. ^ http://tirania.org/blog/archive/2010/Feb-03.html
  20. ^ Ecma-335
  21. ^ Technet.com
  22. ^ http://www.mono-project.com/Database_Access
  23. ^ a b "Compacting GC". mono-project.com. Retrieved 2008-12-16.
  24. ^ Boehm, Hans-J. "Advantages and Disadvantages of Conservative Garbage Collection". Xerox Parc. Retrieved 2008-12-16.
  25. ^ .NET Framework Architecture on the official Mono documentation
  26. ^ ECMA-335
  27. ^ http://tirania.org/blog/archive/2009/Sep-14.html
  28. ^ http://monotouch.net/Releases/MonoTouch_2/MonoTouch_2.0.0
  29. ^ http://monotouch.net/Releases/MonoTouch_3/MonoTouch_3.0.0
  30. ^ http://monotouch.net/Releases/MonoTouch_3/MonoTouch_3.0.12
  31. ^ http://www.monotouch.net
  32. ^ http://arstechnica.com/apple/news/2010/04/apple-takes-aim-at-adobe-or-android.ars
  33. ^ "Mono C# Compiler Under MIT X11 License". Novell Inc. 2008-04-08.
  34. ^ Stallman, Richard (2006-03-09). "Transcript of Richard Stallman on the Free Software movement, Zagreb". Free Software Foundation. Retrieved 2006-11-02. (...)we know that Microsoft is getting patents on some features of C#. So I think it's dangerous to use C#, and it may be dangerous to use Mono. There's nothing wrong with Mono. Mono is a free implementation of a language that users use. It's good to provide free implementations. We should have free implementations of every language. But, depending on it is dangerous, and we better not do that.
  35. ^ Stallman, Richard (2009-06-26). "Why free software shouldn't depend on Mono or C#". Free Software Foundation. Retrieved 2009-07-02. We should systematically arrange to depend on the free C# implementations as little as possible. In other words, we should discourage people from writing programs in C#. Therefore, we should not include C# implementations in the default installation of GNU/Linux distributions, and we should distribute and recommend non-C# applications rather than comparable C# applications whenever possible.
  36. ^ "Microsoft and Novell Announce Broad Collaboration on Windows and SUSE Linux Interoperability and Support" (Press release). Novell. 2006-11-02. Retrieved 2006-11-02.
  37. ^ "Novell and Microsoft collaborate". 2006-11-02.
  38. ^ Stallman, Richard (June 26, 2009). "Why free software shouldn't depend on Mono or C#". Free Software Foundation. Retrieved July 2, 2009. The danger is that Microsoft is probably planning to force all free C# implementations underground some day using software patents. ... We should systematically arrange to depend on the free C# implementations as little as possible. In other words, we should discourage people from writing programs in C#. Therefore, we should not include C# implementations in the default installation of GNU/Linux distributions, and we should distribute and recommend non-C# applications rather than comparable C# applications whenever possible.
  39. ^ "The ECMA C# and CLI Standards".
  40. ^ "Microsoft's Empty Promise". Free Software Foundation. 2009-07-16. Retrieved 2009-08-03. Until that happens, free software developers still should not write software that depends on Mono. C# implementations can still be attacked by Microsoft's patents: the Community Promise is designed to give the company several outs if it wants them. We don't want to see developers' hard work lost to the community if we lose the ability to use Mono, and until we eliminate software patents altogether, using another language is the best way to prevent that from happening.
  41. ^ "The ECMA C# and CLI Standards". 2009-07-06. Retrieved 2009-08-03.
  42. ^ "Microsoft's Empty Promise". Free Software Foundation. 2009-07-16. Retrieved 2009-08-03. we're talking about libraries under the System namespace that provide common functionality programmers expect in modern programming languages: binary object serialization, regular expressions, XPath and XSLT, and more.
  43. ^ "Re: Reboot: Strategic goals for GNOME". GNOME. 2010-03-05. Retrieved 2010-05-12. That article now leads us to believe that there is something "magical" about the way that Microsoft implements regular expressions or how they implemented XSLT and XPath. If you cant find prior art for that, you probably should leave the software industry while you are still ahead.
  44. ^ "Mono Position Statement". Ubuntu. 2009-06-30. Retrieved 2010-05-12. Given the above, the Ubuntu Technical Board sees no reason to exclude Mono or applications based upon it from the archive, or from the default installation set.
  45. ^ "Fedora is concerned about Mono". internetnews.com. 2009-06-12. Retrieved 2010-07-04. We haven't come to a legal conclusion that is pat enough for us to make the decision to take mono out
  46. ^ Cartoon Network's Kid's MMO and Mono.
  47. ^ List of Commercial Applications using Mono
  48. ^ Mono Launch announced on Second Life Blog Retrieved on 2008-08-30.
  49. ^ Mono Second Life viewer released Retrieved on 2008-08-30.
  50. ^ Something Awful: The Internet Makes You Stupid

References

International

Retrieved from "https://en.wikipedia.org/w/index.php?title=Mono_(software)&oldid=381987076"