3 ms·
Opening a newly cloned Chromium repository in ~3s is very impressive to be honest.
by plexicle 10y ago
Opening a newly cloned Chromium repository in ~3s is very impressive to be honest.
- sunnyps 10y agoStill not impressed. I just tried it with Chrome and it's way slower than Sublime Text to be useful for me even when excluding large parts of the checkout. Also enabling the C++ extension made my computer hang, I couldn't spawn new shells or even login in a tty. I really want to be able to use it for my work but I can't unless it's about as fast as Sublime Text.
- JonnieCache 10y agoI was about to try one of these fancy new browser based editors again, but now I'm confused. Shouldn't opening a directory be O(1)? I just opened the chromium trunk in sublime and it took 0.2 seconds, regardless of whether it was currently running or not. Why would one ever use a text editor that has perceptible latency when doing everyday tasks? 3 seconds isn't even latency, it's a freeze tbh.
- sunnyps 10y agoI don't think being "browser based" as the reason that opening a directory is slow. A lot of traditional IDEs (cough Visual Studio cough) also have similar problems. I think they're doing a bunch of work (e.g. caching all subdirectories and files) but aren't doing it concurrently with the UI.
- deleted 10y ago[deleted]
- mxvzr 10y agoI feel we are comparing apple to oranges here: sublime (a text editor) will simply list files & directories in the top level folder when you add a folder to the projects while an IDE (thinking mostly of Eclipse here, but I assume other IDEs aren't that different) will parse every single file to build ASTs, symbol lookup tables and all these things that you either love or cannot stand.
- sunnyps 10y agoVS Code (a "smart" text editor not to be confused with Visual Studio an IDE) doesn't parse C++ code (which is what Chromium consists off) in the default configuration. And even if you have the C++ extension enabled it doesn't parse any code until later.
- deleted 10y ago[deleted]
- wbond 10y agoWith ST3 we scan and index symbols in each file contained in folders that have been opened. This powers our project-wide Goto Symbol functionality and the Symbol Definition popup.