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

321–330 of 343 posts

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

#321

Post by misnome »

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.

Oh, I never use the built-in terminal, and obviously never noticed or clicked on the extra heading (which seems easily hidden with right click).

This also doesn't seem to come under "nagging" for me. To me, that'd be something like, a popup while using or trying to click through a commit reference (which would almost certainly earn it an instant uninstall).

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

#322

Post by mbesto »

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…

> In my opinion those should be provided because developers should strive to develop good products.

Developers also have to put food on the table. I think you've now answered your "is this hard to do?"...

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

#323

Post by 7steps2much »

mbesto wrote: post #322
7steps2much wrote: post #265

Earlier quoted context omitted.

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…

> In my opinion those should be provided because developers should strive to develop good products. Developers also have to put food on the table. I think you've now answered your "is this hard to do?"...

> I think you've now answered your "is this hard to do?"...

Did i buy the product "as is"? If it is an open source product then i agree with you, the product is provided as is. However, in my mind this is not the case with a commerical products.

When I buy something, whether it is software, a car or a a washing machine i have a contract that outlines what i am buying. If the product contains bugs/manufacturing defects/etc. then i expect the manufacturer to either fix those or refund me. In many countries this might even be legally required (Look for Gewährleistung/Produkthaftung in German speaking countries).

I am not asking for features. I am not asking you to make the product better than what I bought. I discovered a defect that was caused by the manufacturer, not obvious at the time of purchase and as such the product does not match what i ordered from the manufacturer. I am asking you to provide to me exactly on what we agreed upon in our contract. If a developer cannot handle that and wants to distribute their software "as is" that's fine, but that will result in my willingness to pay being lower.

If I buy a product I expect that product to perform as was promised. If it does not and the manufacturer refuses to work with me then it's a breach or contract.

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

#324

Post by belltaco »

wiseowise wrote: post #315
belltaco wrote: post #297

Earlier quoted context omitted.

It's a bit like saying 'let them fly on private jets' and someone pointing out that only a few people in the population can afford it. Doesn't imply that private jets are useless, just that their use is limited.

Do you have access to private jet? Because everyone has access to, for instance, Atom source code. Even if they can't use it.

Everyone has access to private jets, even if they can't afford them.

https://www.avbuyer.com/aircraft/private-jets

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

#325

Post by bmitc »

creatonez wrote: post #299
bmitc wrote: post #201

Earlier quoted context omitted.

Features also come but not to Vim.

They absolutely do. See coc.vim which is a compatibility shim that lets you run a huge number of VS Code extensions in vim with minimal modifications. Also see Neovim which is a vim fork that has very good builtin language-server support.

I didn't mean no features come to Vim.

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

#326

Post by antifa »

nojito wrote: post #60
blip54321 wrote: post #33

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…

Nothing to do with freedom. People are naturally cheap. Which is why free tiers are so popular.

I'm not rich and a lot of paid tiers are targeting 5+ seat enterprise companies instead of individuals.

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

#327

Post by antifa »

digisign wrote: post #281
no_circuit wrote: post #175

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?

The company that doesn't wash it's hands, has it's pants down, is regularly stuffing it's mouth with stolen cookies, doesn't even bother to take it's hand out of the jar when responding to allegations, but also for some reason has numerous shills claiming has done nothing wrong.

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

#328

Post by nybble41 »

mckravchyk wrote: post #113
tharne wrote: post #107

Earlier quoted context omitted.

> Most of your points also apply to open source software, and aren't strict requirements for proprietary software. Except I can still use discontinued open source software like Atom. Try installing an older version of an app on an old iPhone. The app store won't let you. You might be able to jailbreak the phone and track down an older version of the app, but it's a pain and Apple makes it as difficult as they can for…

> Except I can still use discontinued open source software like Atom. The same thing can be said about desktop proprietary software, so long as it does not rely on a cloud service to function. > Try installing an older version of an app on an old iPhone. The app store won't let you. You might be able to jailbreak the phone and track down an older version of the app, but it's a pain and Apple makes it as difficult as…

> That said, open source have this edge that if it's just too obsolete for the dependencies, you can hope someone would patch it if it's popular enough. It would be harder to patch a proprietary app.

IMHO this understates the difference, severely. The open source app can be maintained by the community for as long as it has a community. That includes not just dealing with dependency obsolescence but also new features, redesign, porting to new platforms… anything that would have been handled by the original team.

The proprietary app, on the other hand, will be near-impossible to patch for even the most trivial of changes without the original source code or build environment—and let's not forget that distributing the modified version would be illegal; at best you might get instructions for patching your own copy. And of course there won't be any growth in the user community since there is no (legal) source for new copies. Existing users may be able to struggle along on their own for a while but this is ultimately a dead end without support from the copyright holder.

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

#329

Post by mbesto »

7steps2much wrote: post #323
mbesto wrote: post #322

Earlier quoted context omitted.

> In my opinion those should be provided because developers should strive to develop good products. Developers also have to put food on the table. I think you've now answered your "is this hard to do?"...

> I think you've now answered your "is this hard to do?"... Did i buy the product "as is"? If it is an open source product then i agree with you, the product is provided as is. However, in my mind this is not the case with a commerical products. When I buy something, whether it is software, a car or a a washing machine i have a contract that outlines what i am buying. If the product contains bugs/manufacturing defect…

> If the product contains bugs/manufacturing defects/etc. then i expect the manufacturer to either fix those or refund me.

This analogy doesn't work with software. If you put your fridge in your house and your power goes out, you can very clearly see that your fridge is inoperable because of your power, not the fridge. Now let's try this with software:

- The software you buy supports Linux v16 but not v18. You upgrade to v18 not knowing and not your software is broken. But the software was sold to you to support v16 and not v18.

- The software you buy supports API connections to Twilio. In the docs it says "easy to use extensible API for all SMS providers". Twilio discontinues its v1 API endpoint but your software only supports v1 and not v2. You decide to migrate to Plivo and everything works except for one API call that is used once every 3 months.

And on and on and on...see the point?

> I am asking you to provide to me exactly on what we agreed upon in our contract.

Great, now the developer not only has to be a "good developer" but also an expert in contract writing (or has a lawyer that is). Or worse, the lawyer and developer must be completely and harmoniously in sync about product functionality and the contractually nature that you, the client, originally decided to sign the contract with. Note - In case you are unaware, software contracts are notoriously difficult to do well (see Google/Oracle debacle).

> If I buy a product I expect that product to perform as was promised. If it does not and the manufacturer refuses to work with me then it's a breach or contract.

I think you're going to find the more and more you explain your position the more and more you'll see that "why is this so hard" is truly...hard.

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

#330

Post by hamdouni »

indrora wrote: post #225
devwastaken wrote: post #216

Earlier quoted context omitted.

Paying for software does not have a relationship with quality. Imagine if GCC had a "pro" version that was necessary to compile certain code. That would be devastating to those learning and thousands of devs that came before would be spinning in their graves. The reason we do open source and free software is to make life easier for everyone, including your job. It standardizes practices and prevents mudball codebases…

Calling GCC a "good" compiler is going a bit far, imo. LLVM has become the dominant compiler framework (and thus clang, clang++, golang, etc use it) because of corporate interests. GCC as it's constructed is a horrible framework. The way you port GCC to a new platform (say, a weird ARM variant) is to fork it hard and mangle multiple parts of the internals , then carefully feed it back. It's a mess. Nobody should be f…

Are you sure golang use LLVM ? I'm pretty sure it is not the case...
Post reply on HN