Re^2: Choosing the right module

I'd add the whole ACME:: namespace to the list of discouraged modules, too. Older PerlMonks will already know this, i newbie might not.

And i'd also put up a warning flag around most of the JSON:: modules. They work fine for most stuff, but can be VERY flaky when it comes to nested JSON structures in combination with Unicode/UTF8. (Why would you have nested JSON structures? Because you can, apparently)

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP

Comment on Re^2: Choosing the right module

Replies are listed 'Best First'.
Re^3: Choosing the right module by eyepopslikeamosquito (Bishop) on Oct 25, 2022 at 02:49 UTC
I'd add the whole ACME:: namespace to the list of discouraged modules Good point! I've updated my response with an Acme link (for Perl users not around in Acme's heyday of the early 2000s) along with a warning: *it is almost certainly a very silly idea to use an Acme module in production code!*	[reply]
Re^4: Choosing the right module by cavac (Vicar) on Oct 25, 2022 at 08:09 UTC
I must admit, i use one module in a sort-of-production system on the dev side to test code. Acme::Umlautify is great for finding Unicode/UTF-8 bugs in your code. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP	[reply]
Re^5: Choosing the right module by eyepopslikeamosquito (Bishop) on Oct 25, 2022 at 10:35 UTC
I was flabbergasted to learn back in 2012 that Acme::EyeDrops was being used in production! ... but also proud that it'd been running successfully for quite a while. Oh, I see you were also involved in that old thread!! And your reply probably provoked me into adding it to Security through Obscurity References. :)	[reply]
Re^6: Choosing the right module by cavac (Vicar) on Oct 27, 2022 at 10:36 UTC
Re^7: Choosing the right module by hippo (Bishop) on Oct 27, 2022 at 11:11 UTC


Problems? Is your data what you think it is?
	PerlMonks