I'd rather write vimscript than coffeescript.
Atom 1.0
391–400 of 459 posts
Re: Atom 1.0
#392Congrats 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 underton…
lol, 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.
I don't remember Winamp not able to play 20MB mp3, such a rip of entire album, since I started using it in 98.
Re: Atom 1.0
#393Congrats 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 underton…
Sorry 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 TextWrang…
I had found that Sublime did pretty terribly with large files (not source), so I was back in in Emacs.
Re: Atom 1.0
#394Go To Matching Bracket taking almost 2 seconds in atom, happens instantaneously on vim/sublime.
Re: Atom 1.0
#395Wow... just downloaded the windows installer version and it autoinstalled itself wherever it chose fit, without questioning, it installed shortcuts on the start menu, placed itself on an already bloated contextual menu on several file extensions as an Open option, instead on "Open with...", etc. I usually install software on my user folder on the work laptop, as I don't have enough priviledges. This time the installe…
To be fair Chrome doesn't ask you either, at least on the storage location. It looks like Atom puts itself in APPDATA, which is the easiest place to install because you have known permissions and update strategies. I actually like this method. I agree that I didn't like the default shortcut and context menu entries, however.
i also hate that part of chrome - i don't have a fast disk on my default C drive, and i want to move my apps to a separate disk. But chrome doesn't let you do that easily...why do product teams think they can make the best choice for the user, without giving a way out? For a normal user, they can just use a default, and it should be fine. But let me choose if i want to, god damn it!
Re: Atom 1.0
#396Earlier quoted context omitted.
I 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.)
I can open a 15MB log file, but my CPU usage skyrockets.
You're not trying to scale for millions of users. It's okay to let your CPU cook a bit.
Re: Atom 1.0
#397Earlier quoted context omitted.
lol, 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.
I don't remember Winamp not able to play 20MB mp3, such a rip of entire album, since I started using it in 98.
I 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.
Re: Atom 1.0
#398Nice, this is the first thing i start in the morning, use all day and close at the end of the day. I'm using Atom with monokai and linter and love it.
That mid century video is hilarious.
Re: Atom 1.0
#399Congrats 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 underton…
I 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...
The reason is that the core syntax highlighter (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.
Re: Atom 1.0
#400Earlier quoted context omitted.
It comes with Chromium, that is basically a browser. They have their own version of Chromium called Electron. But I recommend nwjs instead, witch is also built on Chromium and nodejs. And lets you make packages that only include your source code, so that you don't have to download the "browser" for every app.
Really? How is the app opened then without bundling Chromium? I built an app 4 months back and that was the only option.
You simply zip the files and rename to dot nw. Then the first time the user runs the file, the user needs to select "open with nw.exe".
ref: https://github.com/nwjs/nw.js/wiki/How-to-package-and-distri...
You probably want to include an "install" script that:
* Download and install nwjs if it doesn't exist
* Make the "package" open with nw.exe
* optionally: Create a shortcut to the "package" on the desktop
* optionally: Set a icon for the shortcut