ChanServ changed the topic of #picolisp to: PicoLisp language | Channel Log: https://irclog.whitequark.org/picolisp/ | Check also http://www.picolisp.com for more information
orivej has joined #picolisp
orivej has quit [Ping timeout: 272 seconds]
Unscrmbl-aw has joined #picolisp
orivej has joined #picolisp
<Regenaxer> Hmm, libedit's API is different
Blukunfando has quit [Ping timeout: 265 seconds]
<Regenaxer> Grr, it doesn't even use .inputrc
<Regenaxer> I *hate* this license mess
<Regenaxer> The main reason for me to use readline() was to stay COMPATIBLE with the rest of the world
<Regenaxer> ONE config
<Regenaxer> I could have stayed with my self-rolled line editor @lib/led.l as well then :(
<Regenaxer> Or go back to GPL?
orivej has quit [Ping timeout: 260 seconds]
<wineroots> You may get good publicity with GPL. But, GPL will mean legally being bound to publish(any pil21 modifiers) modifications if someone chooses to do so. Choose your pick. Does it matter in the long end of things? Would GPL create any relevant issues later?
<Regenaxer> Not for me
<Regenaxer> Several people complained, so I switched to MIT
<Regenaxer> aw was one of them iirc
<Regenaxer> also some guys in India
<Regenaxer> I personally don't care
<Regenaxer> What if I release completely *without* any licence? Everybody
<Regenaxer> can pick what she likes
<Regenaxer> indeed
<Regenaxer> Why not distribute the sources without? It is just text
<Regenaxer> I'm fed up
<wineroots> GNUreadline will make it hard. GNU demands enforcement of copyright or the 4 freedoms as defined. Readline could make it an issue(if someone discovers) sometime in the future
<Regenaxer> yes, that's how I understood it
<wineroots> Maybe post in the mailing list for wider opinion. Things could've changed or it's not an issue any longer, or perhaps it still is an issue to majority of people?
<Regenaxer> Did already
<wineroots> Good
<Regenaxer> I'm really thinking of *no* licence at all
<Regenaxer> Anybody pick what she likes
<Regenaxer> It is an US-legal-system mess
<wineroots> Yes, indeed.
<Regenaxer> Here in Germany I care only about Copyright (Urheberrecht), which is not touched by such licences
<wineroots> Oh, cool
<Regenaxer> ☺
<wineroots> I checked even puthon & ruby use readline. This should not be an issue if they are used by major and minor corps worldwide. Unless, someone's aiming for a closed source fork let's say FutureLisp54
<wineroots> *python
<Regenaxer> I thought I saw that python uses libedit (editline)?
<Regenaxer> Hmm, just tried. python obeys my ~/.inputrc, so it seems to be readline
Unscrmbl-aw has quit [Ping timeout: 260 seconds]
<Regenaxer> Mike Pechkin just told me in a private DeltaChat that MIT allows any other licence, so it is no problem anyway
<Regenaxer> Just keep it as it is?
Unscrmbl-aw has joined #picolisp
<wineroots> Checking
<wineroots> According to gnu it should be compatible. http://directory.fsf.org/wiki/License:X11
<wineroots> MIT is x11 right?
<wineroots> Even software engineering SO has amswers saying so
<Regenaxer> Yeah
<Regenaxer> Just some people may not like it
<Regenaxer> cause they need *their* programs be GPL then
<wineroots> Picolisp code?
<wineroots> (de f ()(print "me gpl?"))
<wineroots> There would only be an issue if they were to remove readline and try to do things with without it. But, that's unlikely. This restriction is so a free software program does not become closed source in the future.
<Regenaxer> ok
<Regenaxer> so let's see if anyone complains in the ML again ;)
<wineroots> Sure! :D
orivej has joined #picolisp
<Regenaxer> OK, so it does not look like a problem :)
TeddyDD has joined #picolisp
<Unscrmbl-aw> hello
<Unscrmbl-aw> for the record, picolisp was already MIT before i learned about picolisp
<Regenaxer> Hi Unscrmbl-aw
<Regenaxer> Ah, sorry! So it was someone else
Unscrmbl-aw is now known as aw-
<aw-> what happened?
<Regenaxer> Nothing so far
<aw-> what's the issue with readline?
<Regenaxer> Ah
<Regenaxer> All in the log here and in the mailing list
<aw-> ohh readline is GPL
<aw-> i see
<Regenaxer> yeah
<Regenaxer> But perhaps no problem as I see now
<aw-> yeah
<aw-> it's not a problem
<aw-> MIT is compatible with GPL
<Regenaxer> Very good
<aw-> you're not distributing readline are you?
<Regenaxer> correct
<aw-> ok, no problem
<Regenaxer> Thanks for clarification
<aw-> the notice on their website makes it seem as though "if you code against libreadline, your software must be GPL"
<aw-> but that is completely incorrect
<Regenaxer> hmm, yes, disturbing
<aw-> tbh though, readline is kinda shit
<aw-> what was wrong with the old approach?
<Regenaxer> lib/led.l was quite outdated
<Regenaxer> no direct support for emacs-mode
<Regenaxer> no support for .inputrc
<Regenaxer> People did not understand it
<Regenaxer> Everyone is used to readline
<aw-> but readline is garbage, building on top of garbage isn't usually a good idea
<aw-> i liked the old line editor
<aw-> worked perfectly for me
<Regenaxer> What is garbage in readline?
<Regenaxer> Works well
<aw-> big, bloated, gpl
<Regenaxer> hmm, is it so big?
<Regenaxer> here on Termux 344K
<Regenaxer> dynamically linked
<aw-> ok maybe not so bad
<aw-> anyways, linking to it during the build process is fine, so no license worries
<Regenaxer> Perfect
Blukunfando has joined #picolisp
ym has joined #picolisp
<DKordic> Welcome ym.
<DKordic> Re: readline; Patches welcomed.
<aw-> haha yeah right
aw- has quit [Quit: Leaving.]
<beneroth> "patches welcomed" is the same as saying "we're not sure if our software doesn't suck" no?
<ym> Maybe in commercial area, but not in open source freeware, IMO.
<beneroth> commercial software often sucks on purpose.
ym has quit [Quit: Leaving]