Live data from Hacker News

Atom 1.20

blog.atom.io

61–69 of 69 posts

Re: Atom 1.20

#61
post #57

Earlier quoted context omitted.

> I love lots of what MS does. Does this include the Embrace+Extend+Extinguish strategy? And how does anyone, other than via sheer forgetfulness, think that Microsoft doesn't have similar nefariousness on today's drawing board? The revelation of the 3E strategy showed they are inherently and absolutely untrustworthy.

They said "lots of," not "all" or even "most." It's a big company, and they are not 100% evil because no company is 100% anything. And honestly, I believe any company with a stranglehold on any market will behave badly. Rather than being salty at Microsoft in particular, let's make sure no company ever has such a stranglehold on computing again.

I didn't claim that Microsoft was unique in anything but the 3E strategy itself.

Actually, what with Google duplicating more and more of Android's core open-source functionality into their proprietary apps and then leaving the open-source code to rot ... Microsoft isn't unique in that way, either.

But more importantly...

> let's make sure no company ever has such a stranglehold on computing again.

That's a long road ahead, since Google has a monopoly on the average user's very mind. And don't forget that Microsoft hasn't lost their stranglehold either, except among programmers and similar personnel. They may be behind on mobile, but they've held onto largely the same markets+marketshares that they had in the late 90's (plus more, though not at monopoly scale, thanks to Azure), and desktops+laptops won't be dying anytime soon.

Re: Atom 1.20

#62
post #12
post #6

Earlier quoted context omitted.

You were downvoted to oblivion, but honestly this is a huge issue that somehow feels like people are just OK with. Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. Full disclosure, I run a Linux desktop with 32GB of RAM. I'm not accustomed to type lag. Judging by your downvotes it's an acquired taste.

I downvoted paule89's comment because it felt like a cheap shot at an established product with well-known pros and cons. Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first. No, restating those facts on HN at every opportunity is not constructive.

I wish that I could upvote this twice.

Re: Atom 1.20

#63

I've tried all the editors, when it comes down to it I always end up going back to some combination of Sublime + Vim. I prefer to do most things on the command line rather than set up IDE configurations, so a plain text editor suits me just right. I like the customization of Sublime, and I've got it setup just how I like. In a way, Vim is similar... once you get it customized perfectly, there isn't going to be anothe…

"I prefer to do most things on the command line rather than set up IDE configurations, so a plain text editor suits me just right."

For me, the killer feature of editors like Atom and VS Code is zero-hassle setup of linters and code formatters. The integrations with Go tools will not only tell you what is wrong with your code as you work, they will automatically manage your imports directives and reformat the source.

Periodically I think about switching to Vim. I am sure that I could set up Vim to have the same features, but I feel like I might have to find a big chunk of time to learn how to manage Vim plugins and the appropriate key combinations to get the same effect.

Re: Atom 1.20

#64

Earlier quoted context omitted.

That's changed in the latest insider build - you can now have multiple projects open

Cool. I'll give it another go when I have some time to play. But honestly, most of the stuff I didn't like about Atom is resolved lately. It's fast enough, small enough (for my 16GB laptop), and reliable. And, has a gazillion features, most of which I never use.

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters?

I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

Re: Atom 1.20

#65

Earlier quoted context omitted.

Cool. I'll give it another go when I have some time to play. But honestly, most of the stuff I didn't like about Atom is resolved lately. It's fast enough, small enough (for my 16GB laptop), and reliable. And, has a gazillion features, most of which I never use.

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters? I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

What do you use now?

Re: Atom 1.20

#66

Earlier quoted context omitted.

Cool. I'll give it another go when I have some time to play. But honestly, most of the stuff I didn't like about Atom is resolved lately. It's fast enough, small enough (for my 16GB laptop), and reliable. And, has a gazillion features, most of which I never use.

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters? I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

I've never used it for anything quite that large. I have three windows open on my first virtual desktop: Editor, terminal, and browser. When I want to poke around in log files or other really long files, I'm using grep, tail, awk, and Perl (and vim), in the terminal.

The biggest file I regularly work with in the editor is 10,631 lines long (I just checked, and it's longer than I thought). Atom works fine with it, including syntax highlighting, and cutting/pasting/typing/etc.

Actually...out of curiosity, I just opened up a ~110,000 line file (a log I had laying around). It seems to work fine. It took a little longer to open than it would in vim (which is effectively instant), but not as long as I would have expected. It was well under a second, and within my comfort zone for opening files. Switching tabs seems maybe a little more sluggish with it loaded, but not uncomfortably so.

I think I have to accept Atom into the category of editors that can work with pretty large files. I can't imagine having a source file any longer than that 10,000 line file I work with regularly (and I would never make a file that large, but historic codebases sometimes have weird things in them), but it seems like it'll work even if someone did.

Re: Atom 1.20

#67

I've tried all the editors, when it comes down to it I always end up going back to some combination of Sublime + Vim. I prefer to do most things on the command line rather than set up IDE configurations, so a plain text editor suits me just right. I like the customization of Sublime, and I've got it setup just how I like. In a way, Vim is similar... once you get it customized perfectly, there isn't going to be anothe…

What's your combination of Sublime and Vim? I've recently switched from VSCode to Vim and have really started to like it. I try to use Vim keybindings in everything I do, including browsing on Chrome with the plethora of Vim-like extensions. I still use Sublime, mainly for its multi-cursor editing power. I don't there's an editor that can really match Sublime's multi-cursor feature. I know there's a way of doing in i…

I just meant that I use Sublime and Vim as my primary text editors. I do use the "vintage" mode in Sublime also, which mimics some of Vim's functionality.

Re: Atom 1.20

#68

Earlier quoted context omitted.

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters? I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

I've never used it for anything quite that large. I have three windows open on my first virtual desktop: Editor, terminal, and browser. When I want to poke around in log files or other really long files, I'm using grep, tail, awk, and Perl (and vim), in the terminal. The biggest file I regularly work with in the editor is 10,631 lines long (I just checked, and it's longer than I thought). Atom works fine with it, inc…

I think it is less the line count that I have problems with lately than line length. It's quite a specific use case, but I work with geographic data and occasionally deal with absolutely enormous wkb's that can be in the hundreds of thousands of characters. Couple that with writing in Hadoop typically going to one line per JSON representation and now I am regularly opening files to review that consist of a single line of text that might have upwards of 80,000 characters on average. Even beautified it still is problematic. VS code seems to be able to do it reasonably so the software stack cannot be blamed.

Re: Atom 1.20

#69
post #65

Earlier quoted context omitted.

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters? I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

What do you use now?

VS Code mostly and if it's a big one even VS code cannot handle I will use Vim. See the sibling comment for my somewhat pointed use case.
Post reply on HN