Tonight I kicked-off the "Er.pm" brand with the HTTP::Server::Simple::Er module. I don't know if I'll be able to build the brand to the level of Adam's "::Tiny", but we'll see.
In any case, I seem to always want something more from an API and I tend to get deadlocked thinking of names instead of writing code. Plus, it amuses me that "Eric's Rewrite|Redesign" neatly abbreviates to "Er" and acts as a pun suffix
And, it is also rather "Er" in some cases. That is, the "::Er" modules are likely to be just about the opposite of "::Tiny", because I usually want more cowbell and I probably expect that you're running a perl which was released in the last 5 years with a working toolchain.
It also might stand for "Experimental Release" or "Emphasis on Rabbit". If we had a tidier way to run forked API's in our namespace, we wouldn't have to talk about what it means.
Anyway, that's one more distraction^Wdependency down, and only about 6 to go before the task at hand is actually done...
It's a fine idea (Score:2)
Re: (Score:1)
Are there criteria for it?
Or is it just "my extensions to stuff"...
Re: criteria? (Score:1)
In a couple of the cases on my todo list, the original API simply grates on me and the only way forward is a complete rewrite.
So, usually it is a sort of "I wish it had been done this way to start with" or "what if..." and like I said: probably an experiment.
Looking forward to... (Score:1)