I don't understand the problem. It sounds like the C/C++ extension was proprietary. This sort of thing can always happen when you rely on proprietary software. Make an open source C/C++ extension and you wouldn't have this problem.
>It sounds like the C/C++ extension was proprietary
The extension itself it MIT licensed (so could be hosted on the open VSIX store, if it wasn't down because the Eclipse project is suffering from server issues right now). In theory any fork can patch out the check and re-release the extension.
However, the extension packages some binaries that are proprietary, and have been since about four years ago. People could re-implement those and re-release an open version of the extension, but you can't just (legally) take the proprietary binaries and ship them if you don't have the license.
Open alternatives actually exist, but their quality and ease of configuration depends on your use case. In large projects the proprietary extension seems to be worse from what I've read.
Yes, that is what I thought, too. (It would be a good idea to have a open source C/C++ extension anyways, whether or not the proprietary extension stops working with non-Microsoft code.) (Maybe there is such extension; I don't know; I don't use VS Code and VS Codium etc.)
There is an absurd amount of additional complexity that needs to be centralized in order to avoid third-party cookies.
Any website can add Google Analytics by copy and pasting 1 line of code. To avoid this cookie, you need to have your own analytics web app. This makes sense for medium-size websites, but if you have a small website your host will probably bill it as a separate website.
First-party comments? Now you need your own comment system, which means you have a long list of responsibilities that you simply wouldn't have if you just used Disqus or Facebook comments. All those spam links to virulent sites will be on your servers now.
Honestly, the Internet would be a much more awesome place if 3P cookies were the norm and everyone was okay with embedding everything everywhere. In the past hotlinking was a problem due to bandwidth concerns, but nowadays most of the traffic is bots anyway so it would be a drop in the bucket.
> First-party comments? Now you need your own comment system
This is incorrect. Without 3P cookies widgets like Disqus cannot track (and automatically sign-in) user across different websites, but everything else including posting comments or liking them should work, you just need to sign-in on every website instead of doing it once.
> Any website can add Google Analytics by copy and pasting 1 line of code.
Again incorrect. Google Analytics doesn't need 3P cookies to count the number of visitors. Without 3P cookies it is just harder to correlate visits across different websites, which is what website owners don't really need, why are you supposed to know what competitor sites your users visit? None of your business.
And for cross-site authoriation there are standards like OpenID. So we could disable 3P cookies right now and Internet will work just fine.
>Without 3P cookies widgets like Disqus cannot track (and automatically sign-in) user across different websites, but everything else including posting comments or liking them should work, you just need to sign-in on every website instead of doing it once.
I feel like I don't understand what a 3P cookie is, then. Isn't Disqus a third-party service? Doesn't it use a cookie to know you have signed in?
If you put a Disqus comment form or Google Analytics in your website, wouldn't you need a cookie popup to comply with GDPR and similar regulations that regulate sending user data to third-parties?
Is 3P cookie supposed to be about the domain of the cookie? But then can a script from one domain like GA set a cookie in a different domain like of a website that uses GA? That doesn't sound right, considering you can't do this server side.
Can you help me understand how would it work for it not to be a 3P cookie?
> Isn't Disqus a third-party service? Doesn't it use a cookie to know you have signed in?
Let's say Disqus JS code is embedded on a site A. Then it can set cookies for that domain. So when you enter your Disqus login and password on site A, it can send a request to Disqus server, obtain authorization token and save it in cookies for domain A. This way you will be recognized every time you visit site A.
This means that operators of site A may access those cookies too, but I don't see any problem here - it's their site anyway.
> If you put a Disqus comment form or Google Analytics in your website, wouldn't you need a cookie popup to comply with GDPR and similar regulations that regulate sending user data to third-parties?
Probably you need.
> Is 3P cookie supposed to be about the domain of the cookie?
3P cookie means that when site A includes content from site B (image, iframes) then the browser will send domain B's cookies with the request for that content. This means that if content from site B is included on 100 different websites, site B can track the user across them using cookies.
So when you sign into Disqus, it can recognize (and track your actions) you on any site using Disqus widget.
When 3P cookies are disabled, requests for content embedded from other sites like B, will be anonymous and without cookies. You will have to log into Disqus for every site where you want to leave a comment.
I see. That's a bit ironic. Cookies use useful because you don't need to use URL query parameters all the time. So what they are doing is taking the session token that would be sent in the Disqus domain cookie and storing it as an embedder's cookie, then using Javascript to put the cookie data in URL's / requests. In fact, "cookie" is probably not even a good method to do this since it will get send in embedder's requests. You could just use localstorage for it.
I've always found the negative effects of 3P cookies, the creepiness of being logged in on every site and ads following you around, to be symptoms of other problems (using the same browser profile for everything you do, a culture of not paying for websites so they have to rely on ads for monetization), so I'm not sure if this is a great solution to the actual problems.
But I guess it does make the internet better for the average person.
It's not surprising that there are legit uses like this for 3P cookies, and that the cons probably outweigh the pros. Browsers already stopped allowing cross-site caching for similar reasons years ago, which I'd say comes at a bigger cost.
Until I can change the color and font of everything on Linux the way I can on Windows XP, I'll never take Linux theming seriously.
Seriously, just make GUIs. That is the solution to ALL of Linux problems. MAKE THE GUIs!!! I can't select the background color of panes from a color picker and instead I have to manually edit text config files and create folders inside dotfolders. Ridiculous. It's 2025.
Not-exactly-devil's-advocate: you're trying to sort content by quality. That's elitist. Also, those those filtered contents are worth more. You can't have only premium contents.
Someone should do it anyway and make it dominant anyway ASAP.
Let the robot run ONE SITE. You still have Twitter, Mastodon, Bluesky, Facebook, Reddit, etc., if you want a non-stop stream of political content on your feed.
