From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with beta from 2019.11.29 21:47 in Windows
Date: Sun, 8 Dec 2019 00:33:10 +0100 [thread overview]
Message-ID: <9836944b-6310-085e-260c-0498f152e509@xs4all.nl> (raw)
In-Reply-To: <82a9078c-b9db-d10e-00a3-a90285e46ff4@gmx.es>
On 12/7/2019 11:49 PM, Pablo Rodriguez wrote:
> free software may be a good contribution to society, but it is no moral
> problem at all. (Probably we should start questioning why we apply
> copyright law to trade secrets.)
What always puzzles me is that companies that otherwise depend on open
source have no problems with quite rigourous copyright claims, even go
for lawsuits, and don't care about violating privacy. And I also have
not much sympathy for companies that start using free software, boast
about it, kind of use the community and then cash out, quit support, put
the usefull stuff in expensive variants only and in the end leave users
in the cold. I have no problem with commercial activities but they
should be open and can not be hidden.
Btw, it's one reason why open source / free sw can fail in cases:
support can be more expensive than for commercial stuff, although often
tex is dirt cheap, if only because much can be achieved with little
coding and once it works, it works forever. One problem in your case is
that managers probably don't make a proper cost-benefit analysis. Maybe
we should make some templates for that some day.
I wonder how much backslash - pun intended - there is because of all
that pseudo open source. Makes a nice topic for late-night discussions
at a next ctx meeting.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-12-07 23:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 15:18 Pablo Rodriguez
2019-12-02 17:01 ` Wolfgang Schuster
2019-12-02 17:46 ` Pablo Rodriguez
2019-12-02 20:45 ` Wolfgang Schuster
2019-12-03 19:37 ` Pablo Rodriguez
2019-12-03 21:14 ` Hans Hagen
2019-12-04 21:19 ` Pablo Rodriguez
2019-12-05 8:23 ` Hans Hagen
2019-12-05 19:31 ` Pablo Rodriguez
2019-12-06 9:01 ` Arthur Reutenauer
2019-12-07 13:40 ` Pablo Rodriguez
2019-12-07 15:32 ` Hans Hagen
2019-12-07 22:49 ` Pablo Rodriguez
2019-12-07 23:33 ` Hans Hagen [this message]
2019-12-04 21:27 ` Pablo Rodriguez
2019-12-02 17:05 ` Hans Hagen
2019-12-02 17:51 ` Pablo Rodriguez
2019-12-02 22:22 ` Hans Hagen
[not found] <7992CF71224042639D33FC342999C075@CJ3001517A>
2019-12-03 8:17 ` Hans Hagen
2019-12-03 19:45 ` Pablo Rodriguez
2019-12-03 21:11 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9836944b-6310-085e-260c-0498f152e509@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).