I've been developing on a chrome book for the past year. I can confirm that vs code runs very smooth, while atom is finicky and just flat out dies on opening large folders/files.
Kudos to another chromebook dev! Are you running Ubuntu in a Crouton, or another setup? I'm doing that and I run Atom without any complaints. It might just be the way I'm using it however.
I removed the write protection screw, upgraded my ssd, flashed on a new bios from https://mrchromebox.tech/, and installed galliumOS--originally I used chrubuntu, then straight ubunutu. Everything works great. Even installed display link drivers, so I can dock to 2 monitors at work.
Can you open arbitrarily large text files/directories in atom these days? Whenever, I open anything over a few thousand LOC atom seems to lock up for me. I was actually forced to switch from Atom to VSC, because I had a bad habit of accidentally clicking on `node_modules` in the file tree and crashing my session.
I had someone on here mention the write protection screw removal method to me before, I just couldn't bring myself to do it on my Pixel 2. But I should try it, I'm glad to hear someone say it worked out great for them. I definitely want to still be able to boot into the normal Chrome OS because it's preferable to me when I'm not working.
I think I see what you're saying. Maybe it's because the pixel is actually a beast, I don't notice it as much. I have VS Code installed, maybe I should give it another shot. I'm probably just used to Atom, and the only time I really used VSC I was trying to work on one of our really large .NET solutions and it just started throwing hundreds of errors at me. I should try one of my MEAN apps in it.
