The Hare community is super helpful and inviting to contributors. I got some very thoughtful feedback on my initial BLAKE2s support and I got my v2 patchset out tonight and all tests are green.
The Hare community is super helpful and inviting to contributors. I got some very thoughtful feedback on my initial BLAKE2s support and I got my v2 patchset out tonight and all tests are green.
I finally got around to sending a patch to add more of my recent Hare projects to the main project listing. I've been very behind.
This whole “AI” mess pushed be back to the Hare programming language.
I’ve always had a soft spot in my heart for projects trying to stay simple and maintainable by really small teams. So, Hare and QBE have felt right for me.
But, I’m a professional programmer and wanted to focus on technologies which put food on the table. And I’m not sure such niche projects will help me with feeding my family, so I’ve decided to distance myself from those.
But I was hurt by this decision. I couldn’t help to lurk on the project’s feed from time to time which always triggered urge to reinstall those and…
…just feel good from having them on my computers, as I don’t currently have any real use case for them… So, I always end just writing some toy apps in Hare just for pure enjoyment of using something I like.
But this whole “AI” mess was the breaking point. IMHO currently there is a big problem with codebases becoming too big for typically-sized teams to reasonably maintain. And the proposed solution is to make a stochastic code generator which will bloat line count even faster with much worse quality? It’s a very, very cursed idea…
I prefer to stay with the “simplicity” team, even at the cost of some cool features. So, the urge to reinstall QBE and Hare on my computer became unbearable and I’ve caved in. But I’m not sure for what I can use them.
The patch is out for review https://lists.sr.ht/~sircmpwn/hare-dev/patches/68242
My motive here was needing it for a hare-wireguard module, but that is taking me on a fun journey of Blake2s first and then Noise next.
Pretty straightforward implementation so now to set up all the test vectors for the last bit to verify it's compatible with the spec and reference implementations.
https://github.com/BLAKE2/BLAKE2/blob/master/testvectors/blake2s-kat.txt
Exploring Blake2s support for #HareLang today since it already has Blake2b support officially.