![]() |
Re: And where is the people from Nokia who worked on Maemo and Meego?
What are these MS (trademark) Tablet (registered trademark) operating systems that aren't MS (trademark) Windows (registered trademark) operating systems?
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Look at the bottom : This is a satire, for the real Qt website go to qt.nokia.com. XD |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
The 1.0 incarnation is getting slagged by techno journalists because it is so heavily locked down and underacheiving, one journo called it something similiar to symbian in 2001. That isn't good when that is the kind of thing google shows up as a review. http://www.theregister.co.uk/2011/02...or_assurances/ Xbox has been a nightmare for M$ The red ring of death cost them a $billion to sort out for example. http://www.theregister.co.uk/2007/07..._death_charge/ It has been voted appalling for reliability http://www.reghardware.com/2009/09/0...eport_sept_09/ And M$ didn't even deny a 54% failure rate. http://www.reghardware.com/2009/08/2...rvey_response/ And lets not also forget the 'Zune' and 'Kin'. So they might push a good idea like kinect but at the cost of two other failing ideas. And then compare the % of market for Bing (renamed three times in as many years) still third in the search markets.) Mobile OS market share for Winmo put them at 4th, some would say 5th. And IE9 which according to the hands on reviews. Heavily linked with windows 7, so won't work in XP And as one developer of a plug in put it. "The only status is the "won't fix" one. We'll not join Microsoft in perverting the net again." Because it is M$ standards again, not world standards and is designed to run for windows 7. http://www.theregister.co.uk/2011/02...didate_review/ M$ need Nokia much more than Nokia need M$, and this is from me who hates Nokia. Some interesting articles on Nokia from the last few days. http://www.theregister.co.uk/2011/02...s_phone_meego/ http://www.theregister.co.uk/2011/02..._more_details/ Someone from Nokia in this actually claims the N900 was a success. So if the one Meego handset is a success like the N900, you might get more. LOL http://www.theregister.co.uk/2011/02..._an_ms_trojan/ |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Does anyone know where Alberto Torres has gone to?
I don't know the guy, but what do you think of the possibility of him setting up a new MeeGo/Qt-based company and poaching a load of ex-Nokia developers? Maybe I'm just dreaming... |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
We are all locked in this silly "ecosystem war" because manufacturers want their platform to become a de facto standard, like Windows in the PC. If you want the application(s) you have to buy my handset or buy my OS. Or buy both. Qt has the potential to precisely disrupt that. Empowering developers to, at last, be free of all platform leashes and just doing what they do best: code. Empowering users so they could use any HW or SW platform and still get what they want. And off course manufacturers would fight tooth and nail against it, because they would become "dumb boxes" for software, just like carriers are becoming just "dumb pipes" for data. Against all odds, I'm hopeful for Qt. And I will buy the MeeGo handset, if only to throw it to the face of all the naysayers. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Speaking of ecosystems: http://tabulacrypticum.wordpress.com...he-rest-of-us/
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
But the leadership inside Nokia seems to get wellpayed from Microsoft soo I guess thats more important for them in shortrun than being following W3C standard and such... |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Meego needs Dalvik VM so Java-developers can transfer from Android to Meego and also Meego would have enough applications to go over "critical mass" at once.
I know couple of Android-developers, who never did like Qt-ecosystem because they couldn't use modern language like Java. Nokia made a mistake with QtJambi to ignore it. QtQuick, QT+QTML+C++ is a mess with two syntaxes and C++ itself is error prone and usually 1/2 as productive as Java or 1/4 as productive as Python. If there is a modern (2011) hardware; dual-core >1Ghz CPU with 1GB RAM memory and stuff (see Samsung Galaxy S2 hardware) it wouldn't matter if essential OS applications would be coded with QtPython or with QtJambi instead of C++. And nothing else would sell anyway if Nokia is looking to the high end with its Meego device. WP7 won't even support dual-core platforms, and it's very likely WP8 won't be ready in the start of 2012 as planned. Nothing forbids having Android-apps in Ovi either. One solution is to have FOSS-Dalvik to be developed (summer job) or then just buy Alien Dalvik license to every Meego phone. It surely is cheaper than WP-license from Microsoft. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Dalvik on Meego would just harm the platform its not that simple tooo integrate. two different beasts. And by saying android devels knows best is like saying Microsoft knows best. and dont forget tghat more advanced games is still written in C++ anyway including Android. and about wp license issues Microsoft infact PAYED nokia too use wp7. bussines as usual |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
If WP7 will not run on dual-core systems at first, that I can really see it substituting Symbian while MeeGo is reserved for more powerful/future devices... |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
I thought I'd put my two bob in......
The answer to the question in the thread title; "and where is the people from Nokia who worked in Maemo and Meego?" They all killed themselves after being made by some marketing wanker to use the word "ecosystem" repeatedly. Just how many points is this word worth when playing ******** Bingo? |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Quote:
As with Symbian, multi-core support first comes to kernel and later the user space processes. So WP7.5 may have multi-core support in kernel already, but I doubt not in user processes still. WP8 is planned in the first half of 2012. Rather long time for Nokia to wait to get a "flag ship" device out. We all know IT-projects also are delayed and postponed, so wouldn't be surprised if WP8 comes end of the 2012. MS Vista was delayed several years. And in Linux, back of the days, having all OS code thread-safe took years. So thinking all that, I do not understand Elop's point at all. Yes, it may still be long way to Meego phone GUI, but WP-plaform is far from ready and surely takes more than 12 months. If Nokia will bring low end smart phone as its first WP-phone, it will fail most likely. And nothing but dual-core >1GHz, 1GB RAM and (well just see Samsung Galaxy S2 what has to be there) will make a "flag ship" device now 2011. The so called "plan B" was much more wiser, because in that Microsoft has responsibility to get their **** together. Nokia will provide the hardware and then WP-phones are tested in North-America if they work or not. Nokia should just say what it needs and Microsoft should provide if they want their WP-platform to survive. But Nokia should concentrate fully in its own software development to its own plaform, Meego UX. If Microsoft fails, the time has not been wasted. But as long as Elop is CEO, I doubt he will allow any high end hardware to end up in Meego phone, because it would be a thread to his next MS-CEO plans. Also having Dalvik VM in the first Nokia Meego-phone would be a killer solution and many Android-developers would transfer to Meego, but once again Elop prolly won't allow it to happen because it would be a thread to his MS-ecosystem. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
They all went to live on a nice big farm out in the countryside.
Don't worry, they will be very happy there and will have lots of room to run around, coding and programming in the fields there. You want to go and see them? um, well you see the farmer is very busy and it is a very long way away. By the time we got there they would all be asleep, and you would probably be asleep too and we'd have to come straight back. So, don't worry, just think of gthem being happy and that will make you happy too. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Productive, as you get more stuff done with lesser time, with lesser code, with lesser bugs and overall. I do not know if there is statistical studies yet, but the common sense with many who know all the three languages and have programmed with them, are that productivity goes something like C++ is 1/2 productive as Java and Python is 4x productive as C++. You can try to google with "Python productive Java C++" And we should face the facts now. Threre will NEVER now be as much Qt/C++ developers as there is Java/Android developers. What Meego phone will need at once when it is shipped, is lots of applications, or either it will fail. Having Dalvik VM would be a big plus and immediately Meego would have thousands of developers and tens of thousands applications. What I also said, that maybe rather than struggling with rather messy QtQuick and C++, Meego OS GUI could be written with QtJambi/Java or QtPython instead to get things more quickly ready and working. It pretty much seems like current methods and tools are not productive enough. The Meego phones should anyway at first be in the high end catogory, so they will have at least 1GB RAM and dual-core CPU. It wouldn't matter to have even two or three VMs running on the system (Python VM, Dalvik VM, Java VM). |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Now excuse me I have to go and put some shelves up with duck-tape. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
Its like saying every developer must use java or else theyr stupid, how dumb is that? personally i prefer Qt and dislike android and java sdk some others prefer webos some even gtk. so saying dalvik would save meego lis just full of garbage! My n900 still is better than maany android phones out even if they have 100000 more apps. still searchinf for a replacements that says all! dalvik is not the solusion for everything. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
QtQuick is a mess, IMHO. Having a new syntax QML and mixing it with the another C++ syntax, which itself is known to be messy. That is why Java-fathers took off the syntax-sugars and polymorphism following the KISS principle. Much of the GNOME GUI-tools (for example in Fedora) are done with Python, and it has been a huge advantage to get things done and ready quickly. VMs will only get faster when they develop further. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
What is Dalvik doing that this community cannot !!!.
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Obviously !!!
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
http://en.wikipedia.org/wiki/Android_Market Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Because i am not a Linux programmer i cannot answer my own question but i know only one thing, something is not right here especially when it has been a long time since the last Nokia update 25 Oct 2010 and the progress on the N900 has slowed dramatically since.
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
I am not a programmer so i am not that knowledgeable in the subject. But isn't the thing with QT that it is supposed to be both productive and effective while java is just productive?
Overall the device that uses QT would run better. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
http://mynokiablog.com/2011/02/19/vi...o-on-nokia-n8/ |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
What it comes to programming language, QtJambi/Java can be eventually faster in certain (long living OOP) applications than Qt/C++ due to moving-GC which handles away heap memory fragmentation and keeps cache misses count low also when the OOP application is running long time (CPU-time-wise). Core applications like Desktop, window manager and such could actually eventually benefit if they would be running in VM (Java, Python) with a smart GC, because they have to be running 24/7 for a lifetime of device's whole session and time to time a possibility to heap memory defragmentation could come handy. |
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
|
Re: And where is the people from Nokia who worked on Maemo and Meego?
Quote:
http://www.youtube.com/watch?v=b61f6bAuytw |
All times are GMT. The time now is 06:27. |
vBulletin® Version 3.8.8