zlacker

I use a mix of sublime and vscode. I often pick sublime, because I want peace of mind. I trust it to not try to make me 'do something else'. It (mostly) doesn't pester me with things to update or that are out-of-date, it doesn't run or fail with weird things in the background I didn't ask it to do. It sticks to a minimal layout. I had a similar love relationship with early versions of paintshop-pro - it contained the right balance of 'enough to do what you need, but not too much to overwhelm you'. Whenever I ran into a too-new version of paintshop-pro, I closed it again because I didn't want to deal with their lost-sense-of-balance. Sublime for me is like that, it is a hammer where the head won't suddenly fall off.

I had an eye-opening experience with VSCode recently: I had brought one of my laptops on a car drive, where I had a few hours before the people (family) I chauffeured would come back, and I had a coding project I wanted to update some stuff on. The kicker: I didn't have internet in the car, but for local vscode editing, that shouldn't be a problem, right(?) At least, I had not thought it would be.

Well, for some reason, VSCode suddenly became stupid. It could not longer figure out where my methods and classes were defined, so I had to navigate my code-base by hand (god forbid). It also flashed something about not being able to connect to "dot net" / ".NET" or something similar. I am not quite sure what was going on, maybe copilot..? Whatever, my VSCode was in a mode where it seemed to rely on some online resource to operate, and suddenly had become braindead by severing the cord..??

This reminds me why I like sublime.