I just lost three hours on stream, debugging an apparently incorrect path finding algorithm... Only to realize after all that time that the problem was a HASHMAP COLLISION, OF ALL THINGS! I am... mad :D
EDIT: can't reproduce it while attempting to hash all possible values to find the collision, so there must be something else at play. I wonder what could explain why switching the map type fixes my code... i'll investigate when i have slept.
We're not yet halfway through November, but it's time to get ready for one of my favourite events of the year: the Advent of Code!
like every year i'll be doing it live in Haskell on twitch, every weekday at 8PM UTC starting tomorrow! as usual i'll try to keep the code as approachable as the problems allow, to keep the stream beginner-friendly.
see you there!
This is a draft of a blog post I'm aiming to publish soon criticizing the NeoHaskell project. Feedback welcome.
Post below the fold ⬇️
This is a very clear analysis of the problems with NeoHaskell. I come from a similar place of being interested in how to increase Haskell's popularity, how to market it, how to dispel the myths around it, and more importantly how to teach it (check my pinned post ^^), and as a result i do share some of the concerns that Gabby highlights here. Specifically, i think that in promising to make Haskell more "beginner friendly" by altering elements of the language itself, NeoHaskell is promising something it cannot deliver.
I've been meaning to write this down for a long while, but i've made it a youtube essay instead, as an experiment, to learn something new; so: what the hell is the problem with monads?
