3 ms·

It’s a real problem. GitLens[0] comes to mind, which used to be a decent free extension, but now gives me flashbacks to the shareware nag screens of old. I’m a

It’s a real problem. GitLens[0] comes to mind, which used to be a decent free extension, but now gives me flashbacks to the shareware nag screens of old. I’m also not against selling software on principle. Downgrading a free piece of software into a demo with an auto-update feels shady, however. [0] https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens https://marketplace.visualstudio.com/items?itemName=eamodio....

NikolaNovak 4y ago
can you elaborate? "I made something people seem to like, hopefully it can help feed my family" sounds more like a wonderful success story rather than shady (depending on target audience of course but that's the part I'd like to understand better rather than make assumptions)
misnome 4y ago
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?
- dschuessler 4y ago
  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.
  - 0des 4y ago
    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.
  - misnome 4y ago
    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).
brianzelip 4y ago
Flashbacks? > Does this affect existing features? > > No, the introduction of GitLens+ has no impact on existing GitLens features, so you won't lose access to any of the GitLens features you know and love. In fact, we are heavily investing in enhancing and expanding the GitLens feature set. Creating an account simply gives you access to a subset of new features that will enable you to get even more out of Git in VS Code! I haven’t used it and only heard of it last week, but the extension’s page you linked to seems decent enough for me to try it out.
- codeflo 4y ago
  I’m sure the thing you quoted is technically true, the existing features are still there somewhere. But it’s not a great experience if some of the most prominent buttons in the VS Code UI now open the GitKraken account page. YMMV; I personally found this very “in your face” and unusable.
brnt 4y ago
Intrseting that the Gitlens code repo is under the gitkraken org. Guess they took them over?

NikolaNovak 4y ago

can you elaborate? "I made something people seem to like, hopefully it can help feed my family" sounds more like a wonderful success story rather than shady (depending on target audience of course but that's the part I'd like to understand better rather than make assumptions)

misnome 4y ago

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?

dschuessler 4y ago
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.
- 0des 4y ago
  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.
- misnome 4y ago
  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).

brianzelip 4y ago

Flashbacks? > Does this affect existing features? > > No, the introduction of GitLens+ has no impact on existing GitLens features, so you won't lose access to any of the GitLens features you know and love. In fact, we are heavily investing in enhancing and expanding the GitLens feature set. Creating an account simply gives you access to a subset of new features that will enable you to get even more out of Git in VS Code! I haven’t used it and only heard of it last week, but the extension’s page you linked to seems decent enough for me to try it out.

codeflo 4y ago
I’m sure the thing you quoted is technically true, the existing features are still there somewhere. But it’s not a great experience if some of the most prominent buttons in the VS Code UI now open the GitKraken account page. YMMV; I personally found this very “in your face” and unusable.

brnt 4y ago

Intrseting that the Gitlens code repo is under the gitkraken org. Guess they took them over?