4 ms·
Facebook does a lot of work like this for its internal development uses (also, when it used to open source Nuclide). I think this is a good first step, but the
by chillee 8y ago
Facebook does a lot of work like this for its internal development uses (also, when it used to open source Nuclide).
I think this is a good first step, but there's a lot more problems that are harder to solve than what this offers (and are what I'd consider the main problems that need to be solved...)
One example is language services. Integrating something like C++ autocomplete is difficult, and not something they seem to have done (looking at their page). The right way to do it is to run the C++ autocomplete on the server, and have some way of providing those suggestions over the connection to your local editor.
- mmcallister 8y agoWhere "some way" == the language server protocol[1] [1] https://en.m.wikipedia.org/wiki/Language_Server_Protocol https://en.m.wikipedia.org/wiki/Language_Server_Protocol
- LeanderK 8y agoshouldn't this be possible? I don't see why not?
- mmcallister 8y agoYes absolutely. I use LSP with VS Code every day. This solution shouldn't prevent me from continuing that
- chillee 8y agoYeah, that's definitely the direction people seem to be moving towards.
- nhooyr 8y ago> The right way to do it is to run the C++ autocomplete on the server, and have some way of providing those suggestions over the connection to your local editor. No need for integration. Its really up to a C++ plugin as this is just straight up VS Code.