Self-awareness disclaimer: These are just my thoughts, I claim no authority. I have not participated in any of the purported fierce interpersonal battles that have occurred.

But I'm not an indifferent bystander. I am a long-time Perl programmer, which simply means that I have been programming in Perl =>> 5 <<= for a long time. ^_^

I do think that there should be a "next-gen" Perl. I do think that it should have a clear designator. (This is largely a sociological argument; programming is a social phenomenon.) Be meaningful as a reference to an important and elegant set of new features, attract new people, keep being awesome.

I understand that there is a tension between the core maintainers (who want to elide unnecessary effort) and people who want Perl "next gen" to have a new label (historical marker, presence identifier). Both sides have a good point. Can we not simply do both ?

Can Perl can't be absolute Perl with a market label that matches "[A-Z0-9]" ?This doesn't need to clutter the code. Let the core maintainers make theirs jobs easier. Let 7 , 8 , 9 , 10 , 11 be possible market-facing labels. I understand the allusion to "42" and I am a D. Adams fan, but I see more advantage in my set:

7: puts the "6" into the past, is a coherent progression, and is a cool prime number 8: puts both "6" _and_ "7" into the past, and can be tilted to represent Infinity 9: a numerical stretch for the label, but goes to Infinity + 1 \^_^ 10: the power of base 10 and other such marketing possibilities 

If I am completely wrong in my musings, please feel free to eli5 -- since this is reddit. ^_^ I confirm that I have indeed been at least 5.

submitted by /u/singe
[link] [comments]

There are a lot of ::Tiny distributions on CPAN that implement the most needed features of whatever (e.g. YAML::Tiny and Module::Build::Tiny) in much smaller and faster to run-time compile modules. It seems that most of the time, accepting the reduced feature set is a good tradeoff for the reduced runtime bloat.

This got me thinking, with how massive CPAN is, containing tons of distributions that implement the same thing in different ways, often resulting in code bloat where Distribution A has dependence B that does Fubar API one way, and Distribution A also has depencency C that doesn't do Fubar API but has a test that needs Dependency D that does Fubar API another way, and so on.

Could we maybe get a "CPAN Tiny" that is a subset of CPAN without all of the massive redundancy bloat? Distributions that go into it can only use Core and/or other "CPAN Tiny" distributions and can not have redundancy. The dependency bloat is major drawback of Perl.

Sometimes to meet one dependency (especially if running tests), well over 20 dependencies with a lot of them having redundant purposes are needed. It's madness. Especially since packagers don't always properly specify runtime dependencies meaning after that big mess is installed, you find you need even more because some dependencies were left out. It's a mess that makes me want to just look for Python solutions.

submitted by /u/AnymooseProphet
[link] [comments]

My wife and have a hobby-level online radio station and we use Logitech Media Server as the backend. As part of what we use we're running a plug-in called Spicefly Sugarcube, which interacts with a "brain" called MusicIP. MusicIP allows music suggestions to be called using an API, which is basically what Sugarcube is doing, and it builds a URL with the very last element being "recipe," which is a filter built into MusicIP that helps shape the direction the songs go.

The issue is I'd like to replace the recipe section of this plug in with a fixed array that cycles through to emulate a radio format clock. I realize that by doing this under the hood I lose the functionality of changing the recipes on the fly, but that's okay.

The program is driven by the plugin.pm file located here:

bitbucket.org/spicefly/sugarcu…

I know nothing about Perl so tried to have ChatGPT alter this to replace the recipe section with a fixed array, It returned the upper part of the file this way, with no other changes, and the plug in won't load like this:

#v6.01 - December 2023

#+===================+

#Licencing Requirements Removed

#Released as Open Source under the GNU General Public License v3.0

#

#In Short Summary

#Complete source code must be made available that includes all changes

#Copyright and license notices must be preserved.

#Contributors provide an express grant of patent rights.

package Plugins::SugarCube::Plugin;

# Define the recipe sequence array

my u/recipe_sequence = ('5s', '4s', '5s', '5s', '4s', '5s', '4s', '5s', '5s', '4s', '5s', '4s', '5s', '5s', '4s', '5s', '5s', '4s');

my $recipe_index = 0;

# Function to get the next recipe in sequence

sub get_next_recipe {

my $recipe = $recipe_sequence[$recipe_index];

$recipe_index = ($recipe_index + 1) % u/recipe_sequence; # Loop back to the start

return $recipe;

}

use base qw(Slim::Plugin::Base);

use strict;

use Slim::Utils::Misc;

use Slim::Utils::Prefs;

use Slim::Utils::Log;

my $log = Slim::Utils::Log->addLogCategory(

{

'category' => 'plugin.sugarcube',

# 'defaultLevel' => 'WARN',

'defaultLevel' => 'DEBUG',

'description' => getDisplayName(),

}

);

So my question is, is this possible, and is the kernel of how to make it work here, or is there a better way to do it? If you look at the original plugin.pm file you'll see how the URL is built, and I really just want the very end of the URL to be &recipe=5s or %recipe=4s depending on the sequence I enter. Any help it appreciated!

submitted by /u/typecrazy789
[link] [comments]

The URI module took a short holiday, but quickly returned. Just for giggles, I'd like to see everyone react (positivily) to u/oalders in the Github issue:

• Can we get 100 reactions?
• Can we get all the reactions (so, thumbs down is really just for completeness)
• Can we star the heck out of the libperl-www repo?

There are people who take care of things so most people never notice when something goes wrong, and from the time I reported this to resolution was three hours (although the issue was already known, I think). That's some pretty good support right there, and we should fête over that.

For what it's worth, GitHub pays attention to these things. When I filed an issue about getting them to think about putting Perl in their Advisory Database, the number of reactions that issue got made them think about it (right now it's a whole process with scheduling dev time, etc). One of the ways to show that Perl is alive is to react to Perl things (um, that deserve it, not bot spam!).

submitted by /u/briandfoy
[link] [comments]

Mo utilities for email.

Changes for 0.02 - 2024-04-26T23:02:53+02:00

• Add tests for error parameters.
• Rewrite the tests so that the functional tests are first and then the errors.