3 ms·
I've been using Nitrous for three months now. Here's why I stick with it: 1) I don't code offline any more. I have too many languages I work with and there's t
by darkpicnic 13y ago
I've been using Nitrous for three months now. Here's why I stick with it:
1) I don't code offline any more. I have too many languages I work with and there's too many points of failure that can be easily fixed with a Google search or StackOverflow. If I'm offline, it's usually a waste of time and most likely, I should be taking a walk.
2) Having a dev environment that is remote means my computer can completely fail and in 5 min, I'm deploying production code again. It means I can move between machines without ANYTHING being different. Leave your work computer at work, work from a friend's computer, yours, it doesn't matter.
3) You actually have control over your box resources. Cloud9 boxes were abysmally slow, even though their editor was better. Koding was way too focused on social and attempting to do too much. Nitrous is simple and fast.
That being said, here is what Nitrous needs to work on:
1) Uptime has been sub-par. They've had problems, especially with US-East, that have led to me not being able to work. This has been minimal, but enough to make me concerned.
2) The editor is very minimal. There is no fuzzy searching for files (like in Sublime), no auto-complete, no code hinting, no error checking other than really basic stuff, like indentation in Python or broken div tags in HTML. Having dabbled with Cloud9's editor, which is fantastic, I def think they need to focus on this.
3) Collaborative editing seems half-baked. Each user has to open the same file and then press a button "Collab Mode". If either forgets to press the button, your editing different files. There's also no sharing of console output, so this means if you are running a script that you are both working on, you both cannot see the same console output. Probably a pretty tricky problem to overcome, so I don't totally blame them.
All and all, still really like the service and hope they keep improving.
- mark_l_watson 13y agoI agree. I hope that they use some of the infused money to add auto completion and themes to the editor.
- gerbal 13y agoRight now it seems like Nitrous's team is really focused on improving stability. And with the apparent rapid growth in scale, that's important. You are certainly right about the need to improve the editor. While the minimalism is part of what has kept me on Nitrous (over Cloud9 or others), it needs massive improvements. It seems to have stagnated for months. CodeMirror has many, many features which would seem to be fairly easy to integrate into the IDE, but haven't been. I hope the next round of hires is more front-end focused.