Whatever floats your boat, but just to be clear my own language and virtual machine do have tests. The value of tests depends on the domain. Graphics and games benefit less from tests. My graphical text editor straddles the worlds.
I'm still using version control as I've clarified elsewhere. I wasn't expecting this post to gain such a broad audience; I realize now it is really about how one's workflows can keep one stuck in a rut, a local optimum.
Thanks for clarifying. I think you might want to make this clearer in the blog post, since many people had the wrong impression.
> The value of tests depends on the domain.
I agree with this. And like I said, for small throwaway projects and quick experiments I can see how tests and version control can be tedious to deal with. But even in projects like your Freewheeling Apps, where you're releasing them to the public and encourage people to use, you're doing them and yourself a disservice to not have tests.
But you clearly know what you're doing, so I'll stop preaching. :) Good luck with your projects!
BTW, I'm a big fan of LÖVE and it's super interesting what you're using it for. I only imagined it was good for games, not apps.
Thanks! I should add that almost every app you can get to from https://git.sr.ht/~akkartik/lines.love by traversing the "Mirrors and forks" sections of readmes has these thorough tests for the editor widget. Certainly every app you can see in the family tree image map from 2023 does: https://akkartik.name/freewheeling/#resources. It's only a tiny new sub-tree that currently does not:
I'm still using version control as I've clarified elsewhere. I wasn't expecting this post to gain such a broad audience; I realize now it is really about how one's workflows can keep one stuck in a rut, a local optimum.