Live data from Hacker News

I’m switching from VS Code to VS Codium

ruky.me

281–290 of 343 posts

Re: I’m switching from VS Code to VS Codium

#281

I can partially understand the desire to switch if there are (free) plugins available on VS Codium that is not on VS Code. However leaving VS Code because of not trusting Microsoft's off switch for telemetry for the IDE and the plugins they provide is an unintentionally uninformed decision IMO. Of all actors, one should probably trust the privacy protections and off switch of a BigCo, like Microsoft, since they tend…

The company that has been caught with its hand in the cookie jar…

I don't know, several hundred times?

Re: I’m switching from VS Code to VS Codium

#282

Earlier quoted context omitted.

That's like saying that hardware should be only repairable by vendor because majority of humanity doesn't have skills to fix it themselves.

That's not even close to what they said. They said, you can do it "if you have the skills" and that "the large majority of humanity does not" have these skills.

That's literally what they've said. They imply that having ability to change something is useless, because only a minority can leverage it.

Re: I’m switching from VS Code to VS Codium

#283
post #42
post #6

Their main argument is “no telemetry” (or sometimes “no cemetery tracking”…), but VS Code has a setting to disable telemetry [0], and I would trust that it’s really disabled if you set it so (why would they lie about something quite trivial to check with Wireshark or such?) > I’m sure there is a small performance gain because you don’t have telemetry running in the background sending data to Microsoft. Have you profi…

I agree but also - a controversial opinion - I am pretty sure Microsoft collects the kind of telemetry to learn about user behavior and improve the IDE, and not to collect private information for some kind of other gain. I am sure that whoever develops Codium will eventually get into a dead-end at some point because they won't have any telemetry connected to the product usage. Other piece is that Codium might inheren…

This doesn't jibe with history. Or the present for that matter, see sibiling to your comment by btdmaster. Uses of data always expand, never contract.

It doesn't matter that most or even 99% of the data is harmless, or that the data is useful, these companies are simply not trustworthy. The fact that no one asks permission up front (opt-in) tells you all you need to know.

Re: I’m switching from VS Code to VS Codium

#284
post #242

Earlier quoted context omitted.

It might be worth contacting these extensions' creators. If you already have the `.vsix` file for the VSCode marketplace, publishing to open-vsix is really super simple (create an account once, get a token, add a few lines to your publish script, e.g. https://github.com/prisma/language-tools/blob/94e4cd612d03ef... ). Some just do not know about it.

PyLance and the remote extensions are developed by Microsoft. They intentionally do not work with the open source editor.

Oh, I did not connect these dots.

Shucks.

Re: I’m switching from VS Code to VS Codium

#285
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

I'll flip the script, why are you so worried about other people choosing editors like vim and emacs? Lots of people don't struggle. Lots of people don't mind a extra few hours for open source solution as it fits their life choices.

Re: I’m switching from VS Code to VS Codium

#286
post #64

Earlier quoted context omitted.

I think most of us value our freedom more. Most people don't think of it in terms of freedom, but freedom it is. With proprietary software: - You don't know when it will disappear or be discontinued. Even your paid-for existing version stops working when the activation servers go down. - You might be forced into an "upgrade" which breaks something you rely on - That's not to mention issues like being able to fix bugs…

Most of your points also apply to open source software, and aren't strict requirements for proprietary software. - discontinued: Atom just got discontinued. It's open source. Photoshop on the other hand has withstood the test of time. - Audacity's 3.0 update removed a feature I relied on. I wasn't forced to update to it, sure, but proprietary software doesn't force updates either. - Being able to fix your own bugs is…

lots of modern proprietary software does require a license to to continue to use and cloud version are updated all the time without any input at all for you.

Re: I’m switching from VS Code to VS Codium

#287

Earlier quoted context omitted.

> Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of them are After a particularly bad tooling week (js supply chain problems, plugin problems and more than the usual amount of DB changes) Our dev team made the unanimous call to move require all developers to use Jetbrains IDEs instead of the…

> Our dev team made the unanimous call to move require all developers to use Jetbrains IDEs Wow, it'd be time to look for a new job. I think having a blessed option and understanding of "use what you want but don't let it affect deliverables" is best.

>Wow, it'd be time to look for a new job.

Everyone on the team agreed. If one person had said no, we would not have made the jump.

> I think having a blessed option and understanding of "use what you want but don't let it affect deliverables" is best.

That's kind of how it worked out for us. We didn't ban emacs or vs code, we just all agreed we'd go Jet Brains first and mostly... and for the more senior of us (me especially), go out of the comfort zone and learn the new tool.

Re: I’m switching from VS Code to VS Codium

#288

Earlier quoted context omitted.

> discontinued: Atom just got discontinued. It's open source. Photoshop on the other hand has withstood the test of time. Photoshop has not withstood the test of time for me. I did a lot of Photoshop a few decades ago. I can't afford > $1000 per year for a hobby. My old Photoshop files are dead, for all intents and purposes. I do occasionally use decades-old, unmaintained open-source tools to open old files. > Audaci…

> I can't afford > $1000 per year for a hobby. In the UK a year's license for Photoshop, Lightroom and Bridge is approx £110.

That doesn't help him if he doesn't live in the UK though?

Re: I’m switching from VS Code to VS Codium

#289

Earlier quoted context omitted.

I think most of us value our freedom more. Most people don't think of it in terms of freedom, but freedom it is. With proprietary software: - You don't know when it will disappear or be discontinued. Even your paid-for existing version stops working when the activation servers go down. - You might be forced into an "upgrade" which breaks something you rely on - That's not to mention issues like being able to fix bugs…

Sorry, but developers don't care about freedom, they just want things that are free == gratis == zero cost.

that's not true. Sure the majority may not care but a sizeable and talented core do or we would have nothing but proprietary software to use right now.

Re: I’m switching from VS Code to VS Codium

#290
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

[deleted]
Post reply on HN