Slashdot Mirror

Are there any programming languages in Latin?

Yes. Perl has a module for that.

So have individuals who create Twitter accounts that look like companies & tweet all about the Olympics (hashtags owned by the IOC!). Bring on the massive work by the IOC for nothing.

Heck use all the supported unicode!

http://unicode-table.com/en/#l...

@cke

Here's some help as to how:
https://metacpan.org/pod/Acme:...
Acme::Unicodify - Convert ASCII text into look-somewhat-alike unicode

LOL at Slashdot not supporting unicode. There's a unicode 'o' between the c and the k so it looks like @coke.

By the way, the Perl 6 way of doing this is:

# read entire file as (Unicode) Str
my $text_contents = slurp "path/to/file";

See: https://docs.perl6.org/routine/slurp.html:

And the same thing can be done in perl 5 with the CPAN module Perl6::Slurp: https://metacpan.org/pod/Perl6::Slurp

I look forward to hearing why Python's chained method call syntax is so much more newbie-friendly than a single, colorfully-named built-in command.

You can always clean up that Perl 5 code using a module such as Path::Tiny:

use Path::Tiny;

my $data = path('file.txt')->slurp;

FTFY.

Cleanup is a noun. Clean up is a verb.

You can always cleanup that Perl 5 code using a module such as Path::Tiny:

use Path::Tiny;

my $data = path('file.txt')->slurp;

Will Moose and the metaobject protocol be implemented in C and integrated into core Perl 5?

Poor "an." Why doesn't "an" get a capital letter?

Look, if you're going to work on re-writing the rules of standard English, do you think you could start on the quoting rules? Trailing punctuation goes inside the quotes, even if it's not part of the quote? Who ever came up with that? And anyway, English title casing rules are easy to deal with... https://metacpan.org/pod/Text:...

Of course the real question is why all the other words do, when No-one Ever Writes Anything Else Like This.

Right. On the internet WE ALL TALK LIKE THIS.

No, plain Perl code is not evil. But here's the perl port of mimic to be evil using Perl: https://metacpan.org/pod/mimic

Perl 6 might be languishing in academia but in the meantime Perl 5 is chugging along nicely with bug fixes released regularly and CPAN content growing week over week. Not to mention Debian and BSD's heavy use of Perl in the base system.

They can have my Pathologically Eclectic Rubbish Lister when they pry it from my cold, dead hands!

Perl 5 have an advanced object system : Moose that provides all OOP features that most others dynamic languages still lack: roles, optional strong typing, type coercion...

This allows to build big applications, well besides just on-shot scripts.

So a few years ago, a bunch of people decided that there was no point in waiting for Perl6, and started back porting the features they liked into Perl5.

And to deal with the whole issue of the Perl6 syntax not being compatible w/ Perl5, they've added 'use feature' where you can tell it which features to enable. (or specify a version number to turn on a whole bunch of things)

So, you want postfix dereferencing? Then use perl 5.20, and enable the feature. (although, I believe it's currently enabled via 'experimental', so people know they're enabling a feature that may change)

Worse multithreading support than Perl.

Perl threading support is fine despite all the whining going on. (See the threads module on metacpan)

Wanna talk about Python threading and the GIL? Or were you just looking for an excuse to bash Perl?

In general, threading makes much more sense on Windows than it does on Linux, because task switching on Linux is optimized for forking, while Windows is optimized for threading. There has been some improvement with newer Linux kernel versions.

For those who don't know, Ingy is a fairly prolific Perl developer [1]. The position he espouses here is quite typical of folks developing modern Perl. The crux of it is that it is better to provide an interface or API for a smaller bit of code that is easily spoken with than one tucked away in the bowels of a massive framework that's tied to a specific language. This position is really a reiteration of Ken Thompson's Rule of Modularity within the Unix Philsophy [2].

To me, this is a noble design goal because it allows developers to use the programming languages they're comfortable with and/or those that best fit the task at hand. I feel that this general principle has been the guiding force behind Google developing Protocol Buffers [3] and Facebook developing Thrift [4]. Software seems easier to build in small pieces that interoperate than if the developers try to build a monolithic and homogenous system all in one go.

It saddens me to see so many folks dismiss this position as a "fad" when it's one of the points to the open source movement.

1. https://metacpan.org/author/INGY
2. https://en.wikipedia.org/wiki/Unix_philosophy
3. https://en.wikipedia.org/wiki/Protocol_Buffers
4. https://en.wikipedia.org/wiki/Apache_Thrift

Last year there were 20,000 surveyed users of NetMason and 9,000 of OpenMason. Today that number has dwindled to just 200 and 90, respectively.

But on the other hand, Mason 2 is out, and it's being actively maintained: Mason. I don't have usage stats for you, but I'd seriously consider using it on new web projects, possibly via the Poet framework.

(You can be the first on the block to start the MVC-backlash. )

Last year there were 20,000 surveyed users of NetMason and 9,000 of OpenMason. Today that number has dwindled to just 200 and 90, respectively.

But on the other hand, Mason 2 is out, and it's being actively maintained: Mason. I don't have usage stats for you, but I'd seriously consider using it on new web projects, possibly via the Poet framework.

(You can be the first on the block to start the MVC-backlash. )

I can think of over 106,000 reasons to use Perl (and by the way, CPAN is still seeing very large numbers of both contributions and contributors).
     

First, I should state that it's really not about the language, it's about the coder. You can build great and crappy things with any language. And every language has it's warts.

That said, the best language I've used in the past 20 years of programming has got to be Modern Perl. Not the chicken scratch Perl you saw 5 or 10 years ago, but Modern Perl. Here are some of the strengths of modern Perl:

It's object system: https://metacpan.org/module/Moose
It's web frameworks, especially Dancer: https://metacpan.org/module/Dancer
It's ORM: https://metacpan.org/module/DBIx::Class
It's package installer: https://metacpan.org/module/App::cpanminus


And so much more. Do yourself a favor and at least have a look at Perl.

First, I should state that it's really not about the language, it's about the coder. You can build great and crappy things with any language. And every language has it's warts.

That said, the best language I've used in the past 20 years of programming has got to be Modern Perl. Not the chicken scratch Perl you saw 5 or 10 years ago, but Modern Perl. Here are some of the strengths of modern Perl:

It's object system: https://metacpan.org/module/Moose
It's web frameworks, especially Dancer: https://metacpan.org/module/Dancer
It's ORM: https://metacpan.org/module/DBIx::Class
It's package installer: https://metacpan.org/module/App::cpanminus


And so much more. Do yourself a favor and at least have a look at Perl.

First, I should state that it's really not about the language, it's about the coder. You can build great and crappy things with any language. And every language has it's warts.

That said, the best language I've used in the past 20 years of programming has got to be Modern Perl. Not the chicken scratch Perl you saw 5 or 10 years ago, but Modern Perl. Here are some of the strengths of modern Perl:

It's object system: https://metacpan.org/module/Moose
It's web frameworks, especially Dancer: https://metacpan.org/module/Dancer
It's ORM: https://metacpan.org/module/DBIx::Class
It's package installer: https://metacpan.org/module/App::cpanminus


And so much more. Do yourself a favor and at least have a look at Perl.

First, I should state that it's really not about the language, it's about the coder. You can build great and crappy things with any language. And every language has it's warts.

That said, the best language I've used in the past 20 years of programming has got to be Modern Perl. Not the chicken scratch Perl you saw 5 or 10 years ago, but Modern Perl. Here are some of the strengths of modern Perl:

It's object system: https://metacpan.org/module/Moose
It's web frameworks, especially Dancer: https://metacpan.org/module/Dancer
It's ORM: https://metacpan.org/module/DBIx::Class
It's package installer: https://metacpan.org/module/App::cpanminus


And so much more. Do yourself a favor and at least have a look at Perl.

It's just a new release that break things, like almost every others...

My point is that the "release early, release really really really often" model of Mojolicious is hard to follow, and sometimes painful.

Also 2.0 being a major release just after 1.99 is quite unexpected as I've seen nothing announcing it (neither in Changes or on the blog.