Skip to content
This repository has been archived by the owner on Mar 27, 2019. It is now read-only.

Commit

Permalink
add duo note
Browse files Browse the repository at this point in the history
  • Loading branch information
@tj
tj committed Aug 22, 2014
1 parent abb5096 commit be12d41
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions Readme.md
View file
@@ -1,3 +1,4 @@
Newcomers should use [Duo](https://github.com/duojs/duo) instead of this implementation. Duo is more feature-complete and adds additional goodies, so check it out!

![web component logo](http://i49.tinypic.com/e7nj9v.png)

Expand Down

8 comments on commit be12d41

@matthewmueller
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:-D

@netpoetica
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea... I think though that if it's at that level you might want to put a deprecation notice as well. Duo looks really good, awesome that it's backwards compatible with component as well, but I think if the recommendation of the core team is to use Duo going forward instead of component, component should be deprecated, just my two cents

@timaschew
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is duo really ready to work with? I still see many issues.
Maybe revert the note and add it again when Duo is more stable?

@sankargorthi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

component(1) appears to be abandoned as of now as discussed in #594 (initiated by you). Encouraging new developers to avoid component is a good idea in my opinion.

@tj
Copy link
Contributor Author

@tj tj commented on be12d41 Sep 12, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

component(1) was pretty unstable too (from an installation perspective with no semver at least), makes more sense to focus on Duo, I still haven't used it much so I can't comment on robustness but seemed fine to me!

@matthewmueller
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timaschew

I think most of the pain points of duo are coming from people that are trying to migrate their existing apps to Duo from Component. This should be significantly easier as of 0.8.3, but it still requires a shift in thinking.

I think this point is still relevant, that newcomers should give Duo a try over Component@1.x. I'm obviously biased here, so up to you guys.

@timaschew
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, agree to give newcomers a try with duo, but for non-newcomers, there should be also a note, that there is no migration guide from component to duo yet. and maybe refer to this issue: duojs/duo#280

@timaschew
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another question: what is the reason why duo is

more feature-complete

if I see the open issues of duo, it doesn't look like it's more feature complete

Please sign in to comment.