I followed his advice and started to post there too. I even volunteered to become a moderator of the #perl tag on dev.to.
So I'd like to invite you to follow that tag and to post articles there using the #perl tag and other tags that might be relevant to your posts.
]]>There are not many ways to express the fact that you really value the work of someone.
You can send them postcards or thank-you notes, but when was the last time you remembered to do that?
Right, I also keep forgetting to thank the people who create all the free and awesome stuff I use.
Giving money as a way to express your thanks is frowned upon by many people, but trust me, the people who open an account on Patreon to make it easy to donate them money will appreciate it.
In any case it is way better than not saying anything.
So pick one or all three of us and depending on your financial possibilities sign up to give a monthly donation.
New names were added and support via GitHub is also mentioned.
I've posted the list of Perl-related creators who have a Patreon or GitHub sponsors account on the Perl Maven site where updating the list is just a Pull-request away.
]]>It became the most frequently read Perl Tutorial and the site is the 4th most visited Perl-related site after cpan.org, perl.org, and perlmonks.org.
I've received many comments on the individual articles that make up the Perl Tutorial. Some required and immediate fix or answer, but many included suggestions that need a lot more work to implement.
There are also a number of missing articles. Some can be seen as comments in the source of the Perl Tutorial page.
It is time to update the tutorial incorporating the comments made on the individual pages,
filling in holes where some topics have not been covered, and making the whole tutorial more like pages of a book.
I need your help in two ways:
This whole project is big and will take a lot of time. In order to justify the time I am going to spend on this I'd like to see that there are people who are ready to support it financially as well. So I've set up a Crowdfunding campaign.
Go ahead support the work via Indiegogo or if you don't want to use Indiegogo, you can send me your one-time support via PayPal to gabor at szabgab.com, or provide a monthly support via Patreon.
There are various perks for the supporters including an eBook version of the whole tutorial.
A few days ago I've started to use Patreon that allows people to support each other on a monthly basis. (Or per creation.)
Searching for perl shows lots of unrelated entries. So it won't be easy to find other people contributing to Perl or writing about Perl.
This is my account: Gabor Szabo on Patreon.
This is the account of David Farrell.
Do you have a Patreon account? Post your link in the comment section so others can find you!
]]>It is also not new. It is a very old tutorial, they just decided to spam you with it now.
]]>Are we so desperate that any spammer would do?
Yuki, I am not sure what do you expect in "evaluation" of this tutorial that is not "criticism". Do you expect people to find the good parts and talk about how wonderful it is that they explain about arrays?
Or do you think that it is ok that they don't "use warnings", don't "use strict", use $a and $b in examples, write code like this:
my @array=(a,b,c,d);
don't always indent their code. Just to name a few.
If you are interested, follow the GitHub project. If you'd like to help with the development, let me know, and I'll invite you to the Bailador Slack channel where we can discuss things. If you'd like to support the project financially then the best thing you can do is to back the crowdfunding campaign of my book about Bailador.
]]>
Most of the traffic to search.cpan.org comes from search Engines.
See some CPAN traffic numbers here
Maybe if more people were linking to pages of MetaCPAN from their own blogs in the relevant context.
For example if you write about databases and Perl you could link to the Perl DBI for Database Access. When you talk about AJAX and JSON, you could mention JSON and Perl. If you are talking about Dates or Timestamps, you could mention DateTime in Perl.
Or any other module that is relevant to your blog post.