Nitrous Service Shutdown – November 14th

Re:Nitrous Service Shutdown – November 14th by SkyMarshal on Monday October 31, 2016 @07:47PM (#12842019)

>I asked in GitLab and everyone said they didn't want to code in a browser for usability reasons.

Can't speak for anyone else but I'm constantly battling to keep my browser from crashing due to too many tabs. Namely Chrome and Firefox on Linux and OSX. I open tabs, then forget to close them. Even as I write this Chrome is popping up alert boxes saying so-and-so page has stopped responding, do I want to Kill or Wait? The thought of adding a fairly heavy-weight SPA IDE to that mix is not attractive.

Out of curiosity, can Atom (https://atom.io/) load a remote IDE into its separate memory space? Only best-of-both worlds I can think of.

[ Parent | on HN ]

Re:Nitrous Service Shutdown – November 14th by raingrove on Monday October 31, 2016 @11:13PM (#12843080)

We had an Atom plugin called Nitrogen that did file sync, remote terminal, and app preview.

https://community.nitrous.io/docs/using-the-nitrogen-atom-pl...

Most of our users preferred the in-browser experience though...

[ Parent | on HN ]

Re:Nitrous Service Shutdown – November 14th by sytse on Monday October 31, 2016 @09:39PM (#12842708)

I agree that something like Atom (javascript IDE run locally) might be the best of both worlds. I think GitHub will lead the innovation with that.

[ Parent | on HN ]