a) I'm going to be doing this "work" (which, okay yeah it is) full-time or even constantly, when I'm probably just going to hack on it for the next few months or years; whenever I've got a coding itch. I doubt I'll ever go into crunch mode on this or get "burned out". I'll just put it aside for a while and do something else.
b) That I can't just say "Whelp, it was fun but I'm done" at some point during the project and find something else to do. There's no hardcore commitment here; like all projects, everything beyond the first step is a pipe dream.
I get what you're saying though and it could definitely be a shitton of work that's probably not usable IRL. But it's still a fun plaything.
Perhaps I missed something in the post, but I don't see a "shitton" of work there.
The first step is easily a one weekend (if not one day) project. None of what was described is particularly difficult, complicated, or labor intensive. I wonder if people are making assumptions about all sorts of fancy extras that the post doesn't mention being included.
That's the time for pure code-work. Thinking/design/testing will eat up more time, but not that much more time. As described it's a pretty reasonable weekend project to last a couple months.
That's my interpretation, anyway. Not that hobbies are bad, but that this is gonna be a life-consuming hobby, will likely detract from other pursuits, and may not pay off as well as OP thinks it will.