3 ms·
I'd suggest you should download every plugin for ST and see how bloated it becomes, you'd end up with something as slow and ungainly as Eclipse. To me, one of
by beefsack 13y ago
I'd suggest you should download every plugin for ST and see how bloated it becomes, you'd end up with something as slow and ungainly as Eclipse.
To me, one of the largest benefits of ST is having a very powerful editor which is fast, simple, and very usable, and wouldn't want to see the core become much heavier than it already is (although I'm loving the code navigation functionality coming in ST3).
- derefr 13y agoOh, I'm certain that having all the plugins running code in the background at once would be a horrible experience (in much the same way that "installing every browser extension" would be a horrible experience.) I'm thinking mostly of plugins (packages, really) that just add code you can call through the command system--they don't do anything or consume any resources unless you prompt them to, so why shouldn't they be shipped with the runtime? But on the other case--what sort of Sublime plugins do you use that constantly run in the background doing something? I don't use any myself that do anything like that; what are some good examples?
- nobleach 13y agoI have loaded a TON of plugins at one point. It was nowhere near Eclipse's "oh, you wanted to keep typing? No, sorry I'm going to block while the JVM does a GC sweep, and I try and figure out what auto-completion to show you". With everything I had loaded in Sublime, it just took a couple of seconds longer to start up. Which plugins were you loading specifically?
- winter_blue 13y ago> No, sorry I'm going to block while the JVM does a GC sweep, and I try and figure out what auto-completion to show you". I've experienced this quite often, mainly on large code bases.