Slashdot Mirror
Attachmate Does the Right Thing For Mono
mikejuk writes "Attachmate, who recently decided to dump the Mono development team, has done the right thing in allowing Miguel de Icaza's new company, Xamarin, a perpetual license to all the intellectual property of Mono, MonoTouch, Mono for Android and Mono for Visual Studio. This allows them to continue to develop and sell the products. Of course this income might just give them the time needed to support the software, which is a good thing, as Attachmate has also handed over the support for all existing customers to Xamarin."
Whether or not you think Mono has value, granting a perpetual license to it to someone who will do something with it was the right thing to do. Allowing a particular technology to be continued rather than just sitting on it because they have no use for it should be applauded. I only wish IBM had done this with OS/2 many years ago. Who knows what would have become of it.
Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
Thankfully, the ecosystem of computer languages and platforms is not subject to the mouth-frothing whims of hard-core ideologues. Those of us who program for a living are not interested in your rants.
If Palm did this with BeOS back about 5-6 years ago. BeOS didn't really compete with them. It did, however, compete with their biggest contemporary competitor and one of their future competitors that they should have seen would soon be a major rival. Had Palm given Haiku developers the same deal with BeOS, it would have been as disruptive for Microsoft and Apple as if a little enemy state were to hit the US with a high altitude EMP on a weekday.
like eComStation ?
Politics is Treachery, Religion is Brainwashing
Mono and by extension .net is a piece of shit and the only people who care are shills and the people that have been convinced by the shills to believe the hype. Even MS is abandoning .shit for javascript/html5 in their next OS. Hahahahahahaha
Well done. I too would post as AC if all I had to say was an idiotic, embarrassingly stupid comment like that.
Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
Why not just call it Ximian rev. 2.0?
#DeleteChrome
No, SuSE is one of the main reasons that Attachemate bought Novel. They have moved the SuSE headquarters back to Nuremberg Germany where it began, and the relationship with the OpenSUSE project is not expected to change.
"Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language" link
is this the end of .NET?
eComStation is a "barely" warmed over (as in bugfixes only) release of OS/2 Warp 4 which IBM last shipped in 2001. Had IBM released the source code to someone who might actually continue development (even if not open-sourcing it) there's no telling what kind of OS it could have evolved into by now.
Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
With the exception of the fact that most people who create programming languages and platforms tend fall into highly opinionated ideologue category e.g. Larry Wall, Guido van Rossum, Matz, Linus, DHH, Theo de Raadt, etc
And I'm not interesting in *their* rants, either. I use their software, but I don't have to read their manifestos. Exhibit A: Richard Stallman.
Not something you see often nowadays, what with patents and copyrights being thrown back and forth in endless litigation and cutthroat corporate espionage.
That said, these guys are pretty awesome for doing that. In a way it lets us know they actually care about the improvement of the industry, even if they couldn't support Mono themselves. Round of applause ol' gents.
What's the point of writing portable code (that is the benefit of using Mono, right?) if I have to buy two seperate IDEs to actually make use of it?
as trolling as that was, it does seem to have a bit of truth - Microsoft has kicked Silverlight to the curb by targeting it pretty much only for mobile and news from inside Microsoft seems to indicate they are ditching .NET for html 5. Knowing Microsoft, however, and seeing their open attack on the security of WebGL, I expect them to port over their Silverlight Direct 3D code and use that instead of using WebGL because a browser without proprietary features would be very un-Microsofty.
The thing that isn't often mentioned, however, is that Microsoft demonstrated Silverlight being compiled into html/javascript at their developer conference (or so I have heard) - that would be nice, and very un-Microsoft of them - write in Silverlight/.NET and run on html 5 browsers. Still, I bet proprietary tech gets in there as I mentioned above, and if so, Miguel's work will still be relevant.
I'm going to the special hell for this, but I misread the headline as "Attachment does the right thing for mono", and I thought to myself -- attachment is what causes mono. Well, that and kissing. Then I realized I was on slashdot, and nobody would get the joke...
#fuckbeta #iamslashdot #dicemustdie
Mono and by extension .net is a piece of shit and the only people who care are shills and the people that have been convinced by the shills to believe the hype. Even MS is abandoning .shit for javascript/html5 in their next OS. Hahahahahahaha
.Net is not bad at all, although not a solution for every problem. As an alternative to Java, it's better in every way except cross-platform compatibility. It obviously doesn't fill every hole that C++ fills.
.Net. Nobody with any serious judgement believes that will happen, or even be a push.
You're very wrong.
You completely misunderstand the role of Javascript/html5 in future MS products. It's an option for simple apps; it would be ridiculous to think MS will push it to replace
However, I wouldn't do any development in Mono. It's nice architecture, but there are too many potential legal and social problems with it.
.Net is not bad at all, although not a solution for every problem. As an alternative to Java, it's better in every way except cross-platform compatibility.
.Net is inferior in the one aspect that matters, then, as total cross-platform compatibility is the raison d'être of Java.
Circumcision is child abuse.
How do we know you didn't? You are the MS whipping boy after all?
May the Maths Be with you!
That's like saying Java is superior to C because the latter being "portable assembly" was its whole purpose. Yes, it was so at the beginning, but the language and the frameworks built on top of them grew to encompass much more than that.
No problem is insoluble in all conceivable circumstances.
you think the work involved in those separate platforms should not be compensated?
No, I think $650 for the bundle is a bit too steep for a microISV. As of right now, the best way I can see for a small developer to get a cross-platform phone application in front of an audience is to write the back-end in C++, write front-ends in Objective-C for iOS and Java for Android, and ignore Windows Phone 7.
Does anyone else find it really discouraging that someone doing the right thing is considered breaking news?
*sigh*
And why would that be? Seems all I hear from those Mono lovers is that those who are opposed to Mono and De Icaza's little ploy have no clue. Yet I am still waiting on what the right clue is. Why is there no patent threat in Mono? Why is it safe to use? Why will I never be sued by Microsoft when I deploy/sell Mono crap? Give me proof and nothing but proof. Thus far all I hear is a thundering silence.
Really De Icaza, posting as an AC? How's the funding going? Did Microsoft find you a new Baystar yet?
Microsoft's community promise... it is a legally binding statement about where you as a developer stand when using Mono.
If you have a problem with the win forms parts not being included, then don't use winforms. No one seems to give a shit about using one of 20 different tool kits with C++, but for some reason, not using winforms with C# on the mono platform is some sort of barrier that makes developing with it impossible.
Xamarin supporting Attachmate's Mono stuff means a lot to me, as a developer. I work for a company that does a lot of Mono-based consulting. This is going to sound like advertising, but having Mono for Android and MonoTouch makes life as a mobile developer easy. For example, my coworkers have been working on an iPhone application for a client using MonoTouch, using MonoTouch.Dialog. The client wanted a dual launch with an Android app, and since we were using all Mono-based projects in an MVC pattern, all we had to do was rewrite the UI for Android. Most of the screens had a lot code that could be reused with MonoDroid.Dialog. That means that even though the iPhone project started two months before the Android one, it only took one month to catch up to iPhone. That's two months that I spent utilizing my time towards other clients, and two months that we didn't have to bill to this client. When I punch those numbers into my calculator, it makes a happy face.
news from inside Microsoft seems to indicate they are ditching .NET for html 5.
Where is this 'news from inside Microsoft'? Do you have any idea the vast amount of functionality that would be lost if you ditched .Net for HTML5? Ditching Silverlight for HTML5 seems logical but certainly not the whole of .Net.
Knowing Microsoft, however, and seeing their open attack on the security of WebGL, I expect them to port over their Silverlight Direct 3D code and use that instead of using WebGL because a browser without proprietary features would be very un-Microsofty.
I for one do see the danger in WebGL, i think it's a brilliant enabling technology (particularly friendly to me because i do most of my 3D coding in OpenGL) but that direct access from a webpage to the GPU (which is pretty much the most volatile piece of hardware in computers today) doesn't seem very safe, video drivers are unstable at the best of times.
.Net is inferior in the one aspect that matters, then, as total cross-platform compatibility is the raison d'être of Java.
Total cross-platform capability? You can only run Java where you've compiled it to native platform-specific code or where there is a platform-specific JVM, just the same as with .Net code.
There are very few parts that are not covered and those parts are not part of the ECMA standard. Seriously... there are replacements for WCF and WinForms and the other small number of namespaces that are not covered.
A major problem was that IBM insisted on 286 compatibility, which meant a 'back flip' between real and protected mode.