hachiojipm / awesome-perl Goto Github PK

Quality Standardを２段階に設定されてますが、高いレベルのQuality Standardが適用されるのは具体的に言ってどのカテゴリーなのでしょうか？ Web Application Frameworkを例に挙げられてますが、他にもあるのでしょうか？

また、Web Application Frameworkなどにわざわざ高いレベルのQuality Standardを適用しているのは何故でしょうか？ そのあたりの説明がないと無用な混乱を生みそうに思います。

細かくてすみませんが、よろしくお願いします。

Sorry, I am not native english speaker.
If you found funny english, throw pull request or issues.

• MooseX::Types
• Specio
• Type::Tiny
• Types::*

Cloud

• AWS::Lambda
  Queueing
• Amazon::SQS::Simple

How about adding Data::Validator and Params::Validate to Args section ?

• Kelp
• CGI::Application

Just a clarification: In my 25 years of programming experience, I've never seen the acronym "CUI". I'm assuming, based on Getopt::Long, that that section is for libraries that aid development of command-line run programs. If so, you might consider using the common acronym "CLI" (command-line interface) to eliminate confusion.

Homer isn't used by any other module [1] and has only had one real release (it's initial 2014 release).
Class::Tiny on the other hand is used by many modules [2] and is actively maintained.

[1] https://metacpan.org/requires/module/Homer?sort=[[2,1]]&size=200
[2] https://metacpan.org/requires/module/Class::Tiny?sort=[[2,1]]&size=200

I think JSON/XML/YAML is data serialize but not text processing. And markdown is something more like template tech?

めっちゃ使う！

Everyone use them, I think :)

Why don't Dancer/Dancer 2, Catalyst, and Web::Simple appear, but Kossy does?

I would think you would also add additional ones that get a lot of traction, like those I mentioned.

Just weird, really.

This list features a large number of Perl's pet projects, libraries, frameworks, etc.

But I find it lacking in terms of learning resources.

What do you think about including tutorials and listing the best / curated learning materials?

Cheers!
よろしくお願いします！

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

I would like to add a new section for ticket system client libraries, for example RT::Client::REST and BZ::Client (which I am involved with). Others include Net::Zendesk and WebService::Zendesk, ServiceNow::SOAP and ServiceNow::Simple. Without looking, Github bugs, Jira, etc also

I hope this repo to continue into the future, and I expect that it is useful for many beginners.
However, think of this I am very tough project.

If you think it's tough, please seek help from people around.
If I can help it, then I'm will to help It.

Most items already have a description about why they're awesome, but there are some that don't have one yet. The Science/Numerics items for example.

Links are useless without a description so let's add one 💃

App::Ack is awesome module, but this lists does not have the category that fit App::Ack. So, should we make App? Or do you have any other ideas?