I saw the talk in the stream and I have to disagree that the decline stabilized at a respectable level, because the community is aging and slowly collapsing. (Sorry for being blunt)

In my (not so humble) opinion does "Perl" need a believable long term strategy to escape it's evolutionary dead end and attract "investment".

But I don't see a strategy I only see traditional tactics.

The first (meta) things are to

• Identify what "Perl" means
• Who the target groups are
• What (used to make) makes Perl great
• Which market developments helped promoting Perl
• How to adapt to environmental changes of the last 25 years
• How to open up development for faster prototyping, evolution and competition of stable solutions

For instance:

• Curtis is talking about inlined functions, what's the difference to the old syntactic macro discussion?
• Function signatures are long overdue, but why the hack do we need to wait for a fast implementation? We could start with a slow one like shown in Function::Parameters °, stabilize the API ASAP and implement the fast version afterwards?

I know some core devs will feel insulted now (sorry!), but evolution means that obsolete features have to die.

Sorry for not spreading "Yes, we can!" slogans, positivity is not my mentality.

I prefer direct speech without meaning it as an insult.

At the same time I take funded critic without being insulted.

°) which has it's foundation in a "macro" mechanism!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.