Atom text editor 1.7.0 released • Hacker News Board

Re: Atom text editor 1.7.0 released

#141

Post by pram » Thu, Apr 14, 2016, 6:16 PM UTC

untog wrote: post #64

Genuine, non-trolly question: why would I use Atom over Sublime Text? I've used both and by and large they were very effective replacements for each other, but Atom had performance issues with large files so I went back to Sublime. What am I missing out on?

I used Sublime for 6 years (I migrated when TextMate was obviously dead) and am just recently attempting to switch to Atom. The package manager is fantastic, and the git integration is very nice as well. It's much better now than when it first came out. It can be very sluggish though.

That said, it's missing two very important features from Sublime that I used constantly. First, you can't use it like a scratch pad like Sublime. In Sublime you can open a file, write stuff to it, and it will be persistent. Atom seems to have an option to save your current work, but can't be used this way from my experience. The second is it doesn't have multi-select like Sublime. You can't drag your mouse and have a bunch of different carets. That was TextMate's killer feature imo, and Sublime as well.

Re: Atom text editor 1.7.0 released

#142

Post by pyre » Thu, Apr 14, 2016, 9:59 PM UTC

mintplant wrote: post #60

pyre wrote: post #53

Earlier quoted context omitted.

The point is that if Electron itself (i.e. using Javascript and the DOM) was the issue then both would suffer.

You might want to tweak the wording a bit - it reads like you're comparing Monaco to Electron, as if it were another app framework based on Chromium.

Since both VS Code and Atom use Electron as a base, so if the basic premise of using JavaScript + the DOM to render a code editor / IDE were flawed (i.e. it could never be performant), then both systems would be having issues.

This is what I was trying to state. If performance issues were fundamentally tied to the use of Electron, then you would see that manifest itself in both packages.

Re: Atom text editor 1.7.0 released

#143

Post by [deleted] » Thu, Apr 14, 2016, 9:59 PM UTC

mintplant wrote: post #60

pyre wrote: post #53

Earlier quoted context omitted.

The point is that if Electron itself (i.e. using Javascript and the DOM) was the issue then both would suffer.

You might want to tweak the wording a bit - it reads like you're comparing Monaco to Electron, as if it were another app framework based on Chromium.

[deleted]

Re: Atom text editor 1.7.0 released

#144

Post by mintplant » Thu, Apr 14, 2016, 10:26 PM UTC

pyre wrote: post #142

mintplant wrote: post #60

Earlier quoted context omitted.

You might want to tweak the wording a bit - it reads like you're comparing Monaco to Electron, as if it were another app framework based on Chromium.

Since both VS Code and Atom use Electron as a base, so if the basic premise of using JavaScript + the DOM to render a code editor / IDE were flawed (i.e. it could never be performant), then both systems would be having issues. This is what I was trying to state. If performance issues were fundamentally tied to the use of Electron, then you would see that manifest itself in both packages.

Oops, I thought you had written sdesol's comment [1]. Sorry.

[1] https://news.ycombinator.com/item?id=11493311