Re: Tizen?
 

Heres another one...Meltemi...take it away

Re: Tizen?
 

Maybe Nokia should change Harmattan back to Maemo 6...

Re: Tizen?
 

actually not. Windows 95 had bookmarks also. With N9 your only way to get a bookmark is to add it to application selector as an icon that looks just like it would be any application.


is this the best straw man you can come up with?



and as I have been saying: I am talking about 99% of "apps" that can be found in "app stores", not the marginal ones you are referring to.

Re: Tizen?
 

It doesn't matter - for modern store-style repository setups they are both utterly inefficient and bloated. Linux on mobile should use neither (they are great for integration purposes - which was the original reason they came into existance, but not for setting up/searching/manipulating a working body of millions of applications/content).

Re: Tizen?
 

As I already quoted from Wikipedia:
Programs written in Visual Basic can also use the Windows API, but doing so requires external function declarations.

And both VS, Delphi, Java IDEs and Qt use graphical components, none of which are standard for Windows, but in addition to the Windows guidelines. So you're completely off base - hardly anything you see in Windows has a standard Windows GUI. It has a standard VS or Delphi or Java or Qt GUI.


Hogwash. When it comes to Windows, I have PCs running with the same desktop resolution as on my last two cell phones. This is all supported in the IDEs. And you can easily run a Linux system on 32GB harddrive; when I put together my last machine it ran Windows 7 a full year with only 64GB SSD. The N900 is a computer - why on earth put in limitations to prevent it from being one?

Re: Tizen?
 

You are confusing the packaging format/tool (.rpm/.deb, rpm/dpkg) with the repository management/update tools (yum/zypper/apt). "Millions" might be a bit of an exaggeration as well ;-)

Re: Tizen?
 

Well there still could be an option to do for example searches on packages on server side. rpm client and server protocol could be optionally more richer to transfer work load from mobile devices to the server. (On the other hand, I do not like to do many operations or calculations on any cloud, because privacy issues.)

But what it comes to apt vs rpm, rpm is technically, security wise and politically better choice. I haven't heard or read any other good reasons for Debian and Ubuntu to stay on deb, but legacy, stubbornness and laziness issues.

Re: Tizen?
 

No, I mean both the package file formats *and* repository management as something that comes from the desktop background and solve the problems desktop linux distros had. With the desktop, you had interdependent software packages with unrelated development cycles and universal distribution models - hence the need for dependencies and public repositories. Modern mobile is a different story. The packages are not equal, there is no interdependency on the application side, there is no need for package dependencies (a mobile linux implements an API version, which is nowadays mandated to be backwards compatible), there is a need for per-user custom repositories, or even packages, package metadata is not only a system-related thing but actually plays part in the user interaction, etc, etc, etc. It really is a whole different ballgame. Don't get me wrong, I *love* apt-get and debs, and have grown to like rpm to an extent and would never switch from them for my desktop linux distro, but on mobile, their main advantage is familiarity, at the (increasing cost of) inefficiency and being unfit for the task.

EDIT: And as for millions - with people increasingly having this crazy idea of having bookmarks/rss feeds published as 'applications', we're going to be lucky if it's just a few millions :)

This is what pretty much every first-gen mobile linux is doing - rehashing desktop formats and technologies and tweaking them to death (maemo -> deb, android -> jar, meego -> rpm, webos -> ipkg). What all of these came to learn is that those are hacks. Hacks that we might be fond of for historical reasons, but still hacks :)

Re: Tizen?
 

per-user custom repositories are supported with rpm, and relatively safe way too. Trusting or not gpg-keyservers is then another thing.

I cannot see how you get around software library and and other soft resource dependencies, if package manager is not aware of them somehow. Some people do not need or want some software libraryC, but some applicationA and applicationB needs it. It is unefficient if C comes within inside A and B both or if C would be installed on the all systems although many would not want to have apps A and B.

Re: Tizen?
 

especially true if every single Qt application you make need to package Qt with it :/
But it hopefully won't be the case.