2008/5/21 Nkoli :
In this case, openmoko is still being marketed to developers and is
still alpha software. As such, I have a reasonable expectation that I
will want to hack a fair number of the applications it ships with. So
that is a valid complaint. Of course, you could simply rewrite each
application in your preferred language, but that's a waste of effort.
Or you could not mess with the applications written in a language you
do not prefer. Or you could wait until there's a more severe need and
then learn the language in question and start working on the
application.
With desktop Linux, most things are sufficiently mature that I expect
not to have to hack them. So the language they are written in is far
less important.
Of course, one person's opinion doesn't matter much, as long as there
are plenty of people familiar with the languages that are commonly
used in openmoko. I think there are far more people who can
effectively write C collaboratively than who can effectively write C++
collaboratively.
The larger issue is extending a C++ codebase in another language.
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Justin Piszcz | exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Radu Rendec | htb parallelism on multi-core platforms |
