Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Arghhhhh!!!!!!



I really don't understand what you are trying to accomplish at PerlMonks. You came here with your templating system saying it is the greatest thing in the world but it is coded poorly and it is too slow and how can it be fixed.

I've said this lots of times, it's not a templating system, its an abstraction method which can be used to build a templating system within which the programmer is completely free to define their own syntax unlike existing templating system where definitions are set in stone. As a result there is only one language involved, Perl, instead of things like TT2 which are one language sandwiched ontop of another language.

What I am trying to accomplish is the sharing of a very neat abstraction system which I have found to bring huge savings of time and effort in everyday work.



You got dozens of responses with good, solid ideas on how to fix the issues and make it faster. Ideas which you ignored and argued against without taking the time to understand them.

I didn't ignore them, I do understand them I just don't agree that they are applicable/suitable, and or I feel they place too many constraints on what is currently a highly dynamic and totally flexible system.



Now you are saying that there was nothing wrong with the code in the first place and that it was always fast enough.

Fast enough is a function of how big your server budget is and the current state of hardware availability. In 2007 when I first came here looking for information on how to improve the processing speed, the efficiency problem was much greater than it is now, and much greater than it will be 4 or 8 years from now.



And you go on below to say that all the people who know how to write efficient code to solve your problem are chained to antiquated ideas, that aren't needed for your "magic" solution.

Sorry! not sorry... I admit my solution is not as efficient as it could be, however I have yet to come across a solution to that problem and I have looked!



And to top it all off, your final word is that your system is the best thing ever, but it is someone else's job to put it on CPAN.

It is pretty awesome, as you would know if you actually understood what it does. As for CPAN, there is no advantage whatsoever to me personally from bundling it up on CPAN because I already have it installed on all my systems. Putting it on CPAN will only help make it easier to share with others, and if no one wants it then why would I bother?



So what have you actually accomplished here other than to annoy people, make them waste their time trying to help you

People need annoying from time to time, keeps them on their toes.



(and belittle them with profanity and insults when they do try to help),

If you can link to any profanity I have uttered, you will also find in direct one to one correspondance the rude monk who provoked it as an equal and opposite reaction. I don't start arguments, but I do give as good as I get.



and fill up the worst nodes lists? You certainly haven't learned anything, not have you contributed in any way.

I've learnt a few things. aXML is my contribution, just because you don't know what it is or why I want to contribute it doesn't mean it has no value.



I just hope that the "more interesting things" you are going to do will be done elsewhere. I for one won't miss you and I doubt anyone else will either

Love you too.


In reply to Re^3: rough start of an axml compiler by Logicus
in thread rough start of an axml compiler by Logicus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (4)
As of 2024-04-20 00:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found