XPost: comp.os.linux.advocacy
From: znu@fake.invalid
In article ,
JEDIDIAH wrote:
> On 2010-11-18, ZnU wrote:
> > In article ,
> > Lawrence D'Oliveiro wrote:
> >
> >> In message , ZnU wrote:
> >>
> >> > The problem can be nearly as bad if you happen to be using OSS software
> >> > that gets abandoned, which is not exactly unheard of for less mainstream
> >> > projects.
> >>
> >> Never heard of an open-source project dying and leaving users’ data
locked
> >> up in a proprietary format. Cite?
> >
> > The format doesn't have to technically be proprietary; it's sufficient
>
> That still doesn't alter the fact that you haven't done so much as to
> offer a single solitary example to demonstrate this point.
Several examples have been offered of apps for which this would be an
issue.
> Just the concept has problems. It's the sort of thing that would tend
> to increase work. For a free software project built by hobbyists and
> volunteers, that really doesn't make sense. There is no benefit to obscuring
> the user's data or making it hard to migrate away.
>
> Preventing an escape path is too much work.
Huh? We're not talking about deliberate efforts to obscure data here.
We're just talking about apps that implement their own file formats,
rather than already widely supported file formats like, say, JPEG or RTF
or whatever. This is done all the time for perfectly good reasons, such
as the fact that such widely supported formats simply don't exist in
many market segments.
--
"The game of professional investment is intolerably boring and over-exacting to
anyone who is entirely exempt from the gambling instinct; whilst he who has it
must pay to this propensity the appropriate toll." -- John Maynard Keynes
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
