this post was submitted on 05 Aug 2023
677 points (96.9% liked)

Technology

34920 readers
111 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] CaptDust@sh.itjust.works 17 points 1 year ago (2 children)

Note that Codium is a no go if you want to debug .NET projects, really annoying limitation MS put in place...

[–] RoyaltyInTraining@lemmy.world 17 points 1 year ago (1 children)

It's shit like this that keeps me from building any kind of trust in MS-owned open source projects.

Anyone thinking that Microsoft's recently found appreciation for open source isn't a Trojan Horse is a fool.

[–] fuzzzerd@programming.dev 1 points 1 year ago (1 children)

Is that because of the extension marketplace? Or the fact that the debugger has always been closed source?

[–] CaptDust@sh.itjust.works 2 points 1 year ago* (last edited 1 year ago)

VSDbg is closed source, technically licensed under visual studio, and only for MS products. Then they sprinkle some key check that prints a message telling you to use it in an official environment or whatever. It's dumb and needs resolved as part of their OSS efforts but seems more unlikely with each passing year.