Remix.run Logo
erdaniels 6 hours ago

Hey ibobev! I've actually been building something very close to box at a snail's pace for 2 years. I built it since I was working a lot with a bunch of raspberry pis where it was better to compile directly on the pi then on my mac but I didn't want to bother to ssh in or lose my local setup. The major difference with what I have so far is that the tool takes a direnv automagical approach to work with multiple machines across multiple projects/directories. It works across docker and ssh without any extra setup other than the tool on the client side.

I just got native LSP working this past weekend and in sublime it's as much as: { "clients": { "remote-gopls": { "command": [ "tool", "lsp", "gopls" ], "enabled": false, "selector": "source.go", }, } }

From what you built so far, do you think there's any appetite in people paying for this type of tool which lets you spin up infra on demand and gives you all the capabilities built so far? I'm skeptical and I may just release it all as OSS when it gets closer to being v1.0.

lightandlight 6 hours ago | parent [-]

> do you think there's any appetite in people paying for this type of tool which lets you spin up infra on demand and gives you all the capabilities built so far?

(I'm not the author) The easiest way to charge for this kind of software is to make it SaaS, and I think that's pretty gross, especially for a CLI tool.

> I'm skeptical and I may just release it all as OSS

It doesn't have to be one or the other: you could sell the software under libre[1] terms, for example.

[1]: https://en.wikipedia.org/wiki/Free_software

erdaniels 5 hours ago | parent [-]

Agreed that SaaS feels ugly. Agreed on selling it as libre. The only thing I could imagine charging for in a subscribed model would be for services that are hosted (e.g. instance/gpu provisioning/monitoring/maintenance in the cloud) while also offering the ability to self-host the same machinery.