Visual Studio Code is designed to fracture - I am very happy that I will be able to use emacs forever

[deleted]

Sorry for the OT. I have to say that blog's style is absolutely gorgeous. I'm reading it on a tablet and it's an delight for the eyes. I'll finish the article now :)

Very interesting page, thanks for sharing. So, the best thing about vs code is how it has stimulated text editors like emacs to still improve.

[deleted]

[deleted]

Great article. Very worried about the future of lsp after reading that. I'm curious to see what features lsp host will bring to vscode. And I wonder how or if the open source community can catch up or, at the very least, tread water.

The pull quotes are massively oversized on a desktop monitor, and the frequent embedding of links to other articles looks like ads. What do you like about the style?

Can't catch up to corporate level. Even trash shines if enough hands polish it. However, maintaining a simple yet pleasing and extensible feature set seems to work well so far. Simplicity is a good defense since complexity is their ~~offense~~ product. My guess is that they push towards recommendations because there's only so much else to do for an LSP server. Like some cute clip art going: "Hi, I'm lsppy, click me to add this trending snippet." At least for python, there is not much to worry if you're content with the status quo. The open pyls seems to perform as well as jedi did before. Probably because they share some code and because the checkers don't care which lsp calls them. But adopting Microsofts language server protocol simplified the configuration, which is nice. I'm still a bit worried about the github situation but it seems I might get away without a Microsoft account after all.

[deleted]

They say those who do not learn from history are doomed to repeat it and this new generation of developers assume Microsoft is giving us VSCode and Github out of the altruistic cockles of their corporate hearts, completely unaware that this is their business strategy: [https://en.wikipedia.org/wiki/Embrace,\_extend,\_and\_extinguish](https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish) I read the article as: * \[x\] Embrace * \[ \] Extend: In Progress * \[ \] Extinguish (For those that are too lazy to click the link) >"Embrace, extend, and extinguish" (EEE), also known as "embrace, extend, and exterminate", is a phrase that the U.S. Department of Justice found that was used internally by Microsoft to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences in order to strongly disadvantage its competitors.

I had the same impression, I had a difficult time actually following the article on my phone.

> the frequent embedding of links to other articles looks like ads. What do you like about the style? On the contrary, proper cross-referencing and linking is more reminiscent of proper papers and writings as far as I'm concerned. Albeit in this form it is updated to directly reference instead of just having some references appendix with no direct way to access the references (largely due to publishing bullshit in academia - the publishers are largely evil profiteering businesses - and the physical paper legacy it has - printouts can't do links).

Exactly my feelings upon reading this. That and wondering how they'll be stopped this time. They've learned from their mistakes and have spent lots more money lobbying over the years.

> blog's style is absolutely gorgeous I didn't pay attention to the style, I just sent the url to EWW, and read it through very quickly. I have to say, for a long time I was skeptical about eww and didn't see much use for it. Lately, I'm using it more and more. It's so nice to open any [raw] file on GitHub, change the major mode and go through it. I don't care anymore if GitHub can or cannot render Org files properly - I just read them in eww. I don't even try to search through GH Action logs in my browser, I open them in eww. Blogposts and essays? eww. Paywalled news articles? eww. Need to gather all the links on the page? eww. Want to extract stuff like rss feeds on the page? eww. eww has features like toggle-images, toggle-colors, toggle monospaced or variable fonts, and eww-readable - it heuristically tries to find main text and remove menus, navigation, etc.

The crisp typography, and the red text on black was surprisingly pleasing. The font size and line width fit perfectly to my tablet's dimensions. I'm looking at it on my PC now and it doesn't look half as good. The quotation text was a bit too big on the tablet but it didn't look as jarring as on a monitor.

Indeed. Atom is going away (November IIRC), forcing Atom user to migrate to Code. Eclipse seems to be a mess of stalling projects, and Emacs is Emacs: not bad, but definitely a higher bar.

Other companies are directly targeting lsp without vscode like Kdab/Qt I hope that balances the situation somewhat.

The VSCode ecosystem really sounds like the Chromium of Editors..

IMO, Jetbrains's Fleet is the best bet for a real VSCode competitor. Hopefully Jetbrains is able to pull market share away from Microsoft causing a side-effect of unifying devs from both camps into maintaining common LSP servers so they stay open.

(but then you miss all the beautiful website designs..