Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Cro approach and "purpose" clearer #2

Open
Altai-man opened this issue Dec 7, 2018 · 0 comments
Open

Make Cro approach and "purpose" clearer #2

Altai-man opened this issue Dec 7, 2018 · 0 comments

Comments

@Altai-man
Copy link
Member

See https://colabti.org/irclogger/irclogger_log/perl6?date=2018-12-07#l879

With all respect to current design, I think, there should be a clearer note or explanation that:

  • Cro is not just your average web framework just because it can serve some http.
  • While showing "end user" features is nice compared to "abstract benefit" ones("You can build a great things with it, "just" that"), there are tons of web frameworks, so Cro::Core key value is being unnoticed by possible end users as in "Oh, they deal with Web, but I don't do that, I do $task-where-composable-chains-are-great-to-use, I don't need a web server".

We already have Approach document written, but one should search for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant