[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proprietary Software term
From: |
Urs Liska |
Subject: |
Re: Proprietary Software term |
Date: |
Sat, 18 Aug 2018 12:38:46 +0200 |
User-agent: |
K-9 Mail for Android |
Am 18. August 2018 12:25:25 MESZ schrieb Trevor <address@hidden>:
>
>locked-in?
Strike!
"Vendor lock in" was it what I was looking for.
Thanks
Urs
>
>------ Original Message ------
>From: "Urs Liska" <address@hidden>
>To: "lilypond-user" <address@hidden>
>Sent: 18/08/2018 10:53:32
>Subject: Proprietary Software term
>
>>Hi,
>>
>>I'm pulling my hair because I don't manage to find a certain term to
>>use in an abstract.
>>
>>We've talked about the issue over and over again, but how do we call
>it
>>when using proprietary software prevents us from changing the tools to
>
>>work with our data/documents? (Well, actually the same effect that
>>prevents us to edit LilyPond scores with other programs, although
>>that's not for license but only for practical reasons).
>>
>>Urs
- Proprietary Software term, Urs Liska, 2018/08/18
- Re: Proprietary Software term, Trevor, 2018/08/18
- Re: Proprietary Software term,
Urs Liska <=
- Re: Proprietary Software term, Andrew Bernard, 2018/08/18
- Re: Proprietary Software term, David Kastrup, 2018/08/18
- Re: Proprietary Software term, Urs Liska, 2018/08/18
- Re: Proprietary Software term, David Kastrup, 2018/08/18
- Re: Proprietary Software term, Wols Lists, 2018/08/18
- Re: Proprietary Software term, David Wright, 2018/08/18
- Re: Proprietary Software term, David Kastrup, 2018/08/18
- Re: Proprietary Software term, Wols Lists, 2018/08/18
- Re: Proprietary Software term, David Kastrup, 2018/08/18
- Re: Proprietary Software term, Wols Lists, 2018/08/18