(1) Zulip Chat - https://zulip.com/ https://zulip.com/ - seems to be reasonably popular, but more people should know about it I’ve been using it for over 5 yea

(1) Zulip Chat - https://zulip.com/ https://zulip.com/ - seems to be reasonably popular, but more people should know about it I’ve been using it for over 5 years now [1], and it’s as good as ever. It’s way faster than any other chat app I’ve used. It has a good UI and conversation model. It has a simple and functional API that lets me curl threads and write blog posts based on them. (only problem is that I Ctrl-+ in my browser to make the font bigger – I think it’s too dense for most people) (2) re2c regex to state machine compiler - https://re2c.org https://re2c.org A gem from the 90’s, which people have done a great job maintaining and improving (getting Go and Rust target support in the last few years). I started using it in 2016, and used it for a new program a few months ago. I came to the conclusion that it should have been built into C, because C has shitty string processing – and Ken Thompson both invented C AND brought regular languages to computing !! In comparison, treesitter lexers are very low level, fiddly, and error prone. I recently saw dozens of ad hoc fixes to the tree-sitter-bash lexer, which is unsurprising if you look at the structure of the code (manually crawling through backslashes and braces in C). https://github.com/tree-sitter/tree-sitter-bash/blob/master/src/scanner.c#L1120 https://github.com/tree-sitter/tree-sitter-bash/blob/master/... These fixes are definitely appreciated, but I think it indicates a problem with the model itself. (based on https://lobste.rs/s/endspx/software_you_are_thankful_for#c_ynrelc https://lobste.rs/s/endspx/software_you_are_thankful_for#c_y...) [1] https://www.oilshell.org/blog/2018/04/26.html https://www.oilshell.org/blog/2018/04/26.html