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.
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.
Editors are irrelevant to that conversation, but people who are accustomed to relying on stacks with many dependencies will definitely find that they struggle more without the internet than people who keep their dependencies minimal. And it's not a cherry picked example, there are all kinds of cases where minimal dependencies = resilience. It doesn't mean you have to go around using punch cards or something, it's really just the emotional attachment to complex tooling that I'm calling out as a hazard here. You end up cultivating skills that are easily invalidated.