Earlier quoted context omitted.
VSCode is embracing Eclipse team and Eclipse way of opensource IDE ecosystem.
No. It's Eclipse that took Microsoft made Monaco editor and built Theia on top of it.
Microsoft hired ex-Eclipse team to build VSCode.
Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
221–227 of 227 posts
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#222There are just certain technologies my brain says "fuck, no" to. GNOME. The Great Banality Laser (whose official name was once Twitter). Visual Studio Code. The fullness of time usually proves my brain's initial impressions right, as it seems to be doing now with Visual Studio Code. I can still remember the monthly paroxysm of bliss that radiated throughout Hackernews, regular as clockwork, timed with Microsoft's mon…
Please explain Gnome, im a happy user after some years of i3 and hyprland. Gnome just works ^tm.
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#223Earlier quoted context omitted.
Compatibility can be iffy though. I eventually switched back to the official VSCode application because I was fed up that extensions kept breaking randomly. I'm worried that Microsoft is succeeding at making the semi-proprietary version of VSCode the only viable option, while keeping the OSS forks as second-class citizens at best.
How common is this? I've used for years and haven't encountered plugins breaking on me.
I don't know, it's just my personal experience. I used the "OSS Code" fork for a few years on Archlinux but Python intellisense kept breaking when I needed it the most, often with one cryptic error or another. Sometimes I could fix it by switching to VSCodium, installing/uninstalling the `code-features` package, or some random config tweak, but at some point I just got tired of fighting the editor instead of coding.
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#224Lloks like Microsoft is going back to it's old ways. I am not surprised tbh.
I mean, Microsoft has been very clear about their business model of VSCode -- similar to Chromium, the base product is free and you can do whatever you want (and indeed there are lots of products reusing the core of VSCode), but extension marketplace/remote/GitHub Copilot are proprietary. It sounds like a fair deal to me -- Microsoft can't just do open source without expecting to get something in return. Now, coming…
Do you have any links or resources you could direct me toward that were more helpful than Microsoft's basic how-to pages for learning VS Code plugin development? I attempted to build a VS Code extension, but the attempt fizzled out. I managed to make some progress in creating the simplest of UI elements and populating them. I'm particularly interested in building a GUI-based editor of JSON / YAML where a user can select a value from a prepopulated dropdown menu, or validating a JSON / YAML file against a custom schema. Any help or advice you could provide would be appreciated!
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#225Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…
Not malicious, but still selfish. It's important to remember that the copilot extensions are an extremely effective way of monetizing VScode. So it seems more like they're kind of compromising on their API usage rules in order to get to market quicker. But allowing themselves to use the APIs before anyone else is in a way anti-competitive, because the only way one could compete would be to use the unfinished APIs. Bu…
Your VaporView extension looks amazing! I can't even fathom how to get that far along in extension development.
Do you have any links or resources you could direct me toward that were more helpful than Microsoft's basic how-to pages for learning VS Code plugin development? I attempted to build a VS Code extension, but the attempt fizzled out. I managed to make some progress in creating the simplest of UI elements and populating them. I'm particularly interested in building a GUI-based editor of JSON / YAML where a user can select a value from a prepopulated dropdown menu, or validating a JSON / YAML file against a custom schema. Any help or advice you could provide would be appreciated!
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#226Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…
> Everyone is reading this as intentional anti-competitive practices Who cares about intention? Anti-competitive behavior is anti-competitive behavior.
Anti-competitive behavior is absolutely fine though when not illegal. I don´t see how vscode could be constructed as having a monopoly when cursor freely forked it.
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#227There are just certain technologies my brain says "fuck, no" to. GNOME. The Great Banality Laser (whose official name was once Twitter). Visual Studio Code. The fullness of time usually proves my brain's initial impressions right, as it seems to be doing now with Visual Studio Code. I can still remember the monthly paroxysm of bliss that radiated throughout Hackernews, regular as clockwork, timed with Microsoft's mon…
Please explain Gnome, im a happy user after some years of i3 and hyprland. Gnome just works ^tm.
Back in the day I looked at a GNOME 1.0 binary and saw it had like 60 library dependencies.
Aint_nobody_got_time_for_that.mov
Given the utter malarkey that's transpired since with GNOME, including the crappy UI revamps, the slowness (in the Windows 7 days, it was literally better just to use Windows on aging hardware), and the arrogant devs reinventing Windows 8 poorly and not listening to what users actually want, nor allowing users to make changes, I've been VERY happy keeping my environment GNOME-free.