| ▲ | mdaniel 2 days ago | |
> Currently, the LSP implementation is partially closed-source What. the. fuck. So, it's Apache 2 for the TypeScript, seems to ship an Apache 2 copy of IntelliJ (just like any Java language server), but smuggles some kind of binary. They truly have lost their way | ||
| ▲ | jillesvangurp 2 days ago | parent | next [-] | |
> Currently, the LSP implementation is partially closed-source, primarily for the sake of development speed convenience -- it heavily depends on parts of IntelliJ, Fleet, and our distributed Bazel build that allows us to iterate quickly and experiment much faster, cutting corners and re-using internal infrastructure where it helps. After the initial stabilization phase and defining the final set of capabilities, we will de-couple the LSP implementation from the internal repository and build pipelines and open source it completely The full quote ... Instead of working on this behind closed doors for the next year or so and then open sourcing everything, they are releasing some open source now with the intention to open source the rest later. I see no problem with that. Seems pragmatic. More companies should do that. Bottom line, you are getting free stuff now. Some of it OSS now. All of it OSS later. No need to get upset. | ||
| ▲ | kartikarti 2 days ago | parent | prev | next [-] | |
Why overreact? Closed-source - bad, first steps towards open-source - bad. Is it always all or nothing? | ||
| ▲ | pjmlp 2 days ago | parent | prev [-] | |
Not like any Java language server. Red-Hat/Microsoft ship Eclipse headless, and Oracle ships Netbeans headless, they don't ship an Apache 2 copy of IntelliJ. And really, just get the full deal instead of running them headless alongside Electron package. | ||