Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I’m switching from VS Code to VS Codium

ruky.me

Post reply on HN
Print view View original

301–310 of 343 posts

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

#301

Post by qmmmur »

jmyeet wrote: 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 entire argument is predicated on your personal preference being superior. Sorry it’s not and neither is mine; it’s entirely context dependent and individual.

I found all of the JetBrains offerings really tacky and expensive for the price. VSCode and neovim work far better for what I want and are more extensible.

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

#302

Post by mekster »

blip54321 wrote: post #33
jmyeet wrote: 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…

Along with your other points, you're not making any sense.

> - That's not to mention issues like being able to fix bugs yourself, extend it, or understand it. I don't do this often directly

That's just saying it's better for paid products because there's always someone paid to fix stuff instead of relying on volunteers.

I care to get the work done in the easiest way possible. And I hardly believe JetBrains will go away anytime soon, besides, using less productive tools until you see the paid competitors leave is really a dumb idea. If JetBrains were to disappear tomorrow and somehow they disabled my perpetual license along with them, I'll have to switch to Vscode but why let go of the benefit with your hypothetical concerns that may not materialize for years to come?

Sounds like you're just trying to create excuses to stay on your free apps.

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

#303

Post by FireBeyond »

7steps2much wrote: post #265
FireBeyond wrote: post #256

Earlier quoted context omitted.

How long do you expect the version you own to be supported though? Security updates? Bug fixes? Feature requests?

I wouldn't expect feature updates at all. In my mind it works like this: New features are adding value. This is something that the developers should be paid for! Releasing a new version for features is justified. Security updates/bug fixes on the other hand are "fixing" things with their product. In my opinion those should be provided because developers should strive to develop good products. But to give you a somewh…

I think that's entirely reasonable. I'd be expecting two years, too as my "high end" expectation.

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

#304

Post by johnny22 »

mangamadaiyan wrote: post #24
buf wrote: 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

the problem isn't the process of using vim. I like that part. The part i dislike is the ecosystem of plugins and extension points.

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

#305

Post by mekster »

varajelle wrote: post #243
mbesto wrote: post #172

Earlier quoted context omitted.

> But if I want to use Atom I can fork it, or keep the source around. It doesn't go away from my environment until _I_ say it does. This is technically true, but in 99% of the cases is not realistically true. Most developers who use said FOSS external dependency do not want to actively maintain it themselves.

For the atom case, it seems some users are going to continue to maintain it: https://github.com/atom-community/atom/

Might be more interesting to follow the next editor the author is working on.

https://zed.dev/

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

#307

Post by vasac »

kingboss wrote: post #229
axkdev wrote: post #140

Earlier quoted context omitted.

I was a jetbrains guy until I discovered the vim/neovim ecosystem. Yes, configurling vim takes time but 1.its fun 2. I can fine tune it to my specific work flows in ways simply not achievable with Idea or any other editor. After configuration is finished, the actual time it takes to do my work is comparable with a full fledged ide. It's probably even faster, considering vim loads faster and also forces you to use the…

Imagine being on your deathbed thinking: "Configuring vim was so fun. Totally worth it". I sometimes feel that most people on this forums are under 24 years of age. So sad to read these comments. So much to do, so many interesting things.... but people enjoy configuring text editors...

Guilty as charged ;)

But still beter than being on a deathbed thinking: "Spending time on internet telling people I know nothing about what they should do was totally worth it".

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

#308

Post by cycomanic »

aDfbrtVt wrote: post #245
cycomanic wrote: post #237

Earlier quoted context omitted.

The only use case I can think where matlab beats Python or Julia is when one has a lot of legacy code. It's funny that you mention documentation, the amount of documentation found around Python is typically much better than matlab. Matlab toolboxes are really hit and miss, some are very good, but there are some really crappy ones. If you actually need to include more traditional programming features matlab becomes a…

I would not wish Matlab GUI programming on my worst enemy. I disagree with your assertion that documentation for Python is typically much better. Take a randomly chosen function I regularly use: "pwelch" https://docs.scipy.org/doc/scipy/reference/generated/scipy.s... https://www.mathworks.com/help/signal/ref/pwelch.html Maybe my bias is showing, but I find the Matlab documentation to be superior. However, that is not…

Funny I'm in optical comms as well, chances are we know each other. I never used "pwelch" though. But I concur my statement on documentation was too strong, I guess it depends quite a bit.

Regarding IDE, I guess we tend to put priorities on different things. I find pycharm's (pro edition) git Integration, debugging, refactoring and profiling vastly superior. I plot using regular qt windows and I agree that for interactive plots where one wants to look at points etc, matlab has the edge, for publication ready plots matplotlib beats matlab hands down though (although the API is quite verbose, proplotlib is a wrapper that makes things more convenient IMO).

Anyway I think we have different priorities in what we are looking for. We use Python for labautomation and the matlab instrumentation toolbox is a buggy mess, our measurement times decreased by a factor of 5-10 when we switched from matlab.

Regarding cost, we are a university so matlab and python have equal costs. I do know of colleagues at industry labs where matlab cost was a factor though.

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

#309

Post by WuxiFingerHold »

jmyeet wrote: 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…

> 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.

I just discontinued my Jetbrains subscription after 10 years or so. Now I'm using VS Code and don't miss anything. My reasons for switching to VS Code are unrelated to the costs but purely due to quality issues and missing or poorly implemented features:

1. For all Jetbrains IDEs, ISO keyboard layout with dead keys doesn't work on Ubuntu based distros. I was baffled when I found out after saying goodbye to Windows lately. When filing a bug I was asked to wade through years old pages of comments to find somewhere someone who posted a workaround that was not compatible with the Toolbox. Well, at least the support could have sent me the instructions to fix it to save me spending an hour to read those threads at Youtrack.

2. Vue 3 support was a disaster for itself. Still, Vue 3 support is very much behind the VS Code extension.

3. Same for Svelte. They are not even working on bugs / feature requests like intellisense in the templates.

4. Same for TailwindCSS. Never ending storing. Don't know and care if Jetbrains got it right by now.

5. Starting maybe 2 years ago, Jetbrains added feature for feature that were just distracting and annoying. This "run command in terminal" thingie for example. They're bloating their IDEs with new (mostly useless stuff) but don't fix essential bugs or get Webstorm back into shape.

6. Datagrip still doesn't (or maybe it does in the meantime) support SQLite STRICT TABLES (version 3.37). The simple answer from Jetbrains was: "The open source lib we're using does not support it so we don't." (Actually the lib (https://github.com/xerial/sqlite-jdbc) is currently unmaintained - another reason to be careful depending on a lib maintained by a single person.). The reply would be perfectly fine for an open source project, but not for a multi billion dollar company I as a customer had payed accumulated several thousand Euros in the last years.

I'm using mainly Go, Rust and several frontend frameworks. VS Code support for those is really good. Many things work much better in VS Code.

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

#310

Post by 0des »

dschuessler wrote: post #292
misnome wrote: post #45

Earlier quoted context omitted.

I have been using GitLens for years, and didn't even know they had a paid version. Where have they been "Nagging" that I've just never seen?

Right next to your terminal should be a tab called "Gitlens: Visual File History". I do not want to argue whether its contents qualify as nagging but it might be what OP is referring to.

See now im in this predicament where I like paying for things so people don't starve, but the thing they're charging for is something I don't care about or use. Now I'm in this weird spot where I like the tool and would like to use it, but I feel like I'm freeloading when I could be paying, but I don't want the part that costs money, so I just uninstall.
Post reply on HN