▲ | NitpickLawyer 3 days ago | ||||||||||||||||||||||||||||||||||||||||
We've been using devcontainers for this, as it's already got good support in vscode. Could you perhaps "elevator pitch" the main differences between devbox and devcontainers? | |||||||||||||||||||||||||||||||||||||||||
▲ | whinvik 3 days ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||
Yes, it feels very similar to Devcontainers. But having tried Devcontainers a lot, it feels like its probably a complex specification since outside of VSCode every implementation has issues. The CLI on Mac has weird user permission issues. Cursor's implementation is very flaky. Zed doesn't implement it yet. So maybe there's space for more solutions in the same space but Devcontainers are very feature rich. And not to mention they have a huge user base via VSCode. | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
▲ | zeroq 3 days ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||
Very good question, and even if your product is better it seems like an uphill battle. devcontainers are backed by MS/VS and they have good incentive to make them work. Why you think your solution will succeed in long run and win over devcontainers? |