Ouch . . .

I don't know why this has to degenerate into a sort of flame war about whether one has to pay for things
or not.

[Within the next few weeks I will have to pay LiveCode to relicence my Indy version of LiveCode - I am well aware of why I am going to do this; and, which is probably the most important point, I don't resent that.]

If I had to pay something for Python I would: NOT because I like Python; because, frankly I don't [ why go backwards to the sort of programming language I last had to work with in 1986? ], but because I shall be making money out of teaching Python.

"silly licensing"

My Devawriter Pro and my Balawriter both feature "silly licensing" because, odd as it may seem, I did not make those
programs for the love of it.

I started this, not to let it wander off onto pay/free or whatever, but to ask advice re setting up Python on Linux boxes
in my school

Richmond.

On 13/8/2018 6:57 pm, Mark Waddingham via use-livecode wrote:
On 2018-08-13 17:34, Mark Wieder via use-livecode wrote:
On 08/13/2018 02:21 AM, Peter W A Wood via use-livecode wrote:

Like it or not (and mainly NOT), I have to offer Python to kids this fall . . .

Frankly, Python, by using this module system seems to defeat itself to a certain extent: or, maybe I'm just
spoilt by LiveCode.

We all are <g>. But python has the best scientific libraries around
(www.scipy.org). And everything python is free and open source - no
silly licensing to worry about.

Last time I checked you sold at least two products which required a license...

If you think licensing is silly, then why do you sell licensed software and not just give it away for free and open source as 'public domain'? :P

Warmest Regards,

Mark.


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to