🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). This channel is logged for the purpose of keeping a history about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Log inspection is getting closer to beta. If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 25 August 2021.
Geth ecosystem: f0b5b39d1b | (Elizabeth Mattijsen)++ | META.list
Freeze Web::Template

While we move it to the zef ecosystem
10:05
ecosystem: a797f20e99 | (Elizabeth Mattijsen)++ | META.list
Remove Math::Trig and HexDump::Tiny

They now live in the zef ecosystem
Geth ecosystem: b78478ad1d | (Elizabeth Mattijsen)++ | META.list
Freeze Web::App::MVC

While we move it to the zef ecosystem
10:49
Geth ecosystem: d110116b44 | (Elizabeth Mattijsen)++ | META.list
Freeze Web::App

While we're moving it to the zef ecosystem
11:34
Geth ecosystem: 1d6f7b0485 | (Elizabeth Mattijsen)++ | META.list
Freeze Color

While we move it to the zef ecosystem
11:57
Geth problem-solving: lizmat assigned to codesections Issue Preparing the Raku Ecosystem for the Future github.com/Raku/problem-solving/issues/316
lizmat unassigned from codesections Issue Preparing the Raku Ecosystem for the Future github.com/Raku/problem-solving/issues/316

fa8010e006 | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | solutions/meta/TheRakuFoundation.md Communicating the effective establishment of the Raku foundation (#300)
  * Communicating the effective establishment
The Raku Foundation exists, so this closes #263
  * Addressing @vrurg comments
16:54
[Coke] FSVO soon 18:16
Geth doc: 6af6cb83f9 | (Daniel Sockwell)++ (committed using GitHub Web editor) | xt/aspell.t
Make xt/aspell's output better/less verbose (#4036)

This commit changes xt/aspell's output from a full list of all the suggestions aspell has for a word (frequently many lines of terminal output) and into a formatted list of misspelled words.
19:18
Geth ¦ problem-solving: vrurg assigned to codesections Issue Uniform approach to distributing important messages within Raku community github.com/Raku/problem-solving/issues/317 21:24
Xliff Where does Bisectable keep it's builds? 22:12
MasterDuke shareable6: 2022.01 22:17
shareable6 MasterDuke, whateverable.6lang.org/2022.01
MasterDuke Xliff: ^^^ there
Nemokosch I tend to mess up the diplomatics so this time I will just ask, please don't think that what I'm saying is meant in a bad way, more just random feedback 22:21
so I was reading up on a problem solving issue (<github.com/Raku/problem-solving/issues/290>) and I bumped into an interesting statement 22:22
_We optimize for readers of the code before we optimize for the writers of code._
And I was like... "Really? 🤔 " 22:23
It absolutely doesn't feel like that to me
And honestly I even found it a nice trait of Raku that it's insanely prototyping-friendly and you can kind of "vent" with your code 22:27
MasterDuke well, i say that's true compared to Perl, but maybe less so compared to (some/many/) other languages 22:29
e.g., Raku regexes are more verbose than Perl regexes 22:30
Nemokosch yes, regexes are pretty reader-friendly compared to most regex syntaxes (perhaps all I have seen) 22:38
but "magic variables" (I don't know if this is the right term, I mean $_ and $/ in particular) for example are rather tricky for someone not used to the Perl family 22:42
again, that doesn't mean they are bad, the topic variable is a bit like good old Pascal `with` for me, it removes unnecessary repetition of a term
for me it feels they are more for refactoring than easy readability 22:44
MasterDuke i wasn't around during the early parts of the language creation, but i wonder if timtoady has a slightly different sense of read the code than one might usually think. i.e., he's talked about being inspired by natural language constructs (e.g., postfix `if`, `unless`), maybe he is/was thinking of reading in a more general sense of understanding 23:00
what's going on than knowing exactly how everything you read is implemented
so one might look at `$/<good-name-here>` and not know exactly *how* the contents of `$/` are populated, but if that name is in fact descriptive, you have a good guess at what's going on. compared to a fictitious example `match_result.named_matches.get('good-name-here')`, there's just a lot more stuff obscuring what you actually care about 23:06
but this is all just speculation on my part
japhb The list of magic variables is actually *much* reduced from Perl. And that was intentional. 23:59