@heaths it's really OSS in general, we're undergoing a pretty significant disapora of maintainers from their popular packages and nobody is willing to pick up the slack (usually because it was a passion project)
I even started on my own tui library in go but haven't been able to bring myself to finish a v1 on it yet
@chas That, and it seems a lot of people like to start a hobby project to learn a language or framework, publish it "just in case others find it useful", then never really maintain it. Seems at least once a week I see at least one person talk about learning rust or go by writing a new web framework.
Fine, but don't publish it. Or hack on an existing one and benefit from their idiomatic experience.
@chas Increased discovery times - both to pull indexes and wade through search results - exhaustion of ideal names (my org is dealing with this now), increased storage and bandwidth costs, etc. Why not leave it on GitHub, Gitea, or wherever? It's idiomatic for go and easy for rust with little to no downside for small projects.
@heaths oh when you said publish I interpreted that as public github - not package repositories (which are notoriously consuming cool names at the same speed we destroyed ipv4 space)
@heaths back to your original point - I've even been guilty of publishing "meme" libs before (usually to prove a point, like a library on npm that removed eval from javascript because I was mad at someone for abusing it)
@heaths I am rather a fan of go's usage of git host paths as part of the package name, it works really well for my brain for some reason (and for uniqueness)
as well as the ability to rename an import on top of that if you DO run into simple conflicts
Add comment