For years the ssh type lag made a remote editor too painful. Now we have things like mosh (with local echo) or syncthing or even native vim scp url support. What makes this better? I can’t tell from the website.
For years the ssh type lag made a remote editor too painful. Now we have things like mosh (with local echo) or syncthing or even native vim scp url support. What makes this better? I can’t tell from the website.
Booste allows GUI code editors like VS Code and Sublime.
I’m not saying your idea isn’t viable, but there are multiple players moving in this direction.
To me, the main thing you’ll have to convince me of is that this is better than editing code locally, but running the code in a local Docker container. For me, this solves the issue of “it runs on my machine”.
From my perspective, your main value add is trying to make executing and testing code on a remote server frictionless (it’s not quite there, but pretty good so far). And that you can edit on a low-resource machine, but effectively “develop” on a more powerful remote system. But these might be a tough sell if you’re targeting the HN crowd (which I’m not sure you are).
The docker point is fair too. Docker containers solve the machine problem, and are incredibly helpful teck. There are perks of cloud hosting (visibility by team, potential to monitor prod and have the codebox reflect it, performant hardware) that we can layer on top of docker container tech. Just hypotheses, to be clear. But to me, we're doing to Docker what Google Docs did to MS Word.
Coupled along with something like docker-machine for instantiating those remote instances, what does this setup not offer that yours does?