I can understand your confusion on "what koding is", that is probably partially my fault. I'm the author of the docs/videos (a koding user, not staff), who is obviously a bit passionate about the platform.
I know i had no trouble "Getting" Koding, but that is because remote development is something i've been using/toying with for three or four years now. Originally it was heavy SSH, and focusing on trying to create VIM IDEs and improve a terminal oriented workflow so that it can all work through SSH, but eventually i learned about some of these Online Dev Environments. I used Cloud9 for about a year, before switching to Koding about a year ago. The point being, i've wanted this remote-environment concept for such a long time, it sort of comes naturally to me.
I imagine if you're very used to working locally, you have a hard time seeing the advantages of using a remote platform. I can understand, it's a very new tech, and it's not the next coming of Christ or anything. I got a bit overzealous with the "unlimited possibilities" line lol, but i have made an issue on the matter and plan on rewording that.
With all that said, i do strongly disagree that "Apparently the Koding team doesn't know either.". You're taking a beta product, with an obviously large list of features that aren't implemented, and saying that the devs don't know what the product is good for. It obviously has a roadmap, both with visible and non-visible features planned, so i think the devs have a good idea where they are headed with it.
It's not perfect of course, but online development is quite new. After being a user of many of these platforms, i chose Koding, so obviously i feel it's "the best". I am obviously biased because i have picked this platform as my platform of choice, but with the warning i hope you won't hold this against me.
Anyway, you can read my other posts which talk about how my docs project, and especially my "2 minute Koding" video, are not pitches to use Koding. They are for Koding users mostly, people who have already decided on the platform. These are things i, as a user, wanted to give to the community and hopefully foster an environment that i want to feel. Communities are what you make of them, and i am trying my part.
I respect your opinion nonetheless, and i'm sure the devs are taking what you say to heart. I hope i can improve the Overview as well, based on the feedback. :)
Hi, i'm the koding user (not staffer) who made the video/docs :)
The video wasn't intended to be a pitch. It was intended for users who are new to Koding, and to quickly gloss over the features of Koding so users can get there bearings on where to go for what.
I really dislike the docs being linked to, as everyone here seems to think that the docs are:
A: Official (understandable, but nevertheless the docs have been made by users)
B: A sales pitch.
I wanted to make the docs because the Koding Team had very little to no documentation, and i've spent a year answering some very common problems in the Koding Activity Feed. The koding docs have helped quite a few users i think, and i'm proud of them.
They aren't a sales pitch to try and buy you. I never intended for that, and i'm sorry they have been posted to HN as such :/
I'm the koding user (non staffer) who made the video.
My goal was to quickly gloss over the features with the video, but i thought the concept of Online Development was a pretty well grasped concept. No offense to you of course, the video obviously falls short for a lot of people. It's not intended to be a pitch, just an overview.
I had hoped that by going over the features, that Koding would make a bit of sense. Perhaps i need to redo the video? The short timeframe goal, really limits me though haha.
I never intended my 2 minute overview to be on the front page of Koding, nor be posted onto reddit and here. This is so much more publicity than a short little video targetted at new Koding users.
I'm the koding user (not staffer) who wrote the docs, good point on the Koding link. I never expected anyone to be reading the docs who didn't know the url for Koding, but both Reddit and Here have linked to the docs directly.
Not sure why, but i'll add a link to Koding from the docs today. Thanks for the feedback :)
Heya, i'm the koding user (not staffer) who wrote those docs :)
> This seems aloof. I feel that this is more explanatory of what Koding offers:
I would agree with this sentiment. I didn't expect so much publicity over my little doc project haha. I'll look at rewording that, thanks for the feedback :)
> On a side note, would it be possible to offer offline capability? Perhaps allowing users to download/upload Vagrant VMs configured with Puppet.
To my limited understanding, the VMs will offer an always-on option in the future. I haven't heard of a timeframe on any of this though.
My apologies if i'm slow to reply/etc, i'm new to this platform.
I know i had no trouble "Getting" Koding, but that is because remote development is something i've been using/toying with for three or four years now. Originally it was heavy SSH, and focusing on trying to create VIM IDEs and improve a terminal oriented workflow so that it can all work through SSH, but eventually i learned about some of these Online Dev Environments. I used Cloud9 for about a year, before switching to Koding about a year ago. The point being, i've wanted this remote-environment concept for such a long time, it sort of comes naturally to me.
I imagine if you're very used to working locally, you have a hard time seeing the advantages of using a remote platform. I can understand, it's a very new tech, and it's not the next coming of Christ or anything. I got a bit overzealous with the "unlimited possibilities" line lol, but i have made an issue on the matter and plan on rewording that.
With all that said, i do strongly disagree that "Apparently the Koding team doesn't know either.". You're taking a beta product, with an obviously large list of features that aren't implemented, and saying that the devs don't know what the product is good for. It obviously has a roadmap, both with visible and non-visible features planned, so i think the devs have a good idea where they are headed with it.
It's not perfect of course, but online development is quite new. After being a user of many of these platforms, i chose Koding, so obviously i feel it's "the best". I am obviously biased because i have picked this platform as my platform of choice, but with the warning i hope you won't hold this against me.
Anyway, you can read my other posts which talk about how my docs project, and especially my "2 minute Koding" video, are not pitches to use Koding. They are for Koding users mostly, people who have already decided on the platform. These are things i, as a user, wanted to give to the community and hopefully foster an environment that i want to feel. Communities are what you make of them, and i am trying my part.
I respect your opinion nonetheless, and i'm sure the devs are taking what you say to heart. I hope i can improve the Overview as well, based on the feedback. :)