![]() |
2007-11-17
, 16:48
|
Posts: 29 |
Thanked: 11 times |
Joined on Oct 2007
|
#42
|
Watch out for the scrolling RSS, it's a CPU hog. Try doing something like playing songs in Rhapsody while the scrolling RSS is enabled and you will see what I mean.
![]() |
2007-11-17
, 16:48
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#43
|
![]() |
2007-11-19
, 02:08
|
Posts: 81 |
Thanked: 3 times |
Joined on Jul 2007
|
#44
|
![]() |
2007-11-19
, 03:02
|
|
Posts: 574 |
Thanked: 166 times |
Joined on Oct 2007
@ BC, Canada
|
#46
|
For those of us who are either thinking about installing 08 or have decided to wait for the official release, how about a few screen shots so we can see what it looks like?
![]() |
2007-11-19
, 03:04
|
Posts: 81 |
Thanked: 3 times |
Joined on Jul 2007
|
#47
|
![]() |
2007-11-19
, 03:17
|
Posts: 81 |
Thanked: 3 times |
Joined on Jul 2007
|
#48
|
Reggie posted a 16 minute video walkthrough.
http://www.internettablettalk.com/fo...5094#post95094
![]() |
2007-11-19
, 03:24
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#49
|
I'm sorry, this doesn't wash. It's great that they've introduced new APIs, even better that upstream GTK etc is being tracked now. However, this shouldn't have come at the expense of the old APIs. When MS, Apple or even Debian/other Linux distros upgrade to new libraries, they keep old ones around as well so that everything doesn't break. I typically have wxGTK libraries of about three or four versions on my systems for different apps that haven't been brought up to current.
I realize that there are extra constraints with this being an embedded platform. I also think it's acceptable to have this sort of breakage for brand-new platforms in brand-new categories. However, as the platform matures, as is surely the case with ITOS 2008, this sort of behaviour becomes less and less tolerable. I hope this is the last time that Nokia intentionally breaks compatibility. Otherwise, I fear they risk alienating 3rd party developers for the platform. Just look at all of the OSS apps that only work on specific versions of ITOS for examples of this already. Jpilot and Abiword to name two. What did this buy us? Lost apps and lost developers.
Apple, Sun, Microsoft, Red Hat, Canonical, all of them keep old versions of libraries around to prevent just this sort of thing from happening. Sure, deprecate old APIs/libraries, but at least keep them around for a release or two. Can you imagine how popular Java would be if each new release of the JDK broke _ALL_ non-trivial apps compiled against the previous version?
![]() |
2007-11-19
, 04:21
|
|
Posts: 273 |
Thanked: 15 times |
Joined on Oct 2007
|
#50
|
I realize that there are extra constraints with this being an embedded platform. I also think it's acceptable to have this sort of breakage for brand-new platforms in brand-new categories. However, as the platform matures, as is surely the case with ITOS 2008, this sort of behaviour becomes less and less tolerable. I hope this is the last time that Nokia intentionally breaks compatibility. Otherwise, I fear they risk alienating 3rd party developers for the platform. Just look at all of the OSS apps that only work on specific versions of ITOS for examples of this already. Jpilot and Abiword to name two. What did this buy us? Lost apps and lost developers.
Apple, Sun, Microsoft, Red Hat, Canonical, all of them keep old versions of libraries around to prevent just this sort of thing from happening. Sure, deprecate old APIs/libraries, but at least keep them around for a release or two. Can you imagine how popular Java would be if each new release of the JDK broke _ALL_ non-trivial apps compiled against the previous version?