Fully understood, but in this case I felt really strongly that it was an honest overlook :)
The lack of key (URL) information simply didn't turn me off this one. 2012/8/23 Hassan Schroeder <[email protected]> > On Thu, Aug 23, 2012 at 7:28 AM, Gintautas Šimkus <[email protected]> > wrote: > > Hassan, I think Sergey simply overlooked that part :) Here it is with > very > > minimal copy/pasting into a search engine: > > Yes, I'm sure I could have found the URL by searching, but my point > was that a gem announcement should also *explain the problem* that > the gem addresses: give me a reason to use it. > > A vague reference to "semantic navigation" doesn't grab me :-) > > -- > Hassan Schroeder ------------------------ [email protected] > http://about.me/hassanschroeder > twitter: @hassan > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Pagarbiai, Gintautas -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
