MyApp->config(using_frontend_proxy => 1);
Camelia
The Camelia image is copyright 2009 by Larry Wall. Permission to use
is granted under the Artistic License 2.0, or any subsequent version
of the Artistic License.
The Camelia image is a trademark of Larry Wall, and permission is
granted for non-exclusive use to label anything related to Perl 6,
provided the image is labeled as a trademark when used as a main logo
on a page. (It is not necessary to so label icons, or other casual
uses not related to business.) Such labeling may be done either by
footnote or with a TM mark.
It is recommended that such a TM mark be in a light but visible color
of gray.
Camelia is intended primarily to represent Perl 6, The Language,
not any other aspect of Perl 6 culture, corporate or otherwise.
In particular, various implementations and distributions are free to
use their own logos and/or mascots.
Certain variants are also permissible; since Camelia knows how to
change her wing colors at will, any color scheme (or lack thereof)
in the same pattern is fine. She just happens to like bright colors
most of the time because they make her happy. But she's willing to
blend in where necessary. :)
Going to the other extreme, a textual variant also exists:
»ö«
Many other variants are possible. Have fun. Good taste and positive
connotations are encouraged, but cannot of course be required.
Those of you who think the current design does not reflect good taste
are entitled to your opinion. We will certainly allow you to change
your mind later as you grow younger. :)
From: Larry Wall
Date: March 24, 2009 10:25
Subject: Re: Logo considerations
[...] I think there's a tendency to
go way too abstract in most of these proposals. I want something
with gut appeal on the order of Tux. In particular I want a logo
for Perl 6 that is:
Fun
Cool
Cute
Named
Lively
Punable
Personal
Concrete
Symmetric
Asymmetric
Attractive
Relational
Metamorphic
Decolorizable
Shrinkable to textual icon
Shrinkable to graphical icon
In addition, you can extend just about anything by attaching "P6"
wings to it. I also take it as a given that we want to discourage
misogyny in our community. You of the masculine persuasion should
consider it an opportunity to show off your sensitive side. :)
Hence, Camelia.
Larry
From: Larry Wall
Date: March 25, 2009 11:28
Subject: Re: Logo considerations - 3 logos needed
On Wed, Mar 25, 2009 at 08:54:34AM -0400, __ wrote:
: I think he was offering it as an example and a suggestion. The perl6
: community might favor it out of respect for Larry but I think he went
: out of his way to make it clear that it's the kind of thing he would
: like.
Yes, I went out of my way to indicate that my mind was still open
(a little). However, if you will allow an old geezer to be a wee bit
testy, I would also like to make it clear that I'm a just a little
tired of these "rounds"; more importantly, that I've been mulling
over this particular issue for many years. I didn't just come up
with that list of requirements off the cuff. I'm old enough to have
lots of stuff on my cuff as well.
Also, it's probably mere hubris, but I already consider myself to be a
"professional designer". I know how to take into account the various
factors that a professional designer would take into account when
designing yet another highly original logo that somehow ends up looking
just like every other logo out there. You'll notice that "sterility"
is not on my list of requirements. It was a deliberate omission.
So let me summarize the requirements into a meta-requirement:
The new logo must make Larry at least as happy as Camelia does.
That is the extent to which my mind is still open... :-)
Larry
my $caller_method_with_namespace = (caller(0))[3];
my ($method) = $caller_method_with_namespace =~ /([^::]*)$/;
Use the init_arg
attribute configuration (see "Constructor parameters" in Moose::Manual::Attributes):
package SOD::KuuAnalyze::ProdId;
use Moose;
has 'users' => (
isa => 'ArrayRef[Str]', is => "ro",
init_arg => undef, # do not allow in constructor
);
1;
$randInt = Math::NumberCruncher::RandInt(10,50);
Returns a random integer between the two number passed to the function, inclusive. With no parameters passed, the function returns either 0 or 1.
These days, public discussion can seem really difficult and painful. Trolls making deliberately destructive comments, exaggerated dramatic statements and even abuse seems common, whether the discussion is online or in-person.
Many of us have experienced real pain and suffering in these discussions. How can we stop it?
Individuals and communities can take action to keep honest and valuable discussions from degenerating into useless drama. In this talk, Ruth shares ideas for managing your own perceptions of what is happening in a rancorous conversation. She shares a framework that enables you and your communities to vaccinate your discussions against trolls and drama, reclaiming useful public discourse for us all.
The Perl Foundation (TPF) is passionate about helping our software communities flourish.
Jump in a time machine and let's see some suggestions for how we can improve Perl, Raku and TPF's branding.
use utf8;
does not enable Unicode output - it enables you to type Unicode in your program. Add this to the program, before your print()
statement:
binmode(STDOUT, ":utf8");
See if that helps. That should make STDOUT
output in UTF-8 instead of ordinary ASCII.
package Foo {
use Moo;
has a => (is => "ro");
has b => (is => "ro");
}
my $bar = Foo->new(a => 42);
# Print only 'a'
say $_ for keys %{ $bar }
# Print all attributes
say $_ for keys( %{
'Moo'->_constructor_maker_for('Foo')->all_attribute_specs
});
# don't forget this if you want to output utf8 characters
binmode(STDOUT, ":utf8");
# don't forget this if you want to output utf8 characters
binmode(STDOUT, ":utf8");
This blog post describes a model that we found useful for talking about CPAN dependencies and reverse dependencies at the QA Hackathon. At the head of the river is Perl itself with the core modules. The river flows into the sea, which contains all distributions that aren't used by any other distribution. Other distributions sit somewhere along the river, their position determined by their reverse dependencies. This post introduces the core concepts, but nothing more.
Remember the saying from Perl-people? "We suck at marketing". Well, not all of us. Some of us are rather good at marketing. Some well-known Perl heroes are good at what they do and good at promoting that, and promoting Perl at the same time. I do my bit and it seems to be appreciated every now and then. I will tell you what I do for marketing Perl, what I think the effect of that is, and how easy it is for you to join me to show other people how awesome Perl is. I will mention some of my Perl heroes, YAPC's, Fosdem, workshops, PM meetings, tuits, buttons, stickers, and more.
A persistent key-value store for fast storage environments.
RocksDB is an embeddable persistent key-value store for fast storage.
UnQLite is a in-process software library which implements a self-contained, serverless, zero-configuration, transactional NoSQL database engine. UnQLite is a document store database similar to MongoDB, Redis, CouchDB etc. as well a standard Key/Value store similar to BerkeleyDB, LevelDB, etc.
UnQLite is an embedded NoSQL (Key/Value store and Document-store) database engine. Unlike most other NoSQL databases, UnQLite does not have a separate server process. UnQLite reads and writes directly to ordinary disk files. A complete database with multiple collections, is contained in a single disk file. The database file format is cross-platform, you can freely copy a database between 32-bit and 64-bit systems or between big-endian and little-endian architectures. UnQLite features includes:
Column-store features
When your database grows into millions of records spread over lots of tables and used in business or science data warehouse applications, you really want a column-store database management system.
MonetDB innovates at all layers of a DBMS, e.g. a storage model based on vertical fragmentation, a modern CPU-tuned query execution architecture, automatic and self-tuning indexes, run-time query optimization, and a modular software architecture.
# Loading from __DATA__
my @hosts = <DATA>;
chomp @hosts;
# => ["coucou.com", "coco.com", "cici.com", "chichi.com", "cucu.com", "cece.com" ]
__DATA__
coucou.com
coco.com
cici.com
chichi.com
cucu.com
cece.com
# Loading from file ./hosts
use Mojo::File;
my $file = Mojo::File->new('hosts');
my @hosts = grep { $_ ne '' } grep { $_ !~ m/^#/ } split '\n', $file->slurp;
# => ["coucou.com", "coco.com", "cici.com", "chichi.com", "cucu.com", "cece.com" ]
# ./hosts
# Deals with comments and blank lines
coucou.com
coco.com
# More hosts
cici.com
chichi.com
cucu.com
cece.com
Three weird tricks to make your object-oriented codemore encapsulated, more reusable, and more maintainable.