51–60 of 106 posts
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
For the money part, you might also consider setting up the domain and redirect for a small fee. For instance, my-name.com could be my VMs securised with a password.
Also, what is the limit of GB I can put on the VM? Say I want to upload files and mp3s.. is there a limit? May I pay to increase it?
Finally, I would like to be able to connect to my VM from other way than web. Say I'm on my linux box with my terminal prompt, it would be nice if I could just ssh to my-name.com and get my VM.. upload/download stuff with scp, and connect to it with FTP. But of course, this would work more with the linux part I suppose :p
Anyhow, congrats also for the "I started my startup" which is, in my opinion, amongst the hardest part (starting!).
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
Surely they've already thought of this.
On the other hand, perhaps their thinking on this is part of the secret sauce, and it's being kept secret for good reason.
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
Open Source could be an advantage for them if they change their license to the AGPLv3. With an AGPLv3 license, any competitors would be required to make their modifications available for download. But as the copyright holder, the OP would not have to release any source he didn't want to, giving him the flexibility to run private, closed source extensions/enhancements if he chooses.
I guess they could sign the copyright over to him, but I don't see another way around that. (IANAL)
Earlier quoted context omitted.
you might want to rethink about plugins depending on your expected audience. People who are looking for good remote desktop solutions would be OK with installing plugins. I played the game on the front page on spoon.net and there was very little lag, it was a smooth experience. People who use remote desktop would prefer smooth experience over ease of installation.
Completely disagree with this idea. If you can avoid browser plugins without major issue, and it seems you have been successful at that so far, by all means continue to do so. Not only will the technorati appreciate not having to install yet another piece of (usually unnecessary) software, but corporate customers will be more inclined to deploy in their environments if it means there won't be another piece of softwar…
I agree that they should avoid plugins if their app works fine on html & js, however, this is unlikely with the current html and js. (Think of playing games). Maybe with the improvements in HTML5 this might be achievable, but currently it's not.
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive adva…
It's fine; the source code to their product is not a competitive advantage ( http://blog.asmartbear.com/unfair-advantages.html )