=.=
Have been using atom on mac for a while, these few days it feels buggy.
Adding project folder does not work like half of the time.
Adding a page of js code and make a .js file in the editor will make the editor freeze and in the end crash.
Does anyone have similar issue when using atom ???
Or I should try uninstall and reinstall it.
I think is yes, i try once because i think its good to use. When i open it, its freeze “not responding”. but i dont blame atom for these, and just say “my computer doesnt support it” and i use Aptana studio 3 till now. smoothly…
Works as a charm on my Debian Linux machine.
I guess Mac porting is a problematic for some reason and I believe it’s a baby IDE smallpocks, wait few more updates, they keep updating it every week and problem will be probably solved and patched, ofc. depends of your system health as well and before all I advize uninstall, clean install, update… check if the problem still persists or it’s gone. Contact the guys on Github from ATOM Dev team send them over bug report you get, end of story, day or few and removed probably.
My works great but it’s still young stuff not mature yet for me,looking good though, iinstalled and constantly followed after updates, reading changes, improvements and stuff but Sublime 3 and Vim are my kind of religion for a long time now, will stay that waymuch more as far as I’m concern
Big shouts to my @Github ATOM Team Guys,
Keep up the good work ladies.
I also encountered the same issue with Atom. I’m using Linux Ubuntu and many time reinstall the package but still got issue. Changed it to VS Code and I’ve got no issue.
For me, it’s the linter packages. They just don’t work right. At all. (Also, copy-pasting screws up indentation, and yes, I disabled the “indent on paste” setting, and it didn’t fix anything.)
I gave Atom a good long try, but today I hit my limit when the Rubocop linter kept complaining about a problem in a different file from the one I was in. And I went to the other file and fixed it, and Rubocop kept complaining anyway, and blocking my view of the code I was working on.
You could argue this isn’t Atom’s fault. To that, I reply that I don’t care whose fault it is, I care that it’s stopping me from writing code. If the Atom ecosystem doesn’t have a good Rubocop linter, then I will decamp for an ecosystem that does.
Hello, SublimeText, my old friend. It’s good to talk with you again.