ah ok, I understand. Yes, that's totally something we would do. Cloning, rewriting in a new language, or forking would be appropriate. It wouldn't make much sense to clone Reddit because it's already open source, but forking it and modifying it would be very appropriate.
We wrote four chat servers reminiscent of chat.nodejs.org in batch[1]; one with Brubeck (python), one with Chicago Boss (erlang), one with node.js, and then the Brubeck chat program was rewritten to work inside of a Spotify App, so yes we clone existing projects. But typically with a project like that, there's a lot of cool stuff in the beginning and you eschew some more tedious aspects that you would need for a real-world project, like, say... IE compatibility. Once you're housekeeping and your new work doesn't teach you much and doesn't give you cool things to show the rest of the group, it gets really boring really fast, and the environment naturally encourages you to do something more dynamic.
ah ok, I understand. Yes, that's totally something we would do. Cloning, rewriting in a new language, or forking would be appropriate. It wouldn't make much sense to clone Reddit because it's already open source, but forking it and modifying it would be very appropriate.
We wrote four chat servers reminiscent of chat.nodejs.org in batch[1]; one with Brubeck (python), one with Chicago Boss (erlang), one with node.js, and then the Brubeck chat program was rewritten to work inside of a Spotify App, so yes we clone existing projects. But typically with a project like that, there's a lot of cool stuff in the beginning and you eschew some more tedious aspects that you would need for a real-world project, like, say... IE compatibility. Once you're housekeeping and your new work doesn't teach you much and doesn't give you cool things to show the rest of the group, it gets really boring really fast, and the environment naturally encourages you to do something more dynamic.