NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
More Sinatra's offsprings in Perl? (Score:1)
oz.
Re: (Score:1)
Actually they did know about Dancer.
After the Dancer release to github, vti wrote a dancer clone using Mojo. Eventually he re-wrote it using Mojolicious, and that was the spark that ignited Mojolicious::Lite development.
Best regards,
life is short
Re: (Score:1)
Hello, to be frank, reading this makes me sick.
So it seems, they actually came on GitHub, found out Dancer, and just fork it? Whithout even taking five minutes to send me an email about that?
Marketblogging about it then smells like arrongance to me, as they don't even take the time to quote the origin of their work.
What is the purpose of such a behaviour? Splitting the Perl community in small groups that work one against the other?
I really don't understand. I'm surprised to see how big some egos are
Re:More Sinatra's offsprings in Perl? (Score:2)
Uh, that's a little unfair. I've been using Mojo since November last year and it from the git log you only put Dancer on github a few weeks ago.
Mojolicious::Lite is just a variant on the Mojolicious code to allow you to have apps in one file, like you have in Dancer. It's not a fork.
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Reply to This
Parent
Re: (Score:1)
Quoting the previous message:
This is a fork, please. Mojolicious was there long ago, I never said the opposite.
But Mojolicious::Lite, it has been directly inspired by my work on Dancer. I don't blame the fork itself, afterall it's how things happen in free software.
But would it be difficult to quote Dancer somewhere, just in order to give a bit of credit to my work?
This is a fork, and an