Re:Time to say good bye to localhost?
by ollysb on Thursday March 15, 2012 @12:32PM
(#3709184)
Depends what the upside was really. If they could continuously run my test suite in the background at near instant speeds then I'd jump onboard.
[ Parent
| on HN ]
If you ever worked at a company that uses a shared server for development, you know that even 20 concurrent developers can bring a sizable machine (not top, but also not bad) down to its knees if they run some sizable framework in dev mode. Code running amok (oops, infinite loop again), test suites running all the time, databases being overloaded by people doing 'some load testing'.
I don't believe that koding will give you an environment that is in any way better than your local stuff (except when they ask the full hosting costs per developer). So the idea that they continuously run your test suite in any way better than a proper setup on your local machine is wishful thinking.
valid points. obviously what we can give for free is not a 4g ram and 8 cores, it's a small instance that runs most of the things- look at it from the bright side, ur program will halt sooner, in case of infinite loop :) and if a company chooses koding to be their dev environment, they are free to provide any amount of ram or cpu per developer, in that case, everything will work as you expect.