Linked by Thom Holwerda on Wed 30th May 2012 08:05 UTC
General Development "In the last five years, LLVM has evolved from an academic project to the universal back-end of C, C++, and Objective C compilers. The key to its success is its performance and adaptability, both of which derive from its unique design and implementation."
Thread beginning with comment 520026
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: I know what we need
by twitterfire on Wed 30th May 2012 15:15 UTC in reply to "RE: I know what we need"
twitterfire
Member since:
2008-09-11

Mono uses LLVM as an alternative for its own JIT compiler. It doesn't generate native code.

As for Apple and encouraging C#/VB devs to code for Os X/ iOS, the problem is that .NET devs invested too much time in learning MS specific apis like winforms and WPF which Apple can't legally implement. They can implement C# bindings to Apple specific apis however.

Edited 2012-05-30 15:22 UTC

Reply Parent Score: 3

RE[3]: I know what we need
by adkilla on Wed 30th May 2012 15:35 in reply to "RE[2]: I know what we need"
adkilla Member since:
2005-07-07

A lot of this would have been solved if Mono used a platform independent API to start with. Also the APIs and technologies on .NET/WinRT are patented which in itself legally restricts them from being used in other platforms/runtimes.

Reply Parent Score: 1

RE[4]: I know what we need
by lucas_maximus on Wed 30th May 2012 17:01 in reply to "RE[3]: I know what we need"
lucas_maximus Member since:
2009-08-18

Microsoft have made a legally binding policy not to use those that use Mono and Infringe on Patents.

http://blog.xamarin.com/2012/05/01/android-in-c-sharp/

The .NET framework is also covered by Microsoft’s legally binding community promise.


http://www.microsoft.com/openspecifications/en/us/programs/communit...

If anyone claims otherwise it is pure FUD.

Reply Parent Score: 9

RE[4]: I know what we need
by zima on Wed 6th Jun 2012 23:55 in reply to "RE[3]: I know what we need"
zima Member since:
2005-07-06

A lot of this would have been solved if Mono used a platform independent API to start with.

Gtk# or Gecko# are there (but anyway, there wouldn't be much point to Mono without some significant portability of code with MS stack)

Reply Parent Score: 2

RE[3]: I know what we need
by moondevil on Wed 30th May 2012 15:40 in reply to "RE[2]: I know what we need"
moondevil Member since:
2005-07-08

Mono uses LLVM as an alternative for its own JIT compiler. It doesn't generate native code.


They also AOT C# code to native.

http://www.mono-project.com/AOT

Reply Parent Score: 5

RE[4]: I know what we need
by henderson101 on Thu 31st May 2012 13:17 in reply to "RE[3]: I know what we need"
henderson101 Member since:
2006-05-30

Except - the licensing on the Mono platform pretty much means that static linking is not allowed. So it's of limited use really.

Reply Parent Score: 2

RE[3]: I know what we need
by _txf_ on Wed 30th May 2012 16:01 in reply to "RE[2]: I know what we need"
_txf_ Member since:
2008-03-17

Mono uses LLVM as an alternative for its own JIT compiler. It doesn't generate native code.


I do believe the mono guys have a product that allows one to compile C# down to native code for ios (it might even be able to access cocoa apis)

Reply Parent Score: 2

RE[3]: I know what we need
by lucas_maximus on Wed 30th May 2012 17:02 in reply to "RE[2]: I know what we need"
lucas_maximus Member since:
2009-08-18

Yes they could implement WPF

http://www.mono-project.com/WPF

The only reason it is not being developed on is because nobody in the Mono community wants it.

Reply Parent Score: 3

RE[4]: I know what we need
by dsmogor on Thu 31st May 2012 08:17 in reply to "RE[3]: I know what we need"
dsmogor Member since:
2005-09-01

Honest question: is it possible to get reasonable performance from would be WPF layered on top of anything other than DirectX?

Edited 2012-05-31 08:17 UTC

Reply Parent Score: 2