I am yet again starting a project in #haskell and having fun getting lost in something fun, but basically causing me to be side-tracked.
I'm working on a simple pixel art editor, but I am excited by #LiquidHaskell to, I think, use refinement types and prove certain properties about my code.
After much failure with trying to get my #haskell#sdl2 project running with #nix, I find the workaround is to use an environmental variable to set SDL_RENDER_DRIVER=software and skip using drivers entirely, I guess?
I think I'm willing to pay a #gopher enthusiast in #monero to try out running my forum server software (and other Gopher Protocol software I made) as well as using my server for at least a week and blogging/tooting about it.
I don't think left vs. right associativity in Haskell is entirely intuitive/consistent, though I may be over-thinking it.
Getting back into writing #haskell and I made the mistake of thinking something like (x !! y !! z) would be evaluated like ( x !! (y !! z) ), probably due to function composition.
Is there any future in languages like #haskell where AI makes code a factor of small frequently and easily replaced glue and scraps, where whatever is most trained on and most hackable, most easily replaced/iterable is king?
Are big pieces of software that benefit from the architectural assurances Haskell brings a dead paradigm?
AI is here to stay and I feel if something was not already in or out of orbit, it may never reach escape velocity
I installed #gnome to hunker down and "get stuff done" as I was before using #windowmaker, but now that I'm using gnome, some things work nicer and easier, but overall I think I may go back to #windowmaker.
I feel for Haskell to survive it needs to be as easy to put together and get running and distributing as Python and Golang is.
I feel like sometimes the idea of starting a new Haskell project is so burdensome, and there's no real "official" way of doing certain things that actually works consistently (like static binaries) that I sometimes just decide a project's not worth it.
We're also in the age of AI now where it's like everything is reduced to glue.
There's maybe too much focus on elegant and good code, systems that support better correctness, when in reality what works best are systems that have an okay degree of correctness assurance and mainly prioritize iteration and prototyping.
Does Haskell lose this battle?
You shouldnt be attached to code. You should feel able to delete and reiterate without too much hesitation. Does Haskell encourage too much "correctness scaffolding?"