Quoting Carsten Munk <[email protected]>:
* What are you waiting for to happen in the MeeGo project?
For openers, some specs:
1. RAM and processor capacity of the target devices. I'm especially
interested in what the *smallest* device is that will run MeeGo.
2. Links to documentation, so I can look up answers to questions like
the Perl integration question I posted to this list.
3. *Schedules* - especially, when are code freezes and hard marketing
deadlines? I need to make business cases for things that I build, and
I can't do that without knowing when I'll be able to put real software
in the hands of real people solving real problems for them for money.
I need to make hard decisions - do I port to / develop for MeeGo
pocket-sized platforms / UIs, or do I stick with "larger" things with
actual keyboards and more RAM / CPU power? Am I stuck with C++ for
efficiency reasons, or can I get away with a scripting language? And
which scripting languages are going to be feasible in the pocket form
factors?
* Do you know what is currently blocking these things to happen, if so, what?
What's blocking me at the moment is a complete lack of information
about what the capacity of the smallest MeeGo device will be. The
other stuff I can figure out once I know how big my sandbox is. ;-)
* What would you contribute with if these things happened? What area,
what specific things - how can you help, where's your talents in this
area and interest?
Performance testing / profiling / tuning, trying to get the most
capable scientific calculation (symbolic and numeric) into the
smallest form factors, algorithmic composition and other musical
applications.
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
