| > It seems like with the recent AWS announcement of CodeCatalyst I took Code Catalyst for a spin the other day and it is terrible. https://twitter.com/GeoffreyHuntley/status/15997732931288637... > It seems like maybe the best position for Gitpod is an acquisition (possibly by Atlassian) I agree. I used to work there and think they need to slash circa 40 employees to shrink down to more sustainable burn rate numbers - https://ghuntley.com/tea > but the odds are stacked against them In more ways then one https://ghuntley.com/fracture documents Microsoft's strategy with Visual Studio Code which means 6 out of 10 top programming languages integrations only work on GitHub Codepaces. If you want .NET, C++, C, Python or Jupyter then the LSP integrations cannot be legally used on Gitpod. GitHub Codespaces got one thing right - they chose IaaS as the brick of compute meaning they can do GPUs and run Kubernetes clusters. On Gitpod, you can't because Gitpod chose Kubernetes as the compute abstraction. Gitpod needs to ditch Kubernetes... https://github.com/gitpod-io/gitpod/issues/4889 and https://github.com/gitpod-io/gitpod/issues/10650 |
Can the user install them? How complicated these are? Is there some awareness about this in OSS communities? If yes, is there some kind of consensus? (Is it something like: okay, then each programming language project needs to provide its LSP, like Rust has rust-analyzer, Scala has Metals, etc..?)