-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I'm the author of https://github.com/pianocomposer321/yabs.nvim. I've been thinking for a while that it might be time for either a major refactor or a complete rewrite, and this last week I decided to just do it. I won't get into all the reasons why I thought this was a good choice (if y'all want to hear why, I'll probably explain in a separate post when I announce that the new version is done), but my question is this: when I'm ready to put the new version up on github, should it be in a new repository under a new name, or under a new branch in the current version? It seems that most other people have always done it under a new repository, but then I'd have to come up with a new name (😬), and it wouldn't have the same discoverability as the original repo did, at least at first (because it would start with no stars). On the other hand, if I made it just a new branch, I'd have to add a deprecation message to the current main branch saying that the new version will eventually take it's place, and that will be a small but annoying breaking change for existing users who don't want to switch to the new version.