Mono Comes To Android 257
A reader writes "After releasing Monotouch for iPhone which allows c# development on iOS, Novell has announced the availability of Mono for Android. Will this give us the 'one language to rule them all' that Java failed to bring, or will the bad blood between the F/OSS groups and Microsoft make this a dead end?"
Mono? On my Android? (Score:4, Funny)
Guess I won't be kissing it for a week or so.
Re: (Score:3)
Re: (Score:3)
That's what happens when you pair it to slutty devices, like the iPhone, over Bluetooth.
I thought the iphone was homo-phonal, you couldn't pair it to phones other than iphones...did this change?
Neither (Score:5, Insightful)
Will this give us the 'one language to rule them all' that Java failed to bring, or will the bad blood between the F/OSS groups and Microsoft make this a dead end?
Neither. It will be exactly what it already is today, just one of many programming languages.
Re: (Score:3, Insightful)
Re: (Score:2, Insightful)
...the reason for this is because Microsoft can wipe the floor with it at any point it feels like.
The same FUD has been used for the last seven years, and Microsoft is still yet to "wipe the floor". As each year passes without the predicted backlash, your suggestion looks more and more like it should come with a free tinfoil hat!
There is no indication at all that Microsoft is unhappy with Mono. In fact, Microsoft needs the Mono project to give its .NET platform legitimacy as a cross platform solution. If it tried to stop Mono then it would only serve to scare developers away from .NET completely.
Re:Neither (Score:4, Insightful)
"But that's just because (blah blah blah)!!"
Exactly.
Re: (Score:2)
Re:Neither (Score:4, Insightful)
The Netflix thing is a bummer, but it's a case of drm not being compatible with open source, as I see it.
It seems to me the problem is that DRM is incompatible with people owning their personal property. There is nothing stopping you from writing an open source program that encrypts movies while they're in transit over a network etc. And then people will break the DRM in two hours just like they do with the proprietary ones.
The real incompatibility is in allowing the user to own their computer. Even if you have proprietary software, if the user can attach a debugger to it or can emulate the whole thing in software then the DRM is toast. The only way that DRM can "work" is by eliminating actual property ownership. It literally requires for us all to become renters and trespassers on what was once our own property, so that corporations can own our culture. I mean literally -- it's not an exaggeration.
DRM sucks, but as far as I can tell, Netflix can't exist without it.
Over-the-air broadcast TV exists without it. In higher quality than Netflix. So I'm not seeing the inherent reason why Netflix can't exist without it.
Re: (Score:2)
DRM sucks, but as far as I can tell, Netflix can't exist without it.
Over-the-air broadcast TV exists without it. In higher quality than Netflix. So I'm not seeing the inherent reason why Netflix can't exist without it.
My assumption is that the movie studios require it, or at least require it if Netflix wants to obtain licenses at a reasonable rate. I can be wrong, but I have a strong feeling that the movie studios have a big part in this.
Re: (Score:2, Flamebait)
Re: (Score:3)
Microsoft doesn't care about Mono for the same reason as Wine - because it doesn't - and never will - work well enough to be a factor either way.
Only if you assume that the point of Mono is to run .NET apps. True, that is what it can do to some extent, but it is also a development platform of its own (which is what TFA is all about). Developing using Mono is the best way to ensure you have a cross platform program.
Applications developed using the base Mono libraries will work on Mono and .NET runtime. You can use libraries that will not run on Microsoft's .NET (the reverse of the problem that you had). The ultimate example is if you develop somethin
Re: (Score:3)
Now that would be an interesting development - Mono first embracing then extending .NET (you know what follows).
Re: (Score:2)
but surely you would concede that mono as an API in its own right would be fine. Just another alternative way to write Android apps.
Re:Neither (Score:5, Insightful)
Re: (Score:3, Insightful)
VFAT was never covered by Microsoft with a Microsoft Community Promise, have patent grants under MS-PL or Apache2 licenses, be covered by the Microsoft Open Specification Promise, or be directly specified by patent covenants. There are parts of .NET that are not explicity covered by these various patent grants, but 1) you don't have to use them and 2) (AFAIK) they are not used in these versions of Mono for Mobile phones.
Microsoft never touted VFAT as a cross platform technology like it did with .NET. The de
Re:Neither (Score:4, Insightful)
LMOL....yeah Microsoft needs Mono for legitimacy? From who??
You answered your own question later when you said:
FYI .NET has been around since 2000. It has been touted as cross platform and cross language. That has not materialized in the past 10 years.
The reason Microsoft needs Mono is exactly because they tout their platform as cross platform. You say that it hasn't materialized in 10 years, but here we are talking about being able to use Mono in Linux, iOS and now Android. As for cross language support [dotnetpowered.com], I can't see how you could possibly deny that claim!
The rest of your post just seems to say that if you only care about running on Windows then you use .NET, but if you want Linux support then you use Mono. That doesn't actually contradict what I said. And if nobody cares about Mono, when why are you bothering to post here about it?
Not correct (Score:2)
Mono is not a language
Although you are technically correct that Mono is not a language, Mono IS a mechanism to use the C# language.
From there to actually develop applications for the iPhone, you make use of the Apple frameworks, which Mono has handily wrapped in C# wrappers.
So I wouldn't say it's "less" than anything, it's just basically a way to use C# for different platforms while still using the native libraries they offer.
Re: (Score:3)
No - this is wrong.
The danger is that Microsoft can steer future versions in a path that only helps them.
They cant take away mono or do anything to stop it in its current form. So any apps written for mono as it is today, are fine.
The danger with mono is in betting your future on it...but the same danger exists with many other APIs too.
Re: (Score:2)
No, it will be less than current *platforms* (as Mono is not a language) and the reason for this is because Microsoft can wipe the floor with it at any point it feels like.
better quickly get back under that tin foil hat of yours.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2, Interesting)
Re: (Score:3)
Everything you see there except for the C# language and a few other bits, are all *at risk*. Things like ADO.NET (used by every persistence layer such as NHibernate, Entity Framework, Linq to SQL, etc), ASP.NET, Winforms, Silverlight, Parallel frameworks, Code Contracts, WCF, WF, etc. etc. Even WPF if they ever decide to clone it.
If Microsoft is so pro open source why don't they open
Re: (Score:2)
"Will this give us the 'one language to rule them all' that Java failed to bring..."
More like the one language to lose them all. Java and Flash cross-platform development have shown that you tend up with a least-common-denominator application that fails to take full advantage of any given platform, Couple that with failing to fully match a specific platform's UI and UX conventions, and you have a nice little recipe for developing a losing application.
You're also perpetually behind the curve, OS-wise. If App
Re: (Score:2)
Re: (Score:3)
More like the one language to lose them all. Java and Flash cross-platform development have shown that you tend up with a least-common-denominator application that fails to take full advantage of any given platform, Couple that with failing to fully match a specific platform's UI and UX conventions, and you have a nice little recipe for developing a losing application.
That's if you wrote the whole application in java. But writing a java backend with a platform-specific frontend is going to save you a hell of a lot of time porting code.
Re: (Score:3)
If you're going to claim Android isn't real Java, you may as well mention that Mono isn't real .NET.
And "maybe"? Keep in mind that Mono includes C dependencies. What a platform like .NET/Java buys you is easier portability and a kinder runtime, but the only place you can run a .NET or Java app that you can't run a C app is where you're deliberately sandboxed.
As for web stuff, the web is actually a decent platform now. I wish people would stop fucking that up with plugins. If you really want to make a browse
Finally (Score:3)
Finally I can hear good quality music with just the one earbud.
No, wait...
Re: (Score:2)
What does android get when kissing windows? ...
And In Other News (Score:5, Funny)
Reuters Minas Tirith - Mordor Inc. has announced the release of Ring of Power Open Source Version, to be released to the Free Peoples of Middle Earth. Mordor VP of Marketing, the Mouth of Sauron, has announced that the purpose of this open source version of the Ring of Power is to demonstrate Mordor's goodwill to all people.
"We're really hoping that all those Elves and Numenoreans and Halflings take our Open Source version of the Ring of Power and use it to do all kinds of nifty things." the Mouth of Sauron said. "There has been some animosity in the past between Mordor and the rest of Middle Earth, but we're pretty keen to the idea that this is the time to put it all behind us, so we're releasing, with this commitment from Sauron himself, open source Rings of Power with no future obligations to the Dark Lord, the Nazgul or anyone else in our organization."
When asked about previous attempts to take control of the other competing powers in Middle Earth (such as the infamous "One Ring to Rule Them All One Ring to Bind Them" proprietary patent-encumbered master Ring), the Mouth of Sauron dismissed it out of hand. "That was just business. But this is the dawning of a new age, and Mordor commits to not trying to seize control of the minds of any wielders of any open source Rings of Power... honest!"
(With files from Rivendell Archives)
Re: (Score:2)
Re: (Score:2)
Aptly put, sir.
So in two years when WP7 is still an also-ran in the mobile market, MS has another reason to trigger their patent bomb to defend .NET. Brilliant.
Re: (Score:3)
Re: (Score:2)
You missed another inconsistency, and that is the Mouth of Sauron, who certainly wouldn't have been around in the Second Age.
Re: (Score:2)
Uh, the Nazgul wouldn't have been around, as they were recipients of the rings of power.
Uh, those would have been proprietary Rings of Power®, just like the One Ring to Rule them All®, which was also mentioned in the press release. The good peoples of Middle Earth had become suspicious of the proprietary Rings of Power after seeing recipients turn into Nazgul and such.
The newly released Open Source Rings of Power have all of the power and benefits of the proprietary RoPs and have the appearance of less of a downside. It is a win-win for both Sauron and for his minions.
IPhone C# (Score:2)
The iPhone developer licence forbids scripting engines or Just-In-Time (JIT) compilers, which .NET needs to run code.
Someone had better let all of the Unity IPhone developers know that they cannot use Mono C# on the iphone as it is forbidden. Really guys all of those apps you have been selling for the last two years for the IPhone is just not possible.
Re: (Score:3)
Re:IPhone C# (Score:4, Informative)
Wrong.
MonoTouch ( which is the IOS .NET development suite ) uses the Mono Full AOT feature and precompiles all the code into a static binary ( including the base class libraries ) and links in runtime stubs for GC and the likes.
Certain features of .NET are naturally not available ( runtime code generation, features relying thereupon ) and some c# features don't work ( virtual methods in generic classes for example )
So you end up with a fully statically linked executable with no JIT included, fully compliant with IOS licensing terms.
Unity3D uses the same approach ( and probably shares a bit of the codebase )
News that matters? (Score:4, Insightful)
We already can program Android in Java (and Scala) and script it in Python, Lua, BeanShell, Perl, Tcl, JavaScript and Ruby. I hadn't noticed the multitudes crying out for Mono.
Re: (Score:2)
+1 parent
No, because Mono isn't a language. C# and F# are languages.
Re:News that matters? (Score:5, Informative)
Re: (Score:2)
Re: (Score:2)
The others I mentioned are scripted using the JSR-223 interface; not something you'd use for anything really deep. Scala is just Java with the compiler replaced by the same guy who more-or-less wrote the current javac, but allowing himself to define a new language with a lot of the mistakes in the design of the Java language itself mitigated. It's totally OO and totally functional at the same time, yet can use existing Java libraries with an amazing level of transparency.
Re: (Score:2)
Not to be negative, especially since I just started writing an Android app, but even Java seems to be half baked. I really hope that once I get used to the quirks my productivity will improve, but nothing seems to work the way I expect it too. I'm not trying to troll here, it's just that there seems to be one way that works well and about 100 other ways that may or may not work. I spend a lot of my time guessing what the one magic working way is (especially since it often isn't my first choice). I had a
Re: (Score:3)
Java works fine on Dalvik, but there are performance regressions that deeply separate Dalvik from Hotspot. Sun's long and hard work over the years has produced a very well performing system that Dalvik is quite a leap from atm. The fact that they recommend avoiding virtual methods in a language with the concept deeply seeded philosophy of abstraction is disconcerting and frankly worrying. I hope that the virtual machine gets to the point where that facet and the many other performance penalizing pieces beco
Re:News that matters? (Score:4, Insightful)
I never saw multitudes cry out for C# for mobile games development, either, but Unity appears to be a very successful product. You don't need people crying out for a product to make development worthwhile.
Maybe if .NET 3 and 4 never happened (Score:3, Interesting)
.NET 2 was a competitor to Java. Since then I believe the API has gone downhill so much that it really hinders development. Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?
Like all MS software, they will blunder on thinking they still drive the entire industry, completely ignoring EVERYTHING their customers tell them and fixing only security issues. Like Windows, .NET will one day be something we look back on while shaking our heads in wonder, with the same feeling you would get watching someone dial a rotary phone.
Re: (Score:2)
Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?
I'm intrigued... What data structures are you talking about? I don't remember seeing that behavior.
Re: (Score:2)
I wish I had mod points. My guess is the microsofties here will mod you down for truth.
Re: (Score:2)
I'm curious what your example case is. What data structure? What are you trying to do with it?
I'm primarily a system administrator, and in the past few years I have seen nothing from Microsoft which hasn't shown a drastic increase in the amount they're listening to their customers. They've been fixing several obviously broken products and providing a lot of tools which make my job easier. The departure of Gates has been one of the best things for the company. It's slow in some areas, yes, but Microsoft
Implying.. (Score:2)
"...or will the bad blood between the F/OSS groups and Microsoft make this a dead end?"
>>Implying that F/OSS groups are the only ones or even the majority that makes apps for android.
I hear that .Net framework is pretty good for building good games. So it will be interesting to see what comes out of this.
Great for WP7 migration! (Score:5, Interesting)
It's really great that there's finally a tool to make life easier for all the developers building Windows Phone 7 apps in C# that want to move their code base to the Android platform!
Re: (Score:3)
And even better news that the Mono patent virus is now going to be directly infecting one of Google's flagships! Yay for Redmond and its evil little minion de Icaza.
Re: (Score:2)
Re: (Score:3)
Show a little respect! This is slashdot! Not everyone here knows binary!
Worst /. article ever? (Score:2)
First, this is just flamebait.
Second, the only people who want everything to be done in one language are those clueless zealots everyone finds an excuse not to hang out with after work.
Third, even if one language completely dominated the niche category of handheld consumer devices, it would mean nothing outside that niche.
Slow news day?
Re: (Score:2)
+1 insightful
I dunno about being the worst article (stiff competition) but spot on about "people who want everything in one language"
I have been teaching Android development for over a year, and the biggest wankers are the ones who come to argue rather than learn.
Real engineers don't have a problem soaking up another platform.
Re: (Score:2)
Re:Worst /. article ever? (Score:5, Insightful)
With regard to your "find an excuse to not hang out with after work" comment. Actually, it are pseudo-academic language snobs who are avoided. The kind who love adding layer upon layer of complexity (including switching languages and tools all over the place), and take pride in their l337 skills for doing this. They can be great developers but are shitty *designers* (too bad they're usually so clueless at design they never even see or consider this aspect). Remember, great design is about *removing* stuff. As Einstein said, "As simple as possible, but no simpler" [note: this is actually misquote of what he actually said, but it is commonly enough used and conveys the same meaning in fewer words]. That means *fewer* languages, not more, should be preferred.
Re: (Score:2)
Actually, it is *terrible* design to use more than one language if you don't have to
I think there are exceptions. Python with some C for the fast bits can be quite compelling.
And I don't know if it counts, but mixing C and C derivatives like C++ or Objective C is pretty common.
I think it depends on your requirements. Obviously it is ideal to KISS, but if writing most of the code in Python saves you months or even just weeks of coding time, then it is hard to say that a straight-C implementation is "better".
Re: (Score:2)
The "one language to rule them all" bit isn't about having everyone use the same language, but about having a language supported on every platform. Java, AFAIK, isn't supported on iOS which is why it's considered a "failure" in that respect, and obviously nobody outside Apple uses ObjC for anything serious so that one's dead as well.
Kinda pricey... (Score:5, Informative)
This just in: "Mono for Android includes the core Mono runtime, bindings for native Android APIs, a Visual Studio 2010 plug-in for developing and testing Android applications, and a software development kit (SDK). The enterprise edition costs $999 (£613) per developer per year, including maintenance and updates. A five-developer enterprise licence costs $3,999 per year, and a professional edition costs £399 per developer per year."
http://www.zdnet.co.uk/blogs/communication-breakdown-10000030/novell-releases-mono-for-android-toolset-10022167/?tag=mncol;txt [zdnet.co.uk]
Re: (Score:2)
This will not rule the world (Score:4, Insightful)
First, it is mono. Beside any technical argument. There are a lot of people who do not like mono, because it is an incarnation of evil (alias MS). I am not saying that it is, but many people feel that way. So this is definitely one obstacle. Second, Android and iOS are different enough to be different on the low level aka programming language level, which will result either in compatibility libraries which are wrappers and resemble at some point internal DSLs. And they result in another abstraction layer which costs memory and CPU power. When you used an iPhone 3G/3GS you already find your phone to slow. So why torture yourself with slow software. And fourth, there are other cross platform approaches which use external DSLs which do not introduce another layer of abstraction at runtime, only on built time. For example: http://code.google.com/p/applause/ [google.com]
Re: (Score:3)
Yeah, but look at your alternatives. You can use Mono, aka .NET, aka Microsoft. Or you can use Java, aka Sun, aka Oracle, aka plaintiff in litigation against Google over Java in Android.
Giant douche or turd sandwich?
Re: (Score:2)
You are confusing a language with a UI (or hardware) library. Sort of. It's a bit more complicated than that, but I'll leave it as that to not further confuse you.
In actuality, .NET, mono, monotouch, and monodroid are a collection of base class libraries, interpreters (or compilers), with each diverging with their own separate UI/hardware libraries. Additionally, the later two (or three) are compiled, with no "additional abstraction at runtime".
Mono for Android! (Score:4, Funny)
Re:Mono for Android! (Score:4, Informative)
http://www.mono-project.com/Compatibility [mono-project.com]
Re: (Score:2)
I'm not sure how one could look at the chart at the provided link and take away that Mono is missing "many" major components.
With the exceptions of the limited implementation of WCF, which ends up forcing you to use painful (albeit well-documented) approaches for web service access, and WPF, for which you can use the workaround of using any other windowing library with a C# binding, most of what's missing is stuff few people would miss anyway. For example, the Entity Framework is a rather clunky and immatur
Re: (Score:2)
While I understand this position, it is mostly a 'fail' for the Windows C# crowd. Having a non-portable stack is a big issue. Non-portable (ie. non-standardized) libraries means you can't trust whether it is going to be on your *customers* chosen platform or not (and big customers get to chose the platform, not the developer). Trying to sell a Gtk# solution would work in some places, but there are
The nebulous danger (Score:4, Insightful)
As I understand it, here is the chief complaint that people have about Mono: Microsoft could have some sort of patents that could apply to Mono; and Microsoft could in the future use these patents to do something bad.
I have never seen any specific examples given, it's just a general "there could be some patents" argument. In fact, I believe the theory is that these could be "submarine" patents, not known now but lurking invisibly.
Here's a specific example. This is a long essay [techrights.org] about this very issue. What is the danger if we use Mono? "[C#] was developed inside Microsoft, so it's likely they have many patents to cover different aspects of its implementation." Got that? "it's likely" Microsoft has "many patents". Citation needed.
This is the 21st Century, and patents are not only public, there are patent search engines. Where are the specific examples?
The situation is even crazier due to the passage of time. Microsoft introduced .NET in the year 2000. It is now the year 2011. Patents in the USA today have a term of 20 years. Presumably these submarine patents were not filed the same year as .NET was introduced; that would be far too obvious... they were probably filed a year or two ahead of time. So presumably these patents have a maximum life of under 9 years, and probably under 7 years.
In the past 11 or 12 years, nobody has noticed these deadly patents, lurking. But wait: these could be true "submarine" patents, where the patent was filed but not granted yet, and Microsoft is using sleazy tricks to extend the filing period and delay granting the patents. This implies that the patent must have been filed before 1995, when the US patent system was changed (patent term went from "17 years after patent granted" to "20 years after patent filed", specifically to fix the problem of submarine patents). Thus, a true "submarine" patent would have to have been kept going via sleazy tricks for over 16 years now, and nobody has noticed it yet.
So, if I understand correctly, we shouldn't use Mono because it could be a trap. Microsoft could have patents nobody has noticed for a dozen years that will expire within the next nine years that could apply to Mono. Or else they could have pending patent applications that have been pending for over 16 years without anybody noticing; those would apply for 17 years after the patent grant finally occurs in the future.
And if the above turns out to be true, and you wrote a program in C#, what would Microsoft's remedy be? Would you be forced to pay them huge sums of money? Would you be forced to give ownership of your source code to Microsoft? Not likely, and anybody who claims it is likely needs to provide legal precedents showing such a remedy in a similar case. No, the only realistic remedy would be that you would have to choose between buying some sort of licensed version of Mono (to comply with the patent licensing terms), or stop using Mono.
And the obvious exit strategy is to rewrite your C# app in Java. That would be a pain, granted, but hardly the end of the world.
And that is even assuming that Microsoft was successful in asserting these hidden patents. After offering C# up as a free standard, and not taking any action for a dozen years, to suddenly assert hidden patents would leave Microsoft wide open to the "unclean hands" [wikipedia.org] legal doctrine. It's hard for me to imagine Microsoft prevailing in this.
And nobody has yet proposed a motive why Microsoft should do this. How does Microsoft gain by backstabbing the C# community? In the near term they could gain some patent licensing fees, but in the long term they would be alienating people they have been trying to woo. How likely is this, really?
So, in conclusion: because of this nebulously scary potential situation with possible unknown Microsoft patents, Mono and C# are
Re: (Score:2)
Re: (Score:3)
As I understand it, here is the chief complaint that people have about Mono: Microsoft could have some sort of patents that could apply to Mono; and Microsoft could in the future use these patents to do something bad.
I have never seen any specific examples given, it's just a general "there could be some patents" argument. In fact, I believe the theory is that these could be "submarine" patents, not known now but lurking invisibly.
That's mostly because no-one wants to go looking, not because they're hard to find. For example there's US patent 6951022 [patentstorm.us] which covers using .Net delegates to dispatch events that have two arguments, one identifying the event source and another that's a structure containing the event arguments. Seems oddly specific, but GTK.Net does exactly this, and it's likely that many other .Net and Mono-based apps also do so because they're following Microsoft's coding standards. That's enough to take out pretty much e
Re: (Score:2)
That should of course be Gtk# not GTK.Net. Bleh, it's getting late.
Re: (Score:2)
The limits of my C# knowledge stand revealed. I do not know very much about this stuff, at all.
Are you saying that Mono is fundamentally broken, because this feature is essential to Mono? Would it be possible to rewrite Mono to not use this feature, if Microsoft ever started asserting this patent?
And, while I am not a patent lawyer, isn't it generally true that the more specific the patent, the easier it is to work around the patent?
Also, this patent expires in 2021, so it must have been filed in 2001, wh
Re: (Score:2)
It's one issue but not the only one - and could be well explained by mono not being very popular, it doesn't matter how much time has passed if there's not enough in the trap to be worth springing it. Another issue is that almost everyone writes for Microsoft's CLR. No matter if it's spec ambiguities, bugs in Microsoft's implementation or bugs in Mono's implementation the most common answer you'll get if it works on their version and not mono will be "dunno, use Windows" as if mono is something akin to WINE
Re:The nebulous danger (Score:5, Insightful)
Microsoft could end the patent issue once and for all by granting a royalty-free license for any and all patents needed to implement a C# runtime. They have not done so. That suggests that they reserve the right to use those patents against any competitor who becomes a large enough threat, or any one else with deep pockets.
IBM has more patents than anyone else, yet they give patent grants in situations like this. Many companies do. Sometimes growing the market by making standards more affordable is better than protecting your share of a smaller market. Microsoft's actions speak louder than their words, and their actions come down on the side of reserving the option of shutting down the use of C# in ways that Microsoft doesn't like. You think that it's silly to fear that Microsoft would do that, I think it's silly for Microsoft to fear that someone might someday use Microsoft's C# patents to harm Microsoft.
Re: (Score:2)
Honestly, in this case the patent problem is wholly beside the point. You could choose Mono and carry an extremely low risk of patent litigation (this kit is produced by Novell which has a good relationship with Microsoft including patent detente) or choose Java... which is currently the topic of ongoing patent litigation between Google and Oracle.
Gee, which of these two is really less appealing?
A human-to-smartphone infection? (Score:2)
And here we keep telling clueless users that "it's not that kind of virus."
Cross platform compatibility! (Score:2)
Can we get... (Score:2)
Penicillin for Android next?
To help with mono infections?
(Yes, I know penicillin doesn't work on real world mono. It's a joke.)
Re: (Score:2)
The answer is No. (Score:2)
Mono, is a framework and not a programming language. And it does incorporate the basic stuff of the
Re: (Score:2)
Actually, Mono runs all of the non-UI and non-WCF 4.0 code I have. Just fine. And it runs most of the WCF client side stuff just fine.
That includes Linq, and almost everything everybody uses on a daily basis.
It should be pointed out that Mono doesn't magically make the UI differences between iOS, Android and whatever go away. You still have to use native widgets per platform.
So, you can make a core assembly, that you share between all three, and independent UI's on top of that. Sounds like a great situation
Oh please please please please (Score:2)
If you were smart, you'd reinstate your Java to C# converter.
Signed,
Fed up Java dev...
Kill it with fire (Score:2)
PYTHON!!! (Score:2)
What does Java have that Python doesn't in two weeks?
Re: (Score:3, Funny)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Every time you do that god kills a kitten...
and uses the fur to wrap a pair of handcuffs so you can get off the way you should, via punishment!
Re:too pricey (Score:5, Interesting)
Crazy. Would love to use it, won't touch it with a barge pole at that price.
Re: (Score:2)
Re: (Score:2, Insightful)
Re: (Score:2)
Nah, I give a shit too. Now that the MS vs Linux battle has come to the 'like kicking a puppy' stage, there's not a whole lot of reasons to continue the hate-fest on MS. If anything, the current attitude of Apple should be hated. Hell, Apple's bigger than Microsoft in stock value now. (Although that could just be the big boys giving Jobs a magic sendoff before he kicks the bucket. Then it looks like the world is going to go back to being dominated by IBM and Java, which is just going to end up back to the o
Re:.NET - where deployment is just a word (Score:4, Funny)
I can write a .NET program on native windows and when I launch the EXE on a machine with no .NET it will simply fail with an error number. It doesn't ask you if you want to put .NET on or even explain to you that you need it to run the program, it just fails.
So... the same thing that happens whenever you launch any other program with its required libraries missing? Try copying a native VC++ program to a system that doesn't have the VC++ runtime installed. It won't spoon-feed you information about what the VC++ runtime is, why you need it, where to get it, and how to install it; it'll just give you a cryptic error.
If you want to do deployment properly, you need an installer. With Visual Studio it's dead simple to make a setup program that'll check for prerequisites like .NET and install them automatically.
Re: (Score:2)
Re: (Score:2)
Mono has support for the language C# 4.0 targeting the CLI. The libraries may not be fully caught up with the libraries that ship with .NET 4.0, but the most important pieces are there. I'm not sure why you think otherwise.
Even Mono for Android is advertised as supporting a subset of .NET 3.5 (which uses C# 3.0) which includes all the languages features you mentioned.
Mono for Android even uses a Visual Studio plugin, making Visual Studio its preferred development environment.
Re: (Score:2)
Actually Mono runs 4.0 code just fine. Obviously you can't use WPF on it.