And, since we’ll be sharing our code, keeping it concise will help others see our logic without being distracted by housekeeping details. It’s annoying but bearable to deal with many lines of boilerplate when setting up a large project, but it’d be far worse to do so repeatedly on each day of AoC. This suggests that the ideal language would be concise and low-boilerplate.
LARGE ADVENT SPEAKER CODE SERIES
When thinking about the ideal AoC language, the first feature of AoC that comes to mind is that it’s a series of small, largely self-contained puzzles rather than one large project. Then I’ll present a Raku solution to last year’s first AoC challenge and compare it to our ideal. To explain why, I’ll walk through what we’d want out of an ideal AoC language.
LARGE ADVENT SPEAKER CODE CODE
I believe that Raku is a good fit for solving many different problems, but it’s definitely an excellent fit for Advent of Code challenges. Why is Raku a great fit for solving AoC challenges? If those ideas are even half as good as I believe them to be, then Raku is a language you’ll want in your toolbelt.
LARGE ADVENT SPEAKER CODE FULL
But, even setting those big-picture ideas aside, Raku is a language that’s full of interesting ideas. In fact, Raku has a rare, laser-like focus on individual productivity and is willing to trade off some standard enterprise/large group features to achieve that goal, as I’ve previously discussed at length ( part 1, part 2, part 3). That’s not to say that Raku is a language that tries to be all things to all people. But even in that relatively rare case, I’d probably write the performance-critical sections of my code in Rust and the rest in Raku, taking advantage of how well the two languages play together.) (The one exception is if solving my problem demands the raw speed or low resource use of a compiled language. When faced with pretty much any problem, I keep concluding that Raku is the language that will let me solve it in the clearest, fastest, and most elegant way possible. What this means in practice is that I find myself reaching for Raku increasingly often. Raku A concise, expressive, aggressively multiparadigm language with strongly inferred types, built-in concurrency, rich metaprogramming, and best-in-class string processing and pattern matching. Raku is notoriously hard to pin down in a single sentence, but here’s my attempt: Since Raku is a relatively new programming language, at least some of you may not be familiar with it or why it’s worth learning. This post will explain how Raku and AoC are such a good fit and then provide some resources to help us all get started solving AoC challenges. If your only goal is to solve AoC challenges, Raku is a great language to use on the other hand, if your only goal is to learn Raku, then solving AoC challenges is a great way to do so. (In this post, I’ll be referring to Advent of Code as “AoC” – not to be confused with the American politician AOC who, to the best of my knowledge, does not program in Raku.)įor me, Raku and AoC are the chocolate and peanut butter of tech Advent season: each is great on its own, but they’re even better in combination. Specifically, the Raku Advent Calendar releases a new blog post about the Raku programming language, while Advent of Code releases a new programming challenge – which can be solved in any language. These two holiday traditions have a fair amount in common – they both run from December 1 through Christmas, and both involve releasing something new every day during the event.
![large advent speaker code large advent speaker code](https://i.ebayimg.com/thumbs/images/g/4cMAAOSw9QlhkZ3E/s-l300.jpg)
Now that it’s December, it’s time for two of my favorite traditions from the tech world: the Raku Advent Calendar and Advent of Code.