Node.js: fork - yes or not?
I think use Node.js is much better than RoR. (IMHO)
Changing the language will be famous news.
But i think this is not loved thema.
Changing anything big will take many time and financies.
Diaspora hasn't any financies (i think) and time can be used for other features/improvements.
But when will somebody fork this project and rebuild it to Node.js what will say the crew?
Do you accept forks of your project or will you continue with justice?
Thank you for any answers
Jason Robinson Thu 13 Feb 2014 4:53AM
@seantilleycommunit in a way true, if you talk about diaspora* as the server software. I'd rather talk about it as a network ;)
Christophe Thu 13 Feb 2014 6:24PM
@maxsamael you should check out Libertree!
Sean Tilley Thu 13 Feb 2014 6:38PM
That's fair, but Diaspora's definition as a network has traditionally been mostly a network of Diaspora pods and Friendica servers. The groundwork we use to make this network communicate is sort just a bunch of partial implementations of standards and rubber bands duct-taped together at the moment.
It works, but I suppose it's worth asking ourselves whether we should improve the foundations for federation and data before encouraging people to build apps and sites that are a part of our network. We do, after all, want to offer a congruent experience for everybody on the network. Especially when you consider how many decentralized social platforms still don't federate with each other.
nio Thu 13 Feb 2014 7:02PM
@christophe I don't want use anything else as diaspora project.
There is many negatives.
I want support the diaspora with new modules (plugins), improvements, servers, bug fixes, donations, etc...
In all means there is much to work and I don't waste me time with X other projects. I <3 diaspora and I want use it :)
goob Thu 13 Feb 2014 7:23PM
whether we should improve the foundations for federation and data before encouraging people to build apps and sites that are a part of our network.
Yes! Definitely.
I realise I'm saying this, knowing that I won't be able to help at all with this task...
RAM518 Thu 13 Feb 2014 8:39PM
Node.js is meant to be run as client-side javascript. RoR is a server-side technology. It doesn't make sense to run D* in a javascript layer, and if you have much experience with javascript, you would cringe at this thought. That's not what javascript was built to do. I vote no.
Christophe Fri 14 Feb 2014 12:25PM
@ram518 Please check Wikipedia: "Node.js is a software platform that is used to build scalable network (especially server-side) applications."
nio Sun 16 Feb 2014 3:46PM
@ram518 You don't have truth at all.
Node.js can be used as server side only. Alternatively you can use Angular or other infrastructure. In this case is there client side javascript.
Anyway you can check some comparsions about speed.
Node is excellent software for API, you can divide the user area and API.
In case speed is RoR now good, but not brilliant.
Next point, i think decentralization and security is in all means answer to this type of network. (IMO)
lnxwalt Sun 16 Feb 2014 9:24PM
I do not believe that the Diaspora project's time is well spent re-implementing the already-existing server in YASPLE (Yet Another Shiny Programming LanguagE). However, if you have the skills to write a Node implementation, go ahead. In the process, you will expose some of the weaknesses in federation, private messaging, tags, etc and you may gain new insights of how to fix them.
Sean Tilley · Wed 12 Feb 2014 9:40PM
@jasonrobinson While your point is valid, it wouldn't really be Diaspora, just some Diaspora federation-compatible application. ;)