6 ms·
Congrats to the team for reaching this important milestone. I'm a Sublime license holder, but I use Atom as much as I can, because the more open source can win
by bdcravens 11y ago
Congrats to the team for reaching this important milestone.
I'm a Sublime license holder, but I use Atom as much as I can, because the more open source can win, the better.
However, yesterday I was doing some complex regex's (porting a random sql dump file into a seeds.rb), and Atom kept dying, whereas Sublime was pretty much instantaneous.
I'm not doing the usual "Atom is slow" drum beating, but saying some undertones of the announcement make me worry a bit. I hear discussion of things like Electron and "social coding" as the future, and I'm hoping that means that no one considers 1.0 to equate to the core editing experience being finished. It's not, and I hope the Atom team continues to iterate before moving on to new features.
Being able to open files larger than 2MB isn't sexy, but it's necessary. Having to hard-kill my editor because the save dialog is trapped on my other full screen session that it won't let me get to deserves more than a "but it's open source" response.
tl;dr congrats team and your core users want the best editor possible over bells and whistles
- arikrak 11y agoI know it's off-topic, but is regex the best way to convert SQL into seeds.rb? I'm thinking of doing the same thing, but I figured I'd use Ruby or a gem. https://github.com/rroblak/seed_dump https://github.com/rroblak/seed_dump
- bdcravens 11y agoThis was a data dump from a previous development effort, and the Rails app was no longer connected to that database. Moreover, it was MySQL, not Postgresql, the new target. I probably could have stood up MySQL and used that gem to achieve the same result, but honestly, while the regex is at times a bit complex, it's straight-forward, since an insert's parenthetical list of values is very close to what you pass to Model.create. Thanks for the gem recommendation though, and hopefully it'll be a better solution the next time I encounter a similar situation.
- elinchrome 11y ago"...now you have two problems" Seems off base to me too.
- chc 11y agoI just tried it on a 14MB file to confirm, and Atom can open files larger than 2MB. (I also scrolled through the whole file just to make sure Atom wasn't cheating somehow, and it seemed to be working fine.)
- dstaley 11y agoI can open a 15MB log file, but my CPU usage skyrockets.
- caffeineninja 11y agoYou're not trying to scale for millions of users. It's okay to let your CPU cook a bit.
- hamburglar 11y agoI just tried it on a 35MB log file and it gave me an alert that said it was gonna be sluggish, then took about 20s to actually open the file I requested (I could navigate to other tabs in the meantime but there was no indication that anything was happening), and then once the file appeared, it took another 20s to become responsive. Searching for a string which appeared in the second line of the file took over 30s, probably because it was searching the entire file to highlight all matches, and all the while, it was completely unresponsive. Then when I tried to close the file, the entire editor hung and eventually gave me a "this tab is not responding" dialog. I clicked "wait" and it took another 10s and the window finally closed. All in all I'd say the experience editing large files still completely sucks compared to every other editor I use. Don't get me wrong, I still love and use Atom, but they really need to come up with a solution to this problem, because it's just ridiculous. The fact that I have to occasionally leave my text editor to edit certain text files is a huge black eye that many people won't put up with, and which I will eventually get tired of putting up with if they don't do something about it soon. One thing I think they could do is take advantage of the fact that when you are editing a file that large, you don't expect to have a particularly good experience with the scrollbar. I don't open a file with 10 million lines and grab the scrollbar to get to the spot I'm looking for; it's just not practical. Over a certain size, they really don't need to have the entire buffer in memory at once, and maybe they don't even need a usable scrollbar so much as they need good relative navigation and search. It would be perfectly reasonable in my opinion to have a "large file mode" for the editor window that has subtly different behavior that makes it not so ridiculously heavy.
- 3pt14159 11y agolol, 2MB? I use emacs and hardly played with Atom. To me this sounds like you are complaining about a 20MB mp3 interfering with your audio player.
- bdcravens 11y agoYeah, it's a bit nuts. Sublime handles those files without batting an eye, and opens files that are hundreds of MB (and even multi-gig files) easily (it handles files that in the past I'd never open in a windowed text editor) I'm pretty sure it's a limitation of the underlying webkit, as loading a file that big in the browser is typically a bad use case.
- ossreality 11y agolol, I'd like to see Sublime opening a multi-GB file. It certainly can't handle more than 50 MB on Windows, and that was after waiting 30 minutes for it to load.
- Demiurge 11y agoI don't remember Winamp not able to play 20MB mp3, such a rip of entire album, since I started using it in 98.
- scintill76 11y agoI think that's the point of the comparison -- 20MB is really only the start of the heavier usecases people might want out of a music player, but an underdeveloped player might only be able to do, say, 2MB.
- pudquick 11y agoSorry for side-jacking this comment - but which version of Sublime, may I ask, and what OS? I'm using Sublime 2 on OS X and large files + regular expressions are generally a cause for pain. Do you have any default settings changed like disabled document preview or similar? The only thing I generally feel is a champ at regular expressions + insanely large files on OS X is TextWrangler/BBEdit. In fact, I keep TextWrangler around specifically for the large file excellence experience which I (currently) don't receive on Sublime Text 2.
- brianpgordon 11y agoUpgrading to Sublime 3 can't hurt... I don't have issues with large files on OS X.
- pudquick 11y agoIs the beta stable enough to use regularly?
- freditup 11y agoYes, I would say it is quite stable. In fact, in the ST blog it says: "Sublime Text 3, while still technically in beta, is the recommended version of Sublime Text to use." [0] [0]: http://www.sublimetext.com/blog/articles/sublime-text-3-build-3080 http://www.sublimetext.com/blog/articles/sublime-text-3-buil...
- pudquick 11y agoThanks :) I'll give it a whirl! EDIT: WOWOW Major difference! Definitely sticking with 3!! Thank you :D Extremely fast in comparison to 2.
- Demiurge 11y agoAtom crashed and froze on me numerous times during this day of 1.0 release. ST3 'beta' has never crashed or frozen on me since it's been out.
- espadrine 11y agoI agree wholeheartedly with the sentiment. However, as I understand it, the issue is not so much with raw size (although it does not help) as it is with long lines. For instance, the following 161K file freezes completely Atom, to the point that you just have to close it: https://github.com/espadrine/aulx/blob/master/html/tokenizer.js https://github.com/espadrine/aulx/blob/master/html/tokenizer... The reason is that the core syntax highlighter (https://atom.io/packages/language-javascript https://atom.io/packages/language-javascript) is heavily unoptimized, and tries precomputing data for the whole line without considering that only the first 0.5k characters will probably be seen. It is too bad, as this was already fixed globally in existing web text editors such as CodeMirror. Given that it is used in Chrome and Firefox' DevTools, and that JS minification happens on the Web, it had to.
- crucialfelix 11y ago> For instance, the following 161K file freezes completely Atom, to the point that you just have to close it: I just downloaded it and you are correct, it locks up. Its the really long line here: https://github.com/espadrine/aulx/blob/master/html/tokenizer.js#L63 https://github.com/espadrine/aulx/blob/master/html/tokenizer... If I open it in Sublime 3 I see that they don't bother to syntax highlight long lines. They just skip it. Issue filed: https://github.com/atom/atom/issues/7444 https://github.com/atom/atom/issues/7444
- lorenzhs 11y ago> If I open it in Sublime 3 I see that they don't bother to syntax highlight long lines. They just skip it. It appears that Sublime Text 3's threshold is 16384 (2^14) characters. Longer lines are not highlighted. Works quite well to be honest.
- oneeyedpigeon 11y agoI think you meant line 634, not 63. Also, pro-tip, always link to a specific file version when you're referencing a line because master will change: https://github.com/espadrine/aulx/blob/b745723680f541353ad5090da16f4f18bc6ecbc0/html/tokenizer.js#L634 https://github.com/espadrine/aulx/blob/b745723680f541353ad50...
- e12e 11y ago> I was doing some complex regex's (porting a random sql dump file into a seeds.rb) As a vim/cli/linux user -- I'm trying to understand -- you were doing search-and-replace? As in what one (some would say a masochist) could do with sed/awk? And/or 's' in vim? (Sed is in some ways more relevant as it works on streams, and so as long as you have the diskspace to store the edited copy, size shouldn't really matter. I suppose it might be possible to have long enough lines that sed chokes, but I've never had to deal with something like that...)
- sergiosgc 11y agoI concur. Congratulations to the team. The project seems to be going in the right direction. It's not up to 1.0 standards for me, though. I'm on Linux, on a last year's X1 Carbon. HiDPI display, at slightly over 200dpi. I'm greeted with this: http://i.imgur.com/McaVhKJ.png?1 http://i.imgur.com/McaVhKJ.png?1 The menu has no margins and no padding but, worse of all, everything is tiny. Note that the main text font is smaller than the i3 top bar (which is at the barely readable size). HiDPI support is not something esoteric nowadays. Lots of hardware requires it, and Linux toolkits support it rather well (not perfect, but ok anyhow). I fiddled with Atom's CSS enough to test drive it. It is ok for common tasks, albeit a bit sluggish (I come from vim...). I could live with that. What I can't live with is all manners of breakage my custom CSS introduced, so I can't yet do a one month run with the editor to kick the tires.