4 ms·

I tried VSCode for few months and decided to stay with sublime text 3 (infite paid license) Why ? Because every 3.rd time i opened some project and wanted to do

I tried VSCode for few months and decided to stay with sublime text 3 (infite paid license) Why ? Because every 3.rd time i opened some project and wanted to do WORK there was gazillion notifications and updates. I don't care. You do develmopment of your product alot, I don't care. I want to update my toolset when I have time, that's 1 or 0.5 per year.

eloisius 3y ago
Number 1 reason I stick with my tools, no matter how good $current_thing is: bash, tmux, and nvim. Nothing ever changes.
vdfs 3y ago
Funny how the "What's new" message in Sublime products is what hate most about them, to the point of disabling updates all together for them, they also have plugins with their own "What's new" messages. I guess there is always someone who will abuse this
smcleod 3y ago
It's interesting to hear how different people like to operate. In general for me personally I like to ensure all software updates are installed daily (not just my editor/IDE). When I login in the mornings the first thing that runs is a simple script that checks for and applies all updates for my OS, Apps, homebrew packages, shell packages, several applications extensions / plugins etc... likewise my servers install updates daily. Obviously there are pros and cons of (in)frequently updating software. For me - with this approach of small, frequent updates I've found that updating software becomes boring - which is a good thing. I honestly can't remember the last time anything broke (that I noticed). I've taken this approach for around 12 years.
- jabroni_salad 3y ago
  I don't mind having stuff update, I just don't like anything that steals focus / the cursor. When I am in windowsland I often find myself saying something along the lines of 'let me know when its my turn to use the computer'. Sure, run your update. just shut the fuck up about it.
  - deleted 3y ago
    [deleted]
- bityard 3y ago
  I used to do this, until I ran into the problem of an update breaking some critical piece of my workflow the morning right before I had some important work to complete. It's not a good look when you have to ask your co-workers to wait for you because you have to stop and fix your computer first. (Although these days software is so unreliable that maybe no one bats an eye anymore? Who knows.) Since then, I've learned that it's not a matter of IF an upgrade will break your system, it's a matter of WHEN. There will always be that one bug that slips under the radar and breaks something, and it's usually right when you can afford it the least. These days, I do approximately weekly upgrades of all my systems/gear, but I make sure to schedule it when I know I will have the time to fix whatever issues come up. (In an enterprise setting, the expanded version of this is called Change Management.)
- ar_lan 3y ago
  I prefer stability over optimal, especially in my development environment. I use macOS with nix-darwin, so updating my applications is never very concerning - I can always just rollback if an update is bad. But macOS updates, while generally they don't break anything, have broken enough that it's the scariest part of my year. The year they shut down any folders in the `/` directory was my (and many coworkers) downfall. It took me a solid 3-4 hours to recoup everything in a working order, and there were failing straggler scripts that were discovered months later. As such I generally avoid updates as often as possible. Also, to be fair, I have a history in IT and while personal computer updates are generally good, infrastructure updates are time-consuming, error-prone, and generally scary, so I do have a default aversion.
- User23 3y ago
  Next morning's standup: "And then I got nothing done for the rest of the day while I fixed my development environment that was messed up by an update."
- JohnFen 3y ago
  > For me - with this approach of small, frequent updates I've found that updating software becomes boring - which is a good thing. That's all well and good until an update happens that changes workflow or changes the look/feel too much. Those sorts of changes cause disruption that I want to schedule. Or until an update is made that changes the software in a way that makes it actively worse for your use case. Those are the sorts of updates I want to avoid. That's why I don't allow software to automatically update. Most of the time I won't notice the update, but when I do, it's a big deal that would have been better if I could have done it on a more convenient day.
gliptic 3y ago
Somehow the most annoying thing to me is this long-standing bug where "Exit" doesn't mean "Exit", but "Exit, unless there's updates, then restart".
- bityard 3y ago
  I install VSCode from the apt repo, so it doesn't update for me unless I update the rest of my system. (Or I can choose to update everything else in VSCode if I know there's a problem with the current version.)
- Hamuko 3y ago
  That seems like a very typical Microsoft bug. I wanted to shut down my gaming PC the other week, so I selected "Update and shut down". Then I switched my monitors to my other computer. 10 minutes later I was wondering why the PC was still humming along. Switched the monitors back to it and saw my Windows 11 installation sitting patiently in the login screen.
EnragedParrot 3y ago
I never receive intrusive notifications from VSCode. It quickly and silently updates every once in a while when I close the program. I'm not sure what kinds of malicious extensions you must've had installed.
- elboru 3y ago
  > It quickly and silently updates What about the “What’s new tab” that opens right when you want to have some work done? Or the notifications you get at the bottom-right corner suggesting to install extensions when you just want to see inside a file. I mean, many people don’t care that much, it’s just a little annoyance to me, as little to not spent 5 mins to find a solution.
  - Jcowell 3y ago
    love those, let me know if a new feature is available and how to better vote a new home type and if I don’t care? instant close. No nagging of “are you sure” just straight and to the point.
    - JoBrad 3y ago
      That's my view, too. At one point I set all of my extensions to manual updates only. But that became cumbersome when I started enabling extensions by workspace, so I just use auto-update now. I appreciate the "what's new" notes, especially when I learn about new features. Edited for clarity
  - EnragedParrot 3y ago
    The "What's New" tab only opens when I don't open Code into a project directory, usually it opens right into the last file I was working on. The extensions notifications I suppose could be an annoyance, but I seldomly encounter new file types, so it's a non-issue for me and I suspect most users.
  - webstrand 3y ago
    Sublime text has this too, except it's a popup. And Package Control, too, has a tab that pops open a few seconds after you've started writing. In my opinion they're not really a problem.
kriz9 3y ago
You can install the portable version of VSCode and you don't have to deal with this anymore - then you can update whenever you need to.
rockostrich 3y ago
Well, the nice thing about VSCode is you can disable all of that... Some people are working with toolsets that benefit from constant updates.
cantSpellSober 3y ago
Funny, I switched from ST in part because of the popup that an upgrade is available. You could have just configured VS Code instead of completely changing editors. In fact, you're commenting on a post with a really fine-grained list of how to! Do you ever configure ST?
- toastercat 3y ago
  Funny, you could have just configured ST to disable the update check instead of completely changing editors. Add `"update_check": false` to your preferences.
  - cantSpellSober 3y ago
    > Do you ever configure ST? Agreed, both editors require configs to turn this off. ST is updated so rarely at least it was less annoying.

eloisius 3y ago

Number 1 reason I stick with my tools, no matter how good $current_thing is: bash, tmux, and nvim. Nothing ever changes.

vdfs 3y ago

Funny how the "What's new" message in Sublime products is what hate most about them, to the point of disabling updates all together for them, they also have plugins with their own "What's new" messages. I guess there is always someone who will abuse this

smcleod 3y ago

It's interesting to hear how different people like to operate. In general for me personally I like to ensure all software updates are installed daily (not just my editor/IDE). When I login in the mornings the first thing that runs is a simple script that checks for and applies all updates for my OS, Apps, homebrew packages, shell packages, several applications extensions / plugins etc... likewise my servers install updates daily. Obviously there are pros and cons of (in)frequently updating software. For me - with this approach of small, frequent updates I've found that updating software becomes boring - which is a good thing. I honestly can't remember the last time anything broke (that I noticed). I've taken this approach for around 12 years.

jabroni_salad 3y ago
I don't mind having stuff update, I just don't like anything that steals focus / the cursor. When I am in windowsland I often find myself saying something along the lines of 'let me know when its my turn to use the computer'. Sure, run your update. just shut the fuck up about it.
- deleted 3y ago
  [deleted]
bityard 3y ago
I used to do this, until I ran into the problem of an update breaking some critical piece of my workflow the morning right before I had some important work to complete. It's not a good look when you have to ask your co-workers to wait for you because you have to stop and fix your computer first. (Although these days software is so unreliable that maybe no one bats an eye anymore? Who knows.) Since then, I've learned that it's not a matter of IF an upgrade will break your system, it's a matter of WHEN. There will always be that one bug that slips under the radar and breaks something, and it's usually right when you can afford it the least. These days, I do approximately weekly upgrades of all my systems/gear, but I make sure to schedule it when I know I will have the time to fix whatever issues come up. (In an enterprise setting, the expanded version of this is called Change Management.)
ar_lan 3y ago
I prefer stability over optimal, especially in my development environment. I use macOS with nix-darwin, so updating my applications is never very concerning - I can always just rollback if an update is bad. But macOS updates, while generally they don't break anything, have broken enough that it's the scariest part of my year. The year they shut down any folders in the `/` directory was my (and many coworkers) downfall. It took me a solid 3-4 hours to recoup everything in a working order, and there were failing straggler scripts that were discovered months later. As such I generally avoid updates as often as possible. Also, to be fair, I have a history in IT and while personal computer updates are generally good, infrastructure updates are time-consuming, error-prone, and generally scary, so I do have a default aversion.
User23 3y ago
Next morning's standup: "And then I got nothing done for the rest of the day while I fixed my development environment that was messed up by an update."
JohnFen 3y ago
> For me - with this approach of small, frequent updates I've found that updating software becomes boring - which is a good thing. That's all well and good until an update happens that changes workflow or changes the look/feel too much. Those sorts of changes cause disruption that I want to schedule. Or until an update is made that changes the software in a way that makes it actively worse for your use case. Those are the sorts of updates I want to avoid. That's why I don't allow software to automatically update. Most of the time I won't notice the update, but when I do, it's a big deal that would have been better if I could have done it on a more convenient day.

gliptic 3y ago

Somehow the most annoying thing to me is this long-standing bug where "Exit" doesn't mean "Exit", but "Exit, unless there's updates, then restart".

bityard 3y ago
I install VSCode from the apt repo, so it doesn't update for me unless I update the rest of my system. (Or I can choose to update everything else in VSCode if I know there's a problem with the current version.)
Hamuko 3y ago
That seems like a very typical Microsoft bug. I wanted to shut down my gaming PC the other week, so I selected "Update and shut down". Then I switched my monitors to my other computer. 10 minutes later I was wondering why the PC was still humming along. Switched the monitors back to it and saw my Windows 11 installation sitting patiently in the login screen.

EnragedParrot 3y ago

I never receive intrusive notifications from VSCode. It quickly and silently updates every once in a while when I close the program. I'm not sure what kinds of malicious extensions you must've had installed.

elboru 3y ago
> It quickly and silently updates What about the “What’s new tab” that opens right when you want to have some work done? Or the notifications you get at the bottom-right corner suggesting to install extensions when you just want to see inside a file. I mean, many people don’t care that much, it’s just a little annoyance to me, as little to not spent 5 mins to find a solution.
- Jcowell 3y ago
  love those, let me know if a new feature is available and how to better vote a new home type and if I don’t care? instant close. No nagging of “are you sure” just straight and to the point.
  - JoBrad 3y ago
    That's my view, too. At one point I set all of my extensions to manual updates only. But that became cumbersome when I started enabling extensions by workspace, so I just use auto-update now. I appreciate the "what's new" notes, especially when I learn about new features. Edited for clarity
- EnragedParrot 3y ago
  The "What's New" tab only opens when I don't open Code into a project directory, usually it opens right into the last file I was working on. The extensions notifications I suppose could be an annoyance, but I seldomly encounter new file types, so it's a non-issue for me and I suspect most users.
- webstrand 3y ago
  Sublime text has this too, except it's a popup. And Package Control, too, has a tab that pops open a few seconds after you've started writing. In my opinion they're not really a problem.

kriz9 3y ago

You can install the portable version of VSCode and you don't have to deal with this anymore - then you can update whenever you need to.

rockostrich 3y ago

Well, the nice thing about VSCode is you can disable all of that... Some people are working with toolsets that benefit from constant updates.

cantSpellSober 3y ago

Funny, I switched from ST in part because of the popup that an upgrade is available. You could have just configured VS Code instead of completely changing editors. In fact, you're commenting on a post with a really fine-grained list of how to! Do you ever configure ST?

toastercat 3y ago
Funny, you could have just configured ST to disable the update check instead of completely changing editors. Add `"update_check": false` to your preferences.
- cantSpellSober 3y ago
  > Do you ever configure ST? Agreed, both editors require configs to turn this off. ST is updated so rarely at least it was less annoying.