J'ai réalisé un #hippopotame en terre cuite et puis je l'ai cui en #céramique et puis j'ai mis des émaux dessus et puis je l'ai cui en cuisson #raku. Le résultat est un mignon petit hippo qui est dans l'eau et dont seule la partie supérieure émerge, tête, dos, petite queue.
TPRF (The Perl and Raku Foundation) is organising a Raku & perl devroom at FOSDEM. Sadly, no booth for Raku & Perl. Still, plenty of interesting stands.
I just submitted a talk to the #Perl and #RakuLang track at #FOSDEM. Deadline for submission is tomorrow (Friday Dec 1st), and it's not too late to share! 😄
For the first day of #AdventOfCode living in UTC+0, I actually have to be up at stupid o'clock anyway. In the interests of speed, which I usually do not care about, given the opportunity I shall start day 1 in #perl in which the thing will take moments. I'll clean it up into #raku because, well, one ought to. I'll then start again in #Julia because that's what I want to learn this time around.
I see a lot of exotic things, or rust, or R. Where's my perl tribesfolk?!
Can we please have an alias 'but' for the 'and' binary operator in programming languages?
if outside and moving_slowly ⇒ if outside but moving_slowly
if online and not connected ⇒ if online but not connected
Such semantics made :perl: #Perl a bliss to write in some cases (if not ⇒ unless), although Perl doesn't have this 'but' alias. Probably #rakuLang can change itself at runtime to add this alias 😅
@mjgardner Luckily I didn't write or publish anything serious in #Perl, let alone something that someone else would review. It was just one of my first programming languages to learn and I really liked these 'unless' and 'until' keywords because I think they make certain cases much more readable. But okay, if that's considered bad practice, oh well 🤷
This thread highlights one of the key differences between the design processes behind #RakuLang and #Perl.
Raku's design all came from the question "What could I build if I could basically start again from scratch? What ideas might I have? How do I build a coherent whole from this blank canvas?"
Perl's ongoing design is all rooted in "What would I use right now in this real code I am writing today? What features would I like to have that I currently do not?"
I'm not trying to say either one is better than the other. Rather, the combination of having them both is great for the overall ecosystem and the users of those languages.
At each small step, Perl goes from a reasonable, practical place, to some new reasonable practical place. Each little step is in itself still useful, and incrementally adds value to something that is already useful.
