Thread by @mcclure111

So… this is odd.
Sublime Text did an update.
Now it is running like mud and pegging the CPU at 100%.
I eventually realized it was doing this "indexing" task.
Indexing… what?
I think it might be doing some parsing operation on multi-megabyte webpack-generated js files D: D: D:

Also the dock icon updated and now it follows the new Mac OS HI standards, which suck :/ They made every icon a rounded rectangle and now I can't distinguish them by shape anymore

It is SUCH an awful feeling trying to type on a MacBook which is overheating. The keys are made of lava

I didn't even mean to upgrade… it was one of those things where I click and then afterward discover a dialog box was opening under my cursor just as I was clicking :/

Oh.
Uh
…Uhhm
Okay.
Well, in addition to the new upgrade killing perf and/or pegging my CPU,
it also downgraded me to the shareware-unregistered version. forum.sublimetext.com/t/after-recent…
Apparently Sublime Text's "upgrade" box now invalidates your license and doesn't tell you until after

This is pretty annoying! Maybe there are some apps I wouldn't mind "oh, that update didn't work so well for me, I guess I have to re-download the old version" but this is… my … text editor? I'd expect my text editor to not just nuke itself. I'd expect that's high-availability

Anyway. Let's recap
1. Sublime Text has an update box open for you right now you've been ignoring.
2. If you agree to it, two things will happen. All your indexes will fry (because 3->4 update) and your CPU will peg until they're done, and two, AFTER upgrade, it will demand $99

So, uh, I guess, avoid clicking that upgrade button unless you are willing to pay $99 and also leave your computer "re-indexing" overnight

So Sublime Text 4 is a bit of a disaster. In addition to costing $99 (but not telling you this until *after* the upgrade) "New View Into File" is now gone and replaced with a "Split View" which (1) is not what I want & (2) is frankly buggy & interacts poorly with existing plugins

For example, one odd thing about the "Split View" which has replaced New View Into File is that if you close one of the views, it asks if you want to save before closing. But of course I'm not closing it, I'm just reverting from split view back to normal view?

Another vague frustration in ST4 is a new "Intellisense" like feature; if I wanted "Intellisense" I'd be using VSCode. In my experience these features mainly serve to interrupt my flow by causing the editor to briefly hang. ST4's does this & its suggestions don't even make sense

If you'll look, in this case, it's bringing up the intellisense/autocomplete when I typed a }, producing a syntactically complete TypeScript line. Its suggestions are…seemingly every symbol that exists in the file?, none of which would be syntactically allowed at cursor position

Maybe the split view*, and whatever the new autocomplete behavior is, are just a sign that this is a "version 1.0" for ST4 and some bugs need ironing out. But if that's the case maybe they should have beta'd longer…? I don't know.

( * Personally I literally never want horizontal split view because code lines are long and horizontal split cuts them in half. I still miss XCode 3, which is the only editor I've ever seen to have a quick-access vertical-split feature. Maybe ST4 can be configured like this? )

Anyway I'd have already switched back to 3 already but after the "indexing…" sandbagging the 3->4 switch gave me, I'm afraid switching back to 3 will result in another multi-hour re-index. ( ST4 for some reason stores its config files in ~/Application Support/Sublime Text 3 )

UPDATE: Setting down my laptop for an hour or two in the middle of a workday to let the "indexing" operation complete after downgrading from ST4 to ST3 because ST4, totally inexplicably, locks up the computer for about a second every time I alt tab in or out(?)