Once fully integrated with AWS, this could offer a rather exciting, low friction way to work on the platform. Using Cloud9 to build, test, and deploy Lambda functions from a single interface with all the auth stuff dealt with automatically.. you could have some powerful APIs running in the cloud very quickly.
(Maybe there's even a play for getting this stuff into the hands of non-engineering employees. Build the "Excel" of APIs, if you will?)
The last thing this world needs is mission-critical software edited willy-nilly through a "convenient" web browser interface. We as an industry can barely put our pants on in the morning on the best of days, and now this.
I'll counter with the suggestion that nothing about how you access an editor should impact your SCM process. Cloud9 has a terminal to run SCM tools and a light-featured Git UI if that's your thing.
You're right - in an ideal world. Somehow the drive for adoption and market share seems to counter such common sense, resulting in the "get started quick" camp running production systems.
Agreed. IMO it's always during an emergency where it's a decision between fixing the server in 20 seconds, or 5 minutes via the normal deployment pipeline.
I'm including a continuous integration step as "normal deployment pipeline". Probably code review and other steps as well. The point is emergency is always --forced.
That Lambda use case makes a lot of sense. The editor they have in place for Lambda right now barely exists. You can't even use it if you go the upload the build artifact as a zip route.
(Maybe there's even a play for getting this stuff into the hands of non-engineering employees. Build the "Excel" of APIs, if you will?)