Aristotle Pagaltzis

1.10 looks good enough at this point. As far as I’m concerned feel free to proceed with that.

I think the ideal would be to accumulate log messages silently at first and only output them once something noteworthy happens. That way, if nothing interesting happens, nothing is output,...

@kornelski Does this mean that the 1.8.9 beta is as far as native M1 support for the old codebase is ever going to go?

@xsawyerx: and the reason for that is that the `perl` distribution is not installed through a CPAN client. It’s an odd duck in many ways, it’s distributed through the CPAN...

The `blue` isn’t coloured because it’s not inside a rule block. That is correct behaviour – this plugin is syntax-sensitive and doesn’t highlight random pieces of the file. However, the...

> The whole `mysql_enable_utf8` was just experimental and totally broken prior to DBD::mysql 4.042. I used it for 10 years without problems. I’m sure I *would* have had problems if...

Of course many of these CPAN modules will produce broken results when used in any somewhat unusual configuration where the broken design actually matters. But a lot of people don’t...

> But once either perl or any cpan module is updated old `mysql_enable_utf8` (prior to 4.042) can change result of DBD::mysql. *Any* CPAN module? How?

@Grinnz: > If a CPAN module provides a string with a different internal representation, even if it's the same string, previous versions of DBD::mysql will treat it differently. Yeah, but...

> What we learnt from this is that developers do not read documentation nor care about states like "This option is experimental and may change in future versions.". How seriously...