|
|
|
| Authored by: Anonymous on Wednesday, February 06 2013 @ 04:24 AM EST |
MS's branding gets me very confused.
Wasn't Mono supposed to be a Silverlight environment for Linux?[ Reply to This | Parent | # ]
|
| |
| Authored by: scav on Wednesday, February 06 2013 @ 05:10 AM EST |
Mono is actually reasonably good as *part* of a cross-platform development
environment for mobile devices, partly because Java and Objective C are so
horrible they make C# look OK, and in any case even if they were only equally
bad, there isn't any other single language you can use as a common code
base for both platforms. I'd really prefer Python, but Google have set their
face against it so there's nothing to be done.
I use Unity3D at work, which uses MonoDevelop for compilation. I don't feel
any tribal unease about using C# in this niche, because mobile devices are
after all one of the areas where MS don't have and are unlikely to acquire a
monopoly.
---
The emperor, undaunted by overwhelming evidence that he had no clothes,
redoubled his siege of Antarctica to extort tribute from the penguins.[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Wednesday, February 06 2013 @ 04:33 PM EST |
First: Legal liabilities. Microsoft has threated Linux including with
patents. MS and Novell entered into a patent agreement by which the only
individuals protected (and that's questionable protection) are those who acquire
the product direct from Novell. Anyone else has a clear litigation risk. My
humble non-legal opinion based on my reading of the terms the two had released
to the public.
Second: Code quality. It is reasonable to expect a
company who has entered a licensing arrange to make use of said product which
was licensed. My humble expert coding opinion is that MS code is incredibly
poor quality with security as an after thought rather then as a foundation.
Additionally, I prefer to avoid bloat. As a result, I'd rather not have MS code
on my computer. I like the fact my computer runs cleanly, fast and doesn't so
much as hiccup.
Third: "It Just Works!". Microsoft has a well documented
history of changing API's and not informing their "partners". This results in
failing products. You yourself have identified that the API's that the code is
supposed to be compatible with isn't complete. I don't want to start using some
application that relies on Mono just to have it completely unusable someday
because MS decided to change their API's.
RAS[ Reply to This | Parent | # ]
|
|
|
|
|
