On the LSP stuff, yes it did originate in VS code. I just find the experience in Sublime to be better. How ironic is that?
I didn't consider the conflict between how I said "try the OG" but then say "VS code is the OG". It is a good point.
I show an example of the block level key binding. So yeah, I needed it and used it. I only showed one example but I have a few more that are my own I just didnt write about them.
Around python vs. js for plugins, have you tried to make a VS code plugin? You need a package.json, npm, and vsce installed globally. Which language is being used is usually the least of my problems. For Sublime, you need a single .py file! Someone shared this 9 line plugin they made: https://gist.github.com/ckunte/31500c17452b0fd8c55bc9460bd9c... - I don't tthink plugin development could be more simple
I bet an LLM could spit out single file plugins very easily. VS code plugins are clearly more work to create and deploy even after taking into account my critiques of Package Control. At the end of the day you can just toss your plugin in a folder or push it to github and reference it with a URL.
I didn't say the docs were "terrible". I just said they were disjointed. They are complete and fully document the APIs. I just wish they were more like the PHP docs or the ones for VS code which are docs plus guides.
All your other points are fine critiques. I'll chalk the other complaints up as a matter of opinion
I didn't consider the conflict between how I said "try the OG" but then say "VS code is the OG". It is a good point.
I show an example of the block level key binding. So yeah, I needed it and used it. I only showed one example but I have a few more that are my own I just didnt write about them.
Around python vs. js for plugins, have you tried to make a VS code plugin? You need a package.json, npm, and vsce installed globally. Which language is being used is usually the least of my problems. For Sublime, you need a single .py file! Someone shared this 9 line plugin they made: https://gist.github.com/ckunte/31500c17452b0fd8c55bc9460bd9c... - I don't tthink plugin development could be more simple
I bet an LLM could spit out single file plugins very easily. VS code plugins are clearly more work to create and deploy even after taking into account my critiques of Package Control. At the end of the day you can just toss your plugin in a folder or push it to github and reference it with a URL.
I didn't say the docs were "terrible". I just said they were disjointed. They are complete and fully document the APIs. I just wish they were more like the PHP docs or the ones for VS code which are docs plus guides.
All your other points are fine critiques. I'll chalk the other complaints up as a matter of opinion