You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@couchdb.apache.org by ermouth <er...@gmail.com> on 2015/05/07 20:11:34 UTC
CouchDB and its (orphan) childs
Dear colleagues,
I‘m going to write longread at Medium about couchapps, smileupps, hoodie
and cloudwall.
Want to compare them in terms of:
* overall architecture and maturity,
* applicability,
* strong and weak sides,
* possible future issues,
* tooling,
* maintainability,
* ability to scale,
* implied costs of ownership.
Kind of investigation. Please, add points I missed.
Also I have several qustions about Hoodie. @Jan, what is the best way to
ask them keeping in mind not all of them seem comfortable for Hoodie?
Same about Smileupps, @Giovanni, can I ask you several may be not very
comfortable questions?And if your answer is ‘yes’ – how can I do it?
And if someone here tried out cloudwall.me, please, feel free to criticize
– tell me what do you think about my little pet project.
Thanks in advance.
ermouth
Re: CouchDB and its (orphan) childs
Posted by Jan Lehnardt <ja...@apache.org>.
> On 07 May 2015, at 20:11, ermouth <er...@gmail.com> wrote:
>
> Dear colleagues,
>
> I‘m going to write longread at Medium about couchapps, smileupps, hoodie
> and cloudwall.
>
> Want to compare them in terms of:
> * overall architecture and maturity,
> * applicability,
> * strong and weak sides,
> * possible future issues,
> * tooling,
> * maintainability,
> * ability to scale,
> * implied costs of ownership.
>
> Kind of investigation. Please, add points I missed.
>
> Also I have several qustions about Hoodie. @Jan, what is the best way to
> ask them keeping in mind not all of them seem comfortable for Hoodie?
Great idea! :)
I’m happy to answer any questions :) You can find me on the #couchdb and
#hoodie IRC channels on Freenode, the Hoodie Slack (http://hood.ie/chat/).
You can also always ask on the Hoodie discussions repo
(https://github.com/hoodiehq/discussion/issues) or email me personally
on this email.
Best
Jan
--
>
> Same about Smileupps, @Giovanni, can I ask you several may be not very
> comfortable questions?And if your answer is ‘yes’ – how can I do it?
>
> And if someone here tried out cloudwall.me, please, feel free to criticize
> – tell me what do you think about my little pet project.
>
> Thanks in advance.
>
> ermouth
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/
Re: CouchDB and its (orphan) childs
Posted by ermouth <er...@gmail.com>.
Nope.
ermouth
2015-05-07 21:52 GMT+03:00 Giovanni P <fi...@gmail.com>:
> Is there an "app store" anywhere for cloudwall.me?
>
> On Thu, May 7, 2015 at 3:11 PM, ermouth <er...@gmail.com> wrote:
>
> > Dear colleagues,
> >
> > I‘m going to write longread at Medium about couchapps, smileupps, hoodie
> > and cloudwall.
> >
> > Want to compare them in terms of:
> > * overall architecture and maturity,
> > * applicability,
> > * strong and weak sides,
> > * possible future issues,
> > * tooling,
> > * maintainability,
> > * ability to scale,
> > * implied costs of ownership.
> >
> > Kind of investigation. Please, add points I missed.
> >
> > Also I have several qustions about Hoodie. @Jan, what is the best way to
> > ask them keeping in mind not all of them seem comfortable for Hoodie?
> >
> > Same about Smileupps, @Giovanni, can I ask you several may be not very
> > comfortable questions?And if your answer is ‘yes’ – how can I do it?
> >
> > And if someone here tried out cloudwall.me, please, feel free to
> criticize
> > – tell me what do you think about my little pet project.
> >
> > Thanks in advance.
> >
> > ermouth
> >
>
Re: CouchDB and its (orphan) childs
Posted by Giovanni P <fi...@gmail.com>.
Is there an "app store" anywhere for cloudwall.me?
On Thu, May 7, 2015 at 3:11 PM, ermouth <er...@gmail.com> wrote:
> Dear colleagues,
>
> I‘m going to write longread at Medium about couchapps, smileupps, hoodie
> and cloudwall.
>
> Want to compare them in terms of:
> * overall architecture and maturity,
> * applicability,
> * strong and weak sides,
> * possible future issues,
> * tooling,
> * maintainability,
> * ability to scale,
> * implied costs of ownership.
>
> Kind of investigation. Please, add points I missed.
>
> Also I have several qustions about Hoodie. @Jan, what is the best way to
> ask them keeping in mind not all of them seem comfortable for Hoodie?
>
> Same about Smileupps, @Giovanni, can I ask you several may be not very
> comfortable questions?And if your answer is ‘yes’ – how can I do it?
>
> And if someone here tried out cloudwall.me, please, feel free to criticize
> – tell me what do you think about my little pet project.
>
> Thanks in advance.
>
> ermouth
>
Re: CouchDB and its (orphan) childs
Posted by Johs Ensby <jo...@b2w.com>.
Ermouth,
this would be very helpful.
Maybe common denominator or “best-of” ideas can be brought back to the discussion on the future of Couch apps or the story of Couch apps
Johs
> On 08 May 2015, at 09:03, ermouth <er...@gmail.com> wrote:
>
>> couchapps, hoodie and cloudwall apps are not competitors
>
> Exactly! Thats why I decided to make an observation.
>
> ermouth
Re: CouchDB and its (orphan) childs
Posted by ermouth <er...@gmail.com>.
> couchapps, hoodie and cloudwall apps are not competitors
Exactly! Thats why I decided to make an observation.
ermouth
Re: CouchDB and its (orphan) childs
Posted by Giovanni Lenzi <g....@smileupps.com>.
And I also think that, besides smileupps, which is not an app-framework but
some sort of docker for REST apps, it would be important to mention that
couchapps, hoodie and cloudwall apps are not competitors against each
other, but instead their features and key strenghts can even be merged
using ddocs to create amazing web applications
2015-05-08 8:13 GMT+02:00 Giovanni Lenzi <g....@smileupps.com>:
> Hi ermouth,
> I like your effort in telling differences between these different
> technologies and I agree to your questions. We can meet on couchdb irc
> channel and then go private.
>
> This could be added to the list I proposed, even I have some comments on
> Medium, so I take back that discussion from where it derailed.
>
> Regarding your pet, I think it powers a very intuitive ui for building and
> sharing data and apps across devices. I wish the best. But I read about its
> security weakness, and I was wondering... couldn't it be addressed somehow
> with couchapp server-side security features?
>
>
> Il giorno 07/mag/2015 20:11, "ermouth" <er...@gmail.com> ha scritto:
>
>> Dear colleagues,
>>
>> I‘m going to write longread at Medium about couchapps, smileupps, hoodie
>> and cloudwall.
>>
>> Want to compare them in terms of:
>> * overall architecture and maturity,
>> * applicability,
>> * strong and weak sides,
>> * possible future issues,
>> * tooling,
>> * maintainability,
>> * ability to scale,
>> * implied costs of ownership.
>>
>> Kind of investigation. Please, add points I missed.
>>
>> Also I have several qustions about Hoodie. @Jan, what is the best way to
>> ask them keeping in mind not all of them seem comfortable for Hoodie?
>>
>> Same about Smileupps, @Giovanni, can I ask you several may be not very
>> comfortable questions?And if your answer is ‘yes’ – how can I do it?
>>
>> And if someone here tried out cloudwall.me, please, feel free to
>> criticize
>> – tell me what do you think about my little pet project.
>>
>> Thanks in advance.
>>
>> ermouth
>>
>
--
Giovanni Lenzi
www.smileupps.com
Smileupps Couchapps Store
Re: CouchDB and its (orphan) childs
Posted by Giovanni Lenzi <g....@smileupps.com>.
Hi ermouth,
> To enforce access control I‘ve created CoverCouch
> https://github.com/ermouth/covercouch. It implements per-doc read ACL
> keeping original CouchDB API untouched.
>
Understood.
Anyway, with the video and latest images, now it is much more clear. If I
can say something.. maybe a first-time user could click straight on "Run
OS", as I did, risking of losing himself on the login or dashboard page,
withouth first understanding the concept/purpose.. To address it, maybe the
video should be put just above the three homepage buttons... anyway, this
has been only my own personal experience.
Congratulations for such a huge and brilliant work
>
> > We can meet on couchdb irc
>
> Thanks a lot for your endorsement! Is it possible to chat using gtalk or
> skype (I‘m ermouth everywhere)? I do not use IRC for some serious reasons,
> sorry.
Gtalk is ok. I'll contact you. Let me know next weeks, when you will be
ready to go.
--
Giovanni Lenzi
www.smileupps.com
Smileupps Cloud App Store
Re: CouchDB and its (orphan) childs
Posted by ermouth <er...@gmail.com>.
Hi Giovanni!
> couldn't it be addressed somehow with couchapp server-side security
features
It does not seem possible. Since cloudwall.me employs PouchDB as storage
and replication layer, native replication protocol required. It can not be
re-implemeted using rewrites+map+list combination.
To enforce access control I‘ve created CoverCouch
https://github.com/ermouth/covercouch. It implements per-doc read ACL
keeping original CouchDB API untouched.
> We can meet on couchdb irc
Thanks a lot for your endorsement! Is it possible to chat using gtalk or
skype (I‘m ermouth everywhere)? I do not use IRC for some serious reasons,
sorry.
ermouth
Re: CouchDB and its (orphan) childs
Posted by Giovanni Lenzi <g....@smileupps.com>.
Hi ermouth,
I like your effort in telling differences between these different
technologies and I agree to your questions. We can meet on couchdb irc
channel and then go private.
This could be added to the list I proposed, even I have some comments on
Medium, so I take back that discussion from where it derailed.
Regarding your pet, I think it powers a very intuitive ui for building and
sharing data and apps across devices. I wish the best. But I read about its
security weakness, and I was wondering... couldn't it be addressed somehow
with couchapp server-side security features?
Il giorno 07/mag/2015 20:11, "ermouth" <er...@gmail.com> ha scritto:
> Dear colleagues,
>
> I‘m going to write longread at Medium about couchapps, smileupps, hoodie
> and cloudwall.
>
> Want to compare them in terms of:
> * overall architecture and maturity,
> * applicability,
> * strong and weak sides,
> * possible future issues,
> * tooling,
> * maintainability,
> * ability to scale,
> * implied costs of ownership.
>
> Kind of investigation. Please, add points I missed.
>
> Also I have several qustions about Hoodie. @Jan, what is the best way to
> ask them keeping in mind not all of them seem comfortable for Hoodie?
>
> Same about Smileupps, @Giovanni, can I ask you several may be not very
> comfortable questions?And if your answer is ‘yes’ – how can I do it?
>
> And if someone here tried out cloudwall.me, please, feel free to criticize
> – tell me what do you think about my little pet project.
>
> Thanks in advance.
>
> ermouth
>