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.
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?
May have child nodes in a field by itself, or in a Maybe, or list!
... recursively through the potential tree find all fields that end in "Foo" and get the fields corresponding value (fields ending in "Foo" are always String).
Please reply if you're willing to alpha test, code review, or otherwise check out my first private release of my hypercard-like game engine (#haskell).
I will open source it, but it's very messy, though, I feel like that's just superficial messiness, and the architecture is something I'm kind of proud of.
Yes that's right, I think I can push out a Christmas release tomorrow!
When you use nixpkgs do you neglect the regular cabal setup (like cabal freeze)? Do you not pay much attention to people who aren't using nixpkgs for your project? Or do you try to make it work well without nixpkgs too?
@dillo I tried to sudo apt-get install dillo -- it basically works, Although, when I tried to install the Gopher plugin, I noticed to get this plugin working, dpid should be running or the like. I'm running Debian Sid. For me this is in:
/usr/libexec/dillo/dpid
/usr/libexec/dillo/dpidc
Am I supposed to do something to get plugins working/have dpid running?
I'm just thinking about how if you properly package your software for easy installation especially on a variety of popular operating systems, you're really putting yourself ahead of the herd, I think.
I feel like generating a Debian package for a cabal/Haskell project should just be one or a few commands, yet it generally has been very involving for me, even if I also have a nix flake. Tips?
I think it took me a long time to feel good about my development speed in Haskell because I kept trying to do things "the old way," basically a not very functional programming kind of way. I was very stuck in the mindset (sorry if I butcher these terms) dynamic typing, imperative and procedural programming. I haven't felt like I have made progress overcoming this until this project where I set out to put the architecture in the way of types, first. It was amazing to me how in doing so the rest..
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?"
Thank you @fosstodon for making my favorite space on the web--I find it to be an actually worthwhile social media space filled with many similar minded, helpful, and warm people.
Here's to more free and open source software in 2024!
I come back to a project that was working and find it's hard to get going again (can't even compile fully)
Going back to some years old Haskell projects and quickly learning to consider ease of longevity by using things like "tested with" or whatever and cabal freeze and nix lock. Weird to me that I have to do so must work figuring out which ghc to use and getting it to compile again.