shpx has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
shpx has joined #picolisp
orivej_ has quit [Ping timeout: 264 seconds]
dtornabene has joined #picolisp
dtornabene has quit [Quit: Leaving]
dtornabene has joined #picolisp
orivej has joined #picolisp
_whitelogger has joined #picolisp
dtornabene has quit [Remote host closed the connection]
alexshendi has quit [Ping timeout: 264 seconds]
shpx has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alexshendi has joined #picolisp
trui has joined #picolisp
<trui>
hellos
<beneroth>
hi trui
<Regenaxer>
Hi trui, beneroth
<beneroth>
hey Regenaxer :)
<Regenaxer>
beneroth, you said you want to write a package manager
<Regenaxer>
What would it be good for?
<Regenaxer>
(I got a question in Mastodon about this)
<beneroth>
modularizing software. deployment and dependence management. independently update/downgrade parts of a software. I explicitly want also have functionality to do things like "is there a database entity which has x/y?" as a dependency for a module.
<beneroth>
apparently the term "package manager" sometimes means a bit different things. some separate dependency management or environment/install management from it.
<Regenaxer>
ok
<beneroth>
does this answer your question? what was the question you got?
<Regenaxer>
I see no need actually. All libs are single-file, very short, and not depending on lots of other things
<Regenaxer>
The question was "Anyone knows if there's something like a packagea manager for libraries in #picolisp land? I looked verify but have seen one"
<beneroth>
T. when the "packages" are so simple and you have a very conscious dev/admin, its not really needed.
<beneroth>
ok, then the answer is there is none. and your viewpoint is that none is needed.
<Regenaxer>
He just read about pil today in a note I posted about 'tasks'
<Regenaxer>
That's only my viewpoint
<Regenaxer>
ok, thanks
<beneroth>
I see package manager as automation of manual tasks. I personal intention is to have a easy way to track what I have installed where in which version, and to automatically copy and install code pieces on multiple machines
<Regenaxer>
I simply wrote there is none :)
<Regenaxer>
ok, makes sense
<beneroth>
in pilBox, this single-app-zips are a kind of packages, no? :)
<Regenaxer>
yeah
<Regenaxer>
I really like Mastodon, ie. the "Fediverse"
<Regenaxer>
Feels much more *right* than twitter
<Regenaxer>
Just the clients are not satisfactory I think
<Regenaxer>
Settled for Mastalab at the moment
<Regenaxer>
The Web GUI jumps unpredictable when new toots arrive, I think this is unusable
<Regenaxer>
Same for Tusky and Tootdon
<beneroth>
Yeah I read your previous complains about it. sounds awful.
<Regenaxer>
But I hope this will improve
<Regenaxer>
yeah
<Regenaxer>
Strange
<beneroth>
you will write a pil client eventually, I'm sure ^^
<Regenaxer>
nobody else complains, perhaps my usage is wrong
<Regenaxer>
yep :)
<Regenaxer>
Too lazy though ;)
<beneroth>
I know the feeling ;)
<Regenaxer>
:))
<Regenaxer>
BTW, I should announce 'tasks' here too
<Regenaxer>
a very cool new function in @lib.l
<beneroth>
oh?
<beneroth>
than I missed it
<Regenaxer>
Allows a dynamically changing 'task'
<beneroth>
something else than task then?
<beneroth>
oh
<Regenaxer>
No, I did not announce it here
<beneroth>
that sounds interesting for me
<Regenaxer>
only twitter and mastodon
<beneroth>
yeah now I feel the social pressure :P
<Regenaxer>
yes, I needed it for the PilBox communication
<Regenaxer>
hehe :)
<beneroth>
yeah sounds great for background stuff
<Regenaxer>
I needed to connect the server in the background, *then* sleep in the bg
<Regenaxer>
in a loop
<Regenaxer>
'tasks' lets you change the key (timeout or FD) each time
<Regenaxer>
Before, I called 'ssl' in a 'task'
<beneroth>
yeah I'll have uses for such tasks, too
<Regenaxer>
and this in another task for the timeout
<Regenaxer>
The problem is if ssl takes longer than the timer task, you get multiple calls to ssl pending
<beneroth>
aye
<Regenaxer>
With 'tasks' the timer starts when ssl is done
<Regenaxer>
Very cool to use with a coroutine
<Regenaxer>
the co yields the new task key each time
<Regenaxer>
So you can easily program complicated background stuff
<Regenaxer>
All running in the main process, so no locking etc. issues
<beneroth>
nice
<beneroth>
yeah I like to change my http.l from forking to async with worker processes eventually
<Regenaxer>
For speed?
<beneroth>
yep. and better memory caching.
<Regenaxer>
T
<beneroth>
pilDB caching.
<Regenaxer>
Can be done with co and tasks I suppose
<beneroth>
would be nice to figure out which external symbols are more often accessed / to 'gc rarely accessed external symbols when memory is needed.
<beneroth>
T
<Regenaxer>
To avoid blocking, I/O is put into a queue of pending stuff
<beneroth>
nice
<Regenaxer>
Still very complicated. Forking is a lot easier ;)
<beneroth>
T
<beneroth>
and much more stable. and good enough for company apps :)
<Regenaxer>
right
<beneroth>
that's why I started this way and keep this for a while :)
<beneroth>
bbl
<Regenaxer>
cu!
<cess11_>
Great news regarding tasks, will be fun to try it out.