Re:Sublime Text 3.2 Released
by rygxqpbsngav on Wednesday March 13, 2019 @07:36AM
(#19377689)
Tried it once or twice. But using VS Code (with Git lens extension) predominantly these days. Couldn't find anything VS Code can't do that Sublime can.
[ Parent
| on HN ]
Sublime doesn't take half a minute to start in a non-ssd hard disk.
Sublime feels more lightweight and doesn't have as much lag when typing as VS Code.
Not to mention the battery drain of VS/Atom
That's definitely a big one for me. Sublime barely uses any battery, but VS Code gobbles it.
VS Code can't handle very large files (multi-GiB), but Sublime can.
Does anybody know of a decent benchmark on editor latency? I swear Sublime feels more responsive vs VS code but that could just be in my head.
There is a great benchmark somewhere on Github, it measures 5-ish metrics, like key->rendered latency, time to load 100MB file, and stuff like that.
Apparently, the Joe editor was the fastest, and Sublime has basically first or second place for most metrics.
Atom crashed for a few metrics :P
I don't know if I could find it for you... but it's out there somewhere, maybe someone here has it bookmarked.
https://github.com/jhallen/joes-sandbox/blob/master/editor-p...
This is probably what you're looking for.
For pure typing latency, here's a fairly rigorous one from three years ago: https://pavelfatin.com/typing-with-pleasure/
It doesn't include VS Code, but it does describe the benchmarking process and the provided tool is simple to use.
On my current setup, VS Code 1.32.1 is ~5ms slower than Sublime Text 3.2: 16.2ms vs 10.8ms respectively.
Re:Sublime Text 3.2 Released
by guessmyname on Wednesday March 13, 2019 @02:20PM
(#19381738)
There's one from 2017, but it's probably not too accurate for things like VSCode anymore. https://news.ycombinator.com/item?id=13933128
Is that all? I can swear I'll never encounter such a huge text file as a programmer.
There are other ways to interact with those than open up in an editor.
As someone else’s anecdote, I have. Log files can easily grow, database exports as well.
I use sublime as a text editor for such files, but other IDEs (in my case webstorm) for everything editing project code
Either you should split the files when exporting (split database schema from data and for each table or by date etc for logs) or grep to filter out than open up GB size in an editor as you'll have problem navigating anyway. You don't want to use 'find' inside the editor for that kind of size.
Or you can use Sublime, where it's not an issue. Find works just fine on large files.
Re:Sublime Text 3.2 Released
by kristofferR on Wednesday March 13, 2019 @09:24AM
(#19378327)
Multiple windows... VS Code is still abhorrent on multi-display setups.