Mono 'discussion' gets interesting: Where does Ubuntu get the money?
--------------------------------------------------------------------
This is (a non exaustive) list of what canonical has been suckered into
paying for developers so far to be written for micoshaft's mono to get it
inside ubuntu:
libmono
libmono1.0-cil
libmono2.0-cil
libmono-accessibity1.0-cil
libmono-accessibity2.0-cil
libmono-addins0.2-cil
libmono-addins-gui0.2-cli
libmono-cairo1.0-cil
libmono-corlib1.0-cil
libmono-corlib2.0-cil
libmono-data-tds1.0-cil
libmono-data-tds2.0-cil
libmono-dev
libmono-mozilla0.1-cil
libmono-peapi1.0-cil
libmono-peapi2.0-cil
libmono-security1.0-cil Sheesh! Give me break!
libmono-security2.0-cil Sheesh! Give me break!
libmono-sharpzip0.84-cil
libmono-sharpzip2.84-cil
libmono-sqllite2.0-cil
libmono-system1.0-cil
libmono-system-data1.0-cil
libmono-system-data2.0-cil
libmono-system-runtime1.0-cil
libmono-system-runtime2.0-cil
libmono-system-web1.0-cil
libmono-system-web2.0-cil
libmono-winforms1.0-cil
libmono-winforms2.0-cil
mono-1.0-devel
mono-2.0-devel
mono-common
mono-debug Yeah right!
monodoc
monodoc-base
monodoc-browser
monodoc-manual
mono-gac
mono-gmcs
mono-jay
mono-jit
mono-jit-dbg
mono-mcs
mono-runtime The first thing to be targetted by a micoshaft lawsuit
mono-utils
In my mind, canonical has been suckered into paying for building a mono
infrastructure and mono code at great expense instead of faster C and C++
programs useable by the wider developer community. This is the purpose of
mono! And it seems to be draining a lot of money out of canonical
successfully!
Every time micoshaft says jump, the mono paid for developers get paid
at great expense to canonical to rebuild ALL that vendor lock in
crapware above.
If I were canonical, I would see spending money on all that crap
as an expensive waste. Change the status for all this crap as third party
software instead of ubuntu software, and spend all the money on
Desktop Linux, and re-useable C and C++ code instead of mono code.
C and C++ is also more easier to debug than mono code. Mono coders
wastes a lot of developer time trying to make stuff work and debug
so they are not at all productive or competitive compared to general
purpose C/C++ coders. And mono coders make slow software compared
to C/C++ coders because they are trying to satisfy Redmond
and their demands first, open source and free software demands second.
Every time there is a virus out break, micosahft makes money.
It make you wonder how the misfortunes of others is being tuned into
a gain for micoshaft through consultancy and product upgrades.
In that same way, every time micoshaft marketing plops changes the rule book
fir .NET, its what happens when you don't jump that is more interesting (to
micoshaft).
If Linux software has been accepted into an establishment on the back
of mono crap, and canonoical didn't change the software because micoshaft
marketing plops knows canonical don't have the money or the technical
consent to do something stupid like intruduce an obvious security
vuln, micoshaft will step in there into those corporate
seats with their crap and sell it against Linux as 'working code'.
The stupidity of mono and micoshaft funded crap will never end until it is
removed from mainstream code.
Linux kernel developers learned that a long time ago.
If something is stupid, then remove it immediately and wait patiently
for its open source and GPL'd replacement.
Don't operate on the priciple that someone holding
a gun to head is a manageable risk. It isn't manageable if
micoshaft marketing plops are involved. They will pull that trigger
to make a quick buck. It happened with Java, it happened with FAT,
and it will happen with mono and every idiot developer conned into
using it.
If you write your applications in C/C++, you can wait years
before you need to change it. And even then, it will be absolute minimal
changes. Unlike mono crap which will all depend on micosahft and its
published and unpublished APIs influencing mono developers no end.
|
|
