00:01 arkiuat joined 00:05 arkiuat left 00:13 arkiuat joined
tbrowder librasteve_: did the &term<x> work? 00:15
01:05 librasteve_ left 01:12 jgaz left 02:12 hulk joined, kylese left 03:15 hulk left, kylese joined 03:17 Aedil left 03:37 arkiuat left 03:45 disbot1 left, disbot2 joined 03:49 arkiuat joined 03:54 arkiuat left 03:55 arkiuat joined 04:35 Aedil joined 04:39 justache left 04:52 justache joined 04:58 lichtkind__ joined 05:00 lichtkind_ left 05:16 Guest9 joined
Guest9 anyone on help duty? 05:17
05:30 melezhik joined 05:32 Guest9 left 06:16 human_blip left 06:18 human_blip joined 06:34 abraxxa joined 06:51 arkiuat left 07:10 arkiuat joined 07:15 arkiuat left 07:28 arkiuat joined 07:32 arkiuat left 08:01 arkiuat joined 08:06 arkiuat left 08:19 arkiuat joined 08:30 arkiuat left 08:35 Sgeo left
disbot2 <librasteve> Guest9: hi, how can I help? 08:55
08:59 arkiuat joined
disbot2 <librasteve> ab5tract: that worked well - you are a genius! 09:02
<librasteve> OUR::{'&term:<' ~ $const.symbol ~ '>'} := sub { Measure.new("{ $const.value } { $const.defn }") };
09:04 arkiuat left
ab5tract Excellent! 09:05
disbot2 <librasteve> new crag-of-the-day: $schwartzschild-radius = 2 * G * 2e30kg / c**2 09:09
<librasteve> -or- 09:10
<librasteve> $r = 2 * G * ?^<mass of sun in kg> / c**2
09:17 dakkar joined 09:26 arkiuat joined 09:31 arkiuat left 09:37 librasteve_ joined 09:59 arkiuat joined 10:05 arkiuat left 10:27 arkiuat joined 10:33 arkiuat left 11:03 arkiuat joined 11:08 arkiuat left 11:21 arkiuat joined 11:27 arkiuat left 11:46 arkiuat joined 11:51 arkiuat left 12:04 arkiuat joined 12:09 arkiuat left 12:16 melezhik left 12:29 arkiuat joined 12:34 arkiuat left 12:53 librasteve_ left 12:55 arkiuat joined 13:00 arkiuat left 13:04 melezhik joined 13:12 justache left 13:17 arkiuat joined 13:21 justache joined 13:22 arkiuat left 13:48 arkiuat joined 13:55 librasteve_ joined 13:57 arkiuat left 14:13 arkiuat joined 14:18 arkiuat left 14:22 arkiuat joined 16:26 melezhik left 16:36 human_blip left 16:38 human_blip joined 17:06 abraxxa left 17:12 melezhik joined 17:37 arkiuat left 17:38 dakkar left 17:49 arkiuat joined
patrickb I'm currently reworking azawawi's File::HomeDir. But I'm changing about everything. It'll basically be a clone of Python's platformdirs. 19:13
Should I:
- Fork and release under a new name.
- Ask azawawi if I can take the module over. 19:14
- Or... ?
lizmat will the API change ? 19:22
patrickb Yes 19:24
lizmat then I suggest another module name... maybe Python::Platformdirs ? 19:25
indicating the influence ?
patrickb It's incompatible, has different features and methods are called differently. The one reason I see to not fork, is that I don't think we need two modules that do the same thing. Especially when File::HomeDirs is for a large part NYI. 19:27
I wouldn't put Python in the name. That module is a good blueprint, but it'll confuse the heck out of people because it has nothing to do with Python at all. 19:28
19:31 abraxxa-home joined
lizmat Platform::Directory ? 19:31
patrickb You still favor a fork. Ok. 19:32
lizmat well, I got the impression from you you basically started from scratch ?
patrickb Or just keep the name: PlatformDirs
lizmat sure 19:33
patrickb True. Still I wonder wether everyone might be better off when we don't have two modules doing essentially the same thing, one pretty rudimentary and no easy way to know that the other one also exists. 19:34
19:35 abraxxa-home left 19:36 abraxxa-home joined
timo one of the modules could become a thin wrapper around the other maybe 19:37
to make a drop-in replacement with some added functionality or bug fixes or so
patrickb Or put a big "just use that other module" banner at the top of the readme 19:38
But then I could just as well adopt that module...
Aww. I can't make up my mind. 19:39
timo one of the difficult problems in programming; i claim this is one kind of "naming things" 19:42
also probably cache invalidation 19:44
19:44 coleman left 19:45 coleman joined
avuserow speaking of adopting modules, I want to adopt Crypt::Argon2. how does it work to release it under the raku-community-modules org? 20:03
patrickb (In case anyone wonders - Yes, that dirs module is still preparation for that debugger thingy of mine.) 20:07
avuserow ideally I would like it if others could release/review if I get busy, otherwise I can own this module myself
patrickb avuserow I guess the first and most important step is trying to contact the original author and communicating your plans. 20:08
I think it can feel pretty bad if your get stripped from you without even being asked. 20:09
*your modules
avuserow yes, I will explicitly do that. (I've been asking for a PR review since ~May and nothing)
20:13 abraxxa-home left
patrickb 👍🏼 20:15
Voldenet multiple modules doing the same thing is okay, but it can lead to rust-like situation where you have N libs for basic stuff 20:32
and then when installing 1 library you end up installing them all because of transitive dependencies 20:33
[Coke] (also, I would say it's better to do a person to person hand off instead of putting something in community modules) 21:29
while there can be more than one way... too many is too many. 21:30
patrickb Homebrew users out there can one of you paste the path of the homebrew Rakudo executable please? 21:52
21:58 itaipu left 22:01 melezhik left 22:06 arkiuat left
[Coke] /opt/homebrew/bin/raku ? 22:07
(I just installed it and was surprised to find it was the one I just cut)
let me know if you need anything else before I uninstall it.
22:09 arkiuat joined
patrickb that's perfect. Thanks! 22:10
no wait
can you paste the output of 22:13
raku -e 'use nqp; say nqp::gethllsym(\"default\", \"SysConfig\").rakudo-home()'
22:15 itaipu joined
[Coke] /opt/homebrew/Cellar/rakudo/2025.11/share/perl6 22:17
changing \" to " 22:18
22:43 human_blip left 22:45 human_blip joined
patrickb That's perfect. Thanks! You can uninstall now. 22:45
[Coke] wonders why homebrew is using tcl-tk 23:27
(to install rakudO)
23:34 Sgeo joined