News for hackers. Stuff that matters.
Re:Atom 1.34 by edoceo on Saturday January 19, 2019 @12:53PM (#18948187)
Our shop has 4 devs, one on VSCode, unlikely to convert, three on Atom. I was the last covert to Atom here - after 15+ years on jEdit.
Re:Atom 1.34 by d3sandoval on Saturday January 19, 2019 @03:19PM (#18948953)
For a second there, I thought I finally found the other person on the internet who was a jEdit zealot. But then I realized it's the same person I've known for years ;)

What makes you stick to Atom? I switched to VSCode due to Atom's terrible performance when opening huge files.

Re:Atom 1.34 by edoceo on Saturday January 19, 2019 @09:21PM (#18950537)
:) I don't open huge files, finally found a good SFTP plugin, php-debug hooks with xdebug.

Really it took me many months of tweaking to get Atom to be a daily driver - I don't want to do it again soon

Re:Atom 1.34 by aynawn on Sunday January 20, 2019 @10:56AM (#18953556)
I used Atom for a couple years and raved about it's features and package management but when it came to using it as an IDE, it fell short for one reason. It doesn't have a configurable way to debug across all languages. For example, try debugging python vs node. Python works well but node doesn't afaik.

OTOH vscode does have a way to do this using a `launch.json` file which is flexible enough to add custom debugging profiles for a single project and it can be stored directly in version control. I tried the editor out because of this one feature alone in order to debug node and haven't looked back.