Combination of efforts (Score: 1) by chebucto@pipedot.org on 2014-02-17 07:03 (#R) Since pipedot and soylentnews are both working towards the same goal, are there any plans to merge the two? Pipedot seems better in some respects (https by default, CSS looks more modern in places), but soylentnews has far more users.The ideal, to me, seems like a merge of pipedot's improvements to slash into the soylentnews codebase.As far as a I know, there are still plans to run a name choosing competition for soylentnews; pipedot is a good idea, and could easily be one of the options. Re: Combination of efforts (Score: 1) by vanderhoth@pipedot.org on 2014-02-17 14:28 (#Y) It's a little misleading. SoylentNews and |. are working toward the same thing, but with different approaches. |. is ground up where as Soylent is trying to use something existing.I like the ground up approach |. is taking there's been a lot of improvements in web technologies since Slashcode, which Soylent is based on, was first written.I think both will succeed in their own right. Soylent does have a very active volunteer crew, where as |. seems to be built by one person (who's doing a fantastic job). I don't think the two approaches are compatible though unless Soylent want's to give up Slash code at some point and use |.'s interface when it's more completely, but I can't really see that happening.
Re: Combination of efforts (Score: 1) by vanderhoth@pipedot.org on 2014-02-17 14:28 (#Y) It's a little misleading. SoylentNews and |. are working toward the same thing, but with different approaches. |. is ground up where as Soylent is trying to use something existing.I like the ground up approach |. is taking there's been a lot of improvements in web technologies since Slashcode, which Soylent is based on, was first written.I think both will succeed in their own right. Soylent does have a very active volunteer crew, where as |. seems to be built by one person (who's doing a fantastic job). I don't think the two approaches are compatible though unless Soylent want's to give up Slash code at some point and use |.'s interface when it's more completely, but I can't really see that happening.