Even more hindsight on Vim, Helix and Kakoune

Re:Even more hindsight on Vim, Helix and Kakoune by bourneavent on Thursday June 22, 2023 @06:22PM (#36439964)

>For instance, I've got a raspberry pi hooked up to some solar panels handling some gardening stuff for me, it'll be just fine.

You can remote ssh into the pi with Vscode or a jetbrains IDE with a laptop that likely won't be fried either under your description.

Python can run on the rasperry pi. Even high level interfaces will remain. Additionally GUI support exists on a Pi.

[ Parent | on HN ]

Re:Even more hindsight on Vim, Helix and Kakoune by __MatrixMan__ on Thursday June 22, 2023 @09:40PM (#36441758)

I'm aware of these features. I've used them in pycharm and intellij and vscode. I just find that they're a bit much to keep track of, and aren't usually worth it. I don't need a development focused OS in my OS, I have Linux for that.

It's been VSciode lately, and it's infuriating how it wants to handle everything for you. You can't just configure your linter, you have to do that and then figure out how to trick VSCode into invoking its linter in a way that respects the same configs otherwise CI won't agree with the dev experience--to name just one case of overreach.

And it's always guiding me to install this plugin or that widget and it's like:

> Great, now I'm relying on all of these undeclared dependencies and I don't know what kind of hell I'm creating for my PyCharm colleagues.

There's just a whole pile of problems that just don't come up if you let separate tools be separate tools.

[ Parent | on HN ]