pylance-release VS Code-Server

One of the things that comes to mind here is the fact that the default Python extension for VS Code is, perhaps surprisingly to many, not open source. https://github.com/microsoft/pylance-release

While it's possible to fork VS Code, it is not possible to fork VS Code and provide a seamless onramp towards a Python editing experience that is fully open source, because users are used to the nuances of the closed-source Pylance experience in VS Code proper. You could use the minified/compiled Pylance plugin in your fork, but you'd have no way to expand its capabilities to new hooks your fork provides. Microsoft's development process would always be able to move faster than a fork, because it could coordinate VS Code internal API development with its internal Pylance team, and could become incompatible with forks at any time.

It's worth re-reading the quote from J Allard in https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... with this modern example in mind.

(Also worth mentioning https://github.com/detachhead/basedpyright?tab=readme-ov-fil... which is a heroic effort to derisk this, but it's an uphill battle for sure!)

Anyone know how can we fix this issue if we build the vscode locally

Do any of these issue tickets explain the behaviour you're seeing? https://github.com/microsoft/pylance-release/issues/4341, https://github.com/microsoft/pylance-release/issues/4071

Maybe they "are the same thing" in terms of behavior (I don't know), but "A uses B" doesn't mean that "A is B".

One important difference in this case is that while "Pylance leverages Microsoft's open-source static type checking tool, Pyright" [1], Pylance itself is not open source. In fact, the license [2] restricts you to "use [...] the software only with [...] Microsoft products and services", which means that you are not allowed to use it with a non-Microsoft open source fork of VS Code, for example.

The license terms also say that by accepting the license, you agree that "The software may collect information about you and your use of the software, and send that to Microsoft" and that "You may opt-out of many of these scenarios, but not all".

[1] https://github.com/microsoft/pylance-release

[2] https://marketplace.visualstudio.com/items/ms-python.vscode-...

There's this one: https://github.com/microsoft/pylance-release/issues/4174 (rules don't apply properly, and ovverrides don't work even after being set, this is especially for the more generic ones like )

The example is not .NET in general, but that specific event when Microsoft reneged on open development tooling[1]. For some people, that was the moment they stopped trusting "new Microsoft" to keep their word (though for me, it was when the Python language server was replaced with a DRM-locked, LSP-noncompliant one[2] a bit before that; unlike .NET hot reload, they didn't backtrack there). I can think the company makes great open .NET tools and at the same time not trust them to close it down on a whim.

Does anyone know where the open xlang reimplementation of MIDL went[3], by the way? (Unlike 1990s MIDL, you can't reimplement this one from the language grammar in the docs, because there is no language grammar in the docs.)

[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there

[2] https://github.com/microsoft/pylance-release/issues

[3] https://github.com/microsoft/xlang/pull/529

Coder|Remote first - US/Canada | Full-time Software Engineer - Open Source | $140K to $180K DOE and location

We keep developers in flow. Coder has created a devtool that offloads development from local workstations to your on-prem and public cloud infrastructure. Target customer is engineering orgs at some of the world’s largest and cutting-edge companies. Our tech stack is TypeScript, React, Golang, Terraform, Linux.

Check us out: https://coder.com/ https://github.com/coder

Disclaimer: The whole process happens locally in the tablet, therefore all the programs are executed inside the tablet. I saw some other tutorials where people use code-server and besides the coding experience might look the same, running the full OS offers more capabilities.

Code-server is an open-source tool that allows you to run VSCode, a popular integrated development environment (IDE), on a remote server through the browser. This setup essentially turns VSCode into a cloud-based IDE, providing flexibility and accessibility advantages.

Coder | Remote first - US/Canada | Open-Source Full Stack Software Engineer: Full time, perm. Min 3 Years of exp - Go, Typescript, React | We love seeing active open-source GitHub and side project work | Base: $120K to $162K/ yr DOE and location

We keep developers in flow. Coder has created a devtool that offloads development from local workstations to your on-prem and public cloud infrastructure. Target customer is engineering orgs at some of the world’s largest and cutting edge companies. Our tech stack is golang, terraform, linux.

Check us out: https://coder.com/ , https://github.com/coder Apply online: https://jobs.ashbyhq.com/Coder

Code Server is an open-source project that allows you to run Visual Studio Code (VS Code) in a remote server environment, accessible through a web browser. VS Code is a popular source code editor developed by Microsoft, known for its lightweight and extensible nature.

Install | Github | License

> Is there any web-based version of VSCode other than VSCode.dev or any open source alternative?

This maybe? https://github.com/coder/code-server

https://github.com/coder/code-server is like vscode.dev but self hosted

If you're just looking for an alternative to codesandbox, why not take the https://github.com/coder/code-server? It's basically a hosted VS code.