Hacker News Reader

Comment by bitcharmer | Hacker News Reader

Influx 1.8 was and still is great. With 2.x and InfluxData shoving ridiculously slow Flux down people's throats on every step they managed to drive away much of their user base.

I just hope 3.0 will bring back more focus on query performance and simplicity.

View on HN

I think they lost a lot of goodwill in 2.x with Flux and subsequently abandoning the thing they were pushing so hard. They also now have 4-5 different names for the same piece of technology in its various incarnations

Honestly someone should just fork the InfluxDB v1.x line and focus on stability and performance. The pre-1.0 to 1.0 release was painful, but what's there now is pretty solid as well as MIT licensed.

It blows my mind that they still have not learned their lessons with world breaking changes. How can you build anything on a database that is constantly reinventing itself chasing some new hotness?

I found Flux to be awesome in that it allowed me to express queries that wouldn’t be expressible at all with promQL or SQL. Yes, you could write down a query that was extremely slow, but I rarely hit those cases.

Not that I’m going to miss it very much; in fact them going back to SQL in IOx immediately put brakes on my effort not only to further learn the language, but also any desire to write any further dashboards and left me feeling I wasted a bunch of time learning it as much as I've done up to that point. I just hope they don’t end up going back to Flux again in 4.0.

Yeah but is 1.8 effectively dead?

Reply on news.ycombinator.com