Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atom 1.33

blog.atom.io

Post reply on HN
Print view View original

41–50 of 55 posts

Re: Atom 1.33

#41

Post by onnnon »

cribbles wrote: post #5

I use Atom daily for work, and I am overall satisfied with the editor and its ecosystem, in particular the mammoth improvements the core team has made toward addressing speed issues that plagued the editor in prior years. I haven't tried the new GitHub integration features in this package, but they seem cool. That having been said - Atom devs, if you're reading this, _please_ put a priority on fixing the auto-update…

I have the same problem. My workaround is to close all application windows, then open a blank one, then do the "Restart and install". Works for me.

Re: Atom 1.33

#42

Post by dman »

melling wrote: post #15
dman wrote: post #9

Earlier quoted context omitted.

This can go the other way too => People kept complaining about Internet Explorer for years. Then one day better alternatives showed up (Firefox, Chrome) and dealing with sub-par experiences was no longer a necessity.

People complained about the lack of functionality in IE. Atom is functional and iterating fast. It works great on my 5 year old Mac Book Pro with 16 GB. I understand that some people do have more minimal hardware, but 16GB looks like a $100 investment. Performance and memory usage are being addressed. I simply see memory usage as less of a problem in 2018/2019. I want more functionality.

I think in 2019 Atom will have to effectively answer the question on what it offers over VS Code.

Re: Atom 1.33

#43

Post by alpaca128 »

pictur wrote: post #23
marsrover wrote: post #2

I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code. I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.

vscode gives me the impression of a shitty microsoft product.

Quite the opposite, imho VS Code is the best piece of software Microsoft has released in a long time.

Re: Atom 1.33

#44

Post by alpaca128 »

GeordiePowers wrote: post #32
marsrover wrote: post #2

I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code. I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.

I switched, after a prior history of many other editors, to VSCode, and then to Atom. One main reason: the vim plugin. The VSCode one was (is?) just not good. Atom's is quite good. VSCode is better for most people; it's a great editor, and does more out of the box without configuration. However, if you're someone who DOES feel the need to tweak everything until it's just right, VSC doesn't hold up. JSON configuration…

And I went from Atom to VS Code and then back to (Neo)Vim again. I haven't yet seen a Vim plugin which is complete enough for me to use without needing to change habits, so I just use Vim now and for some special situations VS Code.

Although now I've read that Atom is supposed to be faster than before, so I'm going to give that a try again.

Re: Atom 1.33

#45

Post by temporallobe »

I really love Atom over any editor I’ve ever used in the past, but damn it can be slow, so I hope this update addresses some of that. I mostly use it for writing code because of the extremely intuitive editing features, advanced regex, and beautiful syntax highlighting. However it can’t handle really large files like logs and such because it tries to prase everything and consumes tons of memory. For that nothing seems to beat Notepad++ on Windows (written in C!). One thing to remember is that Arom is an Electron app and as such is essentially a browser application, which sadly could never be as fast as a native app.

Re: Atom 1.33

#46

Post by hit8run »

coder543 wrote: post #21
hit8run wrote: post #20

I wish they could get Ruby working in Atom out of the box. I still can‘t believe how weak the tooling is in the Ruby on Rails world. Even Jetbrains fails miserably. Why on earth can‘t we have decent code completion in Ruby?! If the human brain can tell what will be available why can’t my computer.

I don't think even the human brain can consistently figure out what's going to be available in Ruby. Oftentimes, the only way to know is to set a breakpoint, run the code, and inspect it at runtime. This is why the tooling sucks even more for Ruby than most dynamic languages, and the code completion and static analysis will almost certainly always be worse than the equivalent tooling in a statically typed language wh…

I once did a web-project in Go just for the tooling. What I gained there was lost in the verbosity and the write everything from scratch mentality when it comes to webdev in Go.

Re: Atom 1.33

#47

Post by temporallobe »

hit8run wrote: post #20

I wish they could get Ruby working in Atom out of the box. I still can‘t believe how weak the tooling is in the Ruby on Rails world. Even Jetbrains fails miserably. Why on earth can‘t we have decent code completion in Ruby?! If the human brain can tell what will be available why can’t my computer.

Really? What’s wrong with RubyMine? I use it for RoR almost daily and it seems to kick ass. It’s not perfect, but then again maybe I don’t know for better. But I agree, developing in Ruby sucks in Atom.

Re: Atom 1.33

#48

Post by the_common_man »

cribbles wrote: post #5

I use Atom daily for work, and I am overall satisfied with the editor and its ecosystem, in particular the mammoth improvements the core team has made toward addressing speed issues that plagued the editor in prior years. I haven't tried the new GitHub integration features in this package, but they seem cool. That having been said - Atom devs, if you're reading this, _please_ put a priority on fixing the auto-update…

Yeah, the feature should simply be disabled. It's like this for 4 years now

Re: Atom 1.33

#49

Post by paulddraper »

melling wrote: post #15
dman wrote: post #9

Earlier quoted context omitted.

This can go the other way too => People kept complaining about Internet Explorer for years. Then one day better alternatives showed up (Firefox, Chrome) and dealing with sub-par experiences was no longer a necessity.

People complained about the lack of functionality in IE. Atom is functional and iterating fast. It works great on my 5 year old Mac Book Pro with 16 GB. I understand that some people do have more minimal hardware, but 16GB looks like a $100 investment. Performance and memory usage are being addressed. I simply see memory usage as less of a problem in 2018/2019. I want more functionality.

It wasn't until Chrome that people thought you could really do anything substantive in JS.

Re: Atom 1.33

#50

Post by pjmlp »

temporallobe wrote: post #45

I really love Atom over any editor I’ve ever used in the past, but damn it can be slow, so I hope this update addresses some of that. I mostly use it for writing code because of the extremely intuitive editing features, advanced regex, and beautiful syntax highlighting. However it can’t handle really large files like logs and such because it tries to prase everything and consumes tons of memory. For that nothing seem…

Notepad++ is written in C++.

https://github.com/notepad-plus-plus/notepad-plus-plus

Post reply on HN