> They are standardizing around k8slens instead of kubectl. Why, because there are things you can do in k8s lens (like metrics) that you'll never get a good experience around in a terminal.
It looks like a limitation of the tool, not of the method, because metrics could come as CSVs, JSON or any other format in a terminal
> I'm pretty much the only one still in vim, I'm not giving up my efficiencies in text manipulation.
I love vim too :)
> I don't disagree with you, but I do see a trend in preferences away based on my experience, our justifications be damned
Trends in preferences are called fashions: they can change the familiarity and the level of experience through exposure, but they are cyclic and without objective.
The core problem is the combinatorial complexity in the problem space, and 1d with ascii will beat 2d with bitmaps.
I'm all for adding graphics to outputs (ex: sixels) but I think depending on graphics as inputs (whether scriping a GUI or processing it with our eyeballs) is riskier and more complex, so I believe our common preferences for CLIs will prevail in the long run.
I think it has more to do with how close to the brink you are. It takes at least a decade for a technology to mature to the point where there's a polished point and click gui for doing it. It sounds like Borg just hit that inflection point thanks to k8slens which I'm sure is very popular with developers working at enterprises.
> It takes at least a decade for a technology to mature to the point where there's a polished point and click gui for doing it
That makes a lot of sense, and it would generalize: things that have existed for longer have received more attention and more polish than fresh new things
I'd expect running a binary to be more mature than running a script, and the script to be more mature than a GUI, and complex assemblies with many moving parts (ex: a web browser in a GUI) to be the most fragile
That's another way to see there's an extremely good case for using cosmopolitan: have fewer requirements, and concentrate on the core layers of the OS, the ones that've been improved and refined through the years
> because metrics could come as CSVs, JSON or any other format in a terminal
You're missing the point, it's about graphs humans can look at and gain understanding. A bunch of floating point numbers in a table are never going to give that capability.
This is just one example where a UI outshines a CLI, it's not the only one. There are limitations to what you can do in a terminal, especially if you consider ease of development
It looks like a limitation of the tool, not of the method, because metrics could come as CSVs, JSON or any other format in a terminal
> I'm pretty much the only one still in vim, I'm not giving up my efficiencies in text manipulation.
I love vim too :)
> I don't disagree with you, but I do see a trend in preferences away based on my experience, our justifications be damned
Trends in preferences are called fashions: they can change the familiarity and the level of experience through exposure, but they are cyclic and without objective.
The core problem is the combinatorial complexity in the problem space, and 1d with ascii will beat 2d with bitmaps.
I'm all for adding graphics to outputs (ex: sixels) but I think depending on graphics as inputs (whether scriping a GUI or processing it with our eyeballs) is riskier and more complex, so I believe our common preferences for CLIs will prevail in the long run.