Linked by Thom Holwerda on Wed 24th Jun 2009 12:24 UTC, submitted by ralsina
Permalink for comment 370462
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2008-04-29
Well, I'm open to the idea that I might make mistakes
Yes, but that doesn't mean that the whole idea comes crashing down. 0install already has a good framework for dealing with this -- it ties in with the native package manager to determine whether or not an adequate library for the given application is already installed. I'm worried you're letting implementation details get in the way of design ideas. It may be years and years before a good system emerges, but that doesn't mean it's impossible; it means we need a clear idea of where we're going.
Mmm; I think what users really want is "see application; use application". They don't really care about the "having / installing" bit. That, I think, is where package managers slip up.
Mmm, again -- I don't think users want to think about repositories. It's a very developer-centric idea.