Live data from Hacker News

I’m switching from VS Code to VS Codium

ruky.me

61–70 of 343 posts

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

#61
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…

You're really missing an important factor of software development which is making things accessible to all walks of life. I simply prefer open source because it doesn't exclude specific classes of people because of money. Imagine a future where only rich people and those from wealthy families get access to the good development tools to help them get richer, while poor developers and those not from a wealthy family struggle to even get access to basic tooling, or have to exchange their personal information and rights in exchange.

Fortunately, many people in software are not simply money worshipers and envision a future where money isn't the priority in building a better world.

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

#62
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…

I am really curious but do not have the time to check this myself: is the vscode telemetry part of the open core bit? The reason I ask this is because I agree with your points and I usually allow telemetry for FOSS programs (for example [1]).

If the telemetry code is open and people can verify that there isn't any identifiable data that is being collected, I don't see any issue with leaving it on in vscode too.

[1] https://blog.davidedmundson.co.uk/blog/what-we-can-learn-fro...

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

#64
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 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 a great part of open source! But not something most professional software developers really expect to do for their IDE.

- open source formats are probably more resilient than closed source, but I would argue many proprietary formats are also pretty resilient. Code is also based on plain text at it's core, like latex, so it's always going to be pretty resilient.

- you'll never have a guarantee that a tool you invest time in or money in will be the leading tool in five years.

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

#65
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 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…

To piggyback off this, another reason that I think software freedom is valuable is community support. Things like LSPs, syntax highlighters, and that sort of support doesn't have to wait on JetBrains to integrate it into their IDE. I think there is real value to the community being able to hack on a tool and not being at the whim of a single developer's priorities

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

#66
post #7

If you're really that concerned about using propriety software why not help build the emacs or vim ecosystem instead?

Because some people don't necessarily want to tinker with emacs or vim for days just to get their perfect setup going

Convenience or freedom. Pick one.

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

#67
post #16

I started using vim 13 years ago. Editors come. Editors go. Vim remains.

Absolutely. On a tangential note, "Your problem with vim is that you don't grok vi" continues to be a favourite read: https://gist.github.com/nifl/1178878

Thank you, I might give vi another go.

Btw, for reading, raw version is better: https://gist.githubusercontent.com/nifl/1178878/raw/2a20bba8...

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

#68
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…

If Windows, Office, LinkedIn, GitHub, Skype and Chat are any indication, the telemetry situation will worsen severely over time.

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

#69
post #46
post #3

(Proprietary is spelled propriety in a few places.) I’m surprised VS Codium is so well packaged..

And principle is spelled principal in one place. I wonder if principle/principal border/boarder could have/could of their/they're its/it's will just become accepted alternative English spellings in time?

Excepting “could of” the spellings per se are all correct, they just mean something different than their alternative. How do you read text when you don't know what the words mean any more?

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

#70
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…

There's also the issue of signing in or applying a licence file on a system owned by someone else. In some environments this simply isn't allowed.
Post reply on HN