Getting basic language infrastructure going is surprisingly labour intensive.
I've built a toy language up to hello world -- lexing, parsing, evaluating and minimal REPL. I'm already at over 100 commits and 900LOC of Rust (source: https://github.com/Wilfred/garden/tree/6b0ecf775b45047d927f00e0469e178b72c929f2).
miniblog.
Related Posts
There are *so many* ways that reading a text file can fail.
Maybe it doesn't exist, it's a broken symlink, it's actually a directory, it's not the encoding you expected, or perhaps you just don't have the correct permissions.
Reporting good errors is surprisingly labour intensive.
Finally migrated my 2014-era web application off an old server.
When I set it up, I tried to take good notes. These days I expect a bundle I can deploy with command -- a list of required packages is distro-specific, labour intensive, and bitrots!
There's a threshold where it's just easier to write a patch than to file a bug. It's more likely to result in a fix, but it can be more labour intensive.
I don't know where the line is. It seems to depend on the community's interest in patches, and whether you have commit privs.
