Koding vs WakaTime: What are the differences?
Developers describe Koding as "A new way for developers to work". Koding is a feature rich cloud-based development environment complete with free VMs, an attractive IDE & sudo level terminal access!. On the other hand, WakaTime is detailed as "Quantify Your Coding. Open-source plugins for automatic time tracking & insights into your programming". Quantify your coding - open source plugins for automatic time tracking & insights into your programming.
Koding can be classified as a tool in the "Cloud IDE" category, while WakaTime is grouped under "Programming & Code Analytics".
Some of the features offered by Koding are:
- Free virtual machine (VM) with Ubuntu, root access, apt-get, and many commonly used tools
- Built-in Terminal with 256-color support
- All languages, databases, and command-line tools are supported
On the other hand, WakaTime provides the following key features:
- Fully automatic, with reports via email
- Find the time you spend per feature/commit
- See time spent in each language
"Free" is the primary reason why developers consider Koding over the competitors, whereas "Automatic time tracking per project" was stated as the key factor in picking WakaTime.
What is Koding?
What is WakaTime?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Koding?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Koding?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I like the editor and all the themes I can pick from. I started using Koding pretty early on after an invite. After experiencing sluggishness when turning on my VMs (had free account, VM's turn off 15 mins. after logging out) I decided to get on a paid plan so I can have an always on VM. This did not help. I was still experiencing sluggish VM's and also it did not help that Koding had a free storage space promotion that I believe their servers weren't ready to handle. I could not access my VM's on some evenings. I'd wait over an hour and still had no access. This one time I was working on something and my VM's were acting stupid. I tried restarting them, then they wouldn't turn on. So I just left my computer and when I came back and signed in again it was like one of my VM's was cleared out and I had a new one. My files were lost. Support was good, they manage to get my files back but a couple of them were corrupted, seems like some sort of system output wrote over them. Overall I had a very bad experience using Koding. I believe the lack the resources because most of the time I couldn't even view the files on my VM. I did like that the customer service was quick to respond and that it is centered around a social experience. I cancelled my subscription after such a bad experience. $19/month for something you can't access during peak hours is a ripoff. Customer service was great though as I did complain once and they credited one month to my account. However, it sucks that I lost some files. Maybe it'll be worth it when their computers are more powerful.
Contrary to the other reviewers experience, I've had no issues with downtime. In fact, as of today, my VM has been up 97 days!
These guys pump out features like no one's business. Take a look at their very active changelog: https://koding.com/Activity/Announcement/changelog
The community aspect is super awesome and they have a very engaged community. Overall, I like the value that I am getting for the money that I am paying them ($9/month).
It uses the user IaaS infrastructure - by default AWS
Time tracking for that, spent while working across multiple components and using multiple languages.
WakaTime allows us to track how much time is spent developing features.