I agree with most of these statements, but I also understand that AWS Cloud 9 can’t be the same product as it was before. After all AWS bought it, probably because they wanted to include it into their ecosystem, not because they just liked it and wanted to own it. I was quite excited about Lambda integration and decided to give it a try. My feelings and observations after one week could sum up this:
Such car can only drive the one who knows every detail about how the car works. Before you turn it on, you need to adjust the spikes, blow the tires, and adjust the voltage. It is a pure contrast to what Cloud9 was before: a user-friendly product. For people who just want to drive a car and are not interested to be driver and car mechanic in one person, this is a disaster and they will go away, I’m pretty sure.
Even if I am enthusiastic about the integration of Labma’s functionality adn the fact that the whole AWS ecosystem became more accessible with AWS Cloud 9, I must admit that Cloud 9 has irretrievably lost some of it’s simplicity and multi-purpose functionality. It seems impossible to have everything in one …
So there is no way back. If you choose to jump on AWS bandwagon, great, I’m sure that development will go on, support is great, documentation professional (and insanely long), but we need to forgot old Cloud 9, so let it RIP.
And about templates… c’mon guys, is it such a problem to run a little script which will configure your workspace, install node, etc? I think not.
So what is more important for me (and time consuming) is possibility to run script to configure also AWS services (IAM, VPC, EC2, etc) from within Cloud 9. If this is already possible, I would be grateful for any hint.
Edit: Just got answer on AWS forum that most of it is possible with their CLI.