3 ms·
> This means we ended up building completions by hand and soon, via the community. You like people to contribute for free ("build a community") but refuse to g
by wildmanx 5y ago
> This means we ended up building completions by hand and soon, via the community.
You like people to contribute for free ("build a community") but refuse to give them an actual FOSS client. This is bound to fail.
There are ways to make this go both ways though, and I hope you'll make them work once you are a bit further along in your journey. Exciting project!
- wodenokoto 5y ago> You like people to contribute for free ("build a community") but refuse to give them an actual FOSS client. This is bound to fail. Sublime text has a pretty active community that builds and shares extensions. Why not warp?
- ushakov 5y agoSublime is selling a product that users can purchase and own Warp is owned by venture capitalists
- scottlamb 5y agoMeh, I could be into it without them providing a FOSS implementation. Think of Microsoft's language server protocol. It's nice that VS Code is open source, but even if it weren't, we might still be using this protocol with rust-analyzer and neovim. Or any number of older protocols/formats with RFCs that didn't start with good FOSS implementations. In the case of completion, if you can generate (less rich but still useful) bash/zsh/fish completion scripts from these files, program authors might be happy to use it even in the absence of a fancy terminal.
- Siira 5y agoThere exists multiple fully functional FOSS LSP clients. The semi-proprietariness of VS Code does not doom LSP. The documentation people would contribute to Warp though are unlikely to have any popular FOSS clients.