ace VS pylance-release

I used a note system built on top of Fossil as my primary system for quite a while. Here are the details in case anyone is interested.

Fossil allows CGI extensions[1]. There's a database for tickets, but that's just a regular SQLite table that you can use to store anything you want, and it's version controlled and queryable. I stored the notes plus metadata in the tickets database. The CGI returned HTML with the Ace editor for creating/editing notes.[2] Notes were stored using the command line.[3] I needed to add the web server user to the sudoers file to access the Fossil binary.

There were two reasons to use Fossil for this. The biggest was that it handled authentication. The second is that I had a version controlled database to do all the work for me.

I think I eventually moved away from it because I prefer working locally. The "transition" was dumping the data out of the database and into markdown files.

[1] https://fossil-scm.org/home/doc/trunk/www/serverext.wiki

[2] https://ace.c9.io/

[3] https://fossil-scm.org/home/help?cmd=ticket

Ace editor -> https://ace.c9.io/

Hey there! Thanks for reaching out. Writing a code editor with syntax highlighting in a browser can be a little tricky, but it's definitely doable. One resource that might be helpful is the Ace Editor library (https://ace.c9.io/). It's a lightweight but powerful editor that includes syntax highlighting for a huge range of languages. You could also check out CodeMirror (https://codemirror.net/), which is another popular library for building web-based code editors. Good luck, and let us know how it goes!

neocities seems to use the ace editor, and you can view its default keybinds here: https://github.com/ajaxorg/ace/wiki/Default-Keyboard-Shortcuts

The frontend uses the ace editor for syntax highlighting and then sends all the "text" you have typed to a python backend. The backend then writes all the text to a temporary directory and calls the compiler using subprocess (something similar to os.system).

It is built using Reveal.js and Ace, and is a simple markdown presentation tool right in the browser.

https://github.com/ajaxorg/ace

It's a pretty complex JavaScript application but you can development and even run tests locally without ever needing to "build". I'm building a JavaScript-based text editor, too, and it also uses Makefile and you can just run a static file server such as Python SimpleHTTPServer to host all the files in the directory. I still have and componentized HTML/CSS, separated JS files.

Thanks for the suggestion! Although Ace is not the most popular kid in the block, it is still maintained. It does support tmLanguage and could be used for a proof-of-concept editor!

For the code editing you can use Ace.

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