For my hobby projects or even more recreational programming I often choose some technologies that have some aspects I'm interested in learning I can't easily do

For my hobby projects or even more recreational programming I often choose some technologies that have some aspects I'm interested in learning I can't easily do during the day job. E.j. a different paradigm, digital signal processing, desktop vs web app, etc. Because during work I tend to be very pragmatic, and choose pretty boring, but battle tested technology. For the projects I have been working so far, usually niche tech doesn't provide enough tangible benefits to justify the risk of choosing it, the generally smaller ecosystem, less tooling, fewer documentation and potentially longer developer onboarding. Doesn't mean only the most established things one can choose, but avoiding things that are too new and unknown or too far off of what I'm comfortable working with. And once a tech stack is chosen you are likely not going to change it significantly for years to come. So it can get a little stale and I can get an urge to try new things. But my warm fuzzy feelings or curiosity for some new tech doesn't justify increasing complexity by adding no stuff to a production product/service.