Long, things get more complicated. If you browse around the site - you'll see that I've been logging some of the tests/experiments I've been doing. Then I stumbled upon a bunch of example pattern code which is not wrong, but obviously too verbose. The reason, I suppose is that people try to understand, me including, what that pattern means, how to code it, look at examples, then do it. More often than not, they translate form Java/C++/C# - which whoul be fine, in the end it works for those languages, but ,and this is the big point for me, php has features not present in those languages.
It is a dynamically typed language, with a couple of unique features - like the ability to freely convert between strings and symbols (variable and function names). It would be foolish not to use those. In my opinion, we should code the pattern in the language, and more importantly, this helps the understanding of the language. Speaking it better so to say.
Patterns are not self-contained standalone entities. To be honest, I wrote and uploaded this collection, simply because I got pissed off. Then I said to myself, yeah, you can throw tantrums, but can you do better? What is better? How do you see these things implemented? What do you use for your own code? Then a few of the "standard" ones, and a couple of the items on the list - for completeness - they are too short or copies of other patterns to be useful, but I wanted to show that similarity.
Audience? Well, myself and my vanity for starts, a few of my friends with whom we exchange ideas, people like you. I simply don't believe that I should keep knowledge in a cupboard. Even if this helps a little, it's worth it, because it wil bounce back to me.
Long, things get more complicated. If you browse around the site - you'll see that I've been logging some of the tests/experiments I've been doing. Then I stumbled upon a bunch of example pattern code which is not wrong, but obviously too verbose. The reason, I suppose is that people try to understand, me including, what that pattern means, how to code it, look at examples, then do it. More often than not, they translate form Java/C++/C# - which whoul be fine, in the end it works for those languages, but ,and this is the big point for me, php has features not present in those languages.
It is a dynamically typed language, with a couple of unique features - like the ability to freely convert between strings and symbols (variable and function names). It would be foolish not to use those. In my opinion, we should code the pattern in the language, and more importantly, this helps the understanding of the language. Speaking it better so to say.
Patterns are not self-contained standalone entities. To be honest, I wrote and uploaded this collection, simply because I got pissed off. Then I said to myself, yeah, you can throw tantrums, but can you do better? What is better? How do you see these things implemented? What do you use for your own code? Then a few of the "standard" ones, and a couple of the items on the list - for completeness - they are too short or copies of other patterns to be useful, but I wanted to show that similarity.
Audience? Well, myself and my vanity for starts, a few of my friends with whom we exchange ideas, people like you. I simply don't believe that I should keep knowledge in a cupboard. Even if this helps a little, it's worth it, because it wil bounce back to me.