[wp-hackers] corrected > coding standards and practicality of use.
halukkaramete at gmail.com
Sat Mar 10 18:57:17 UTC 2012
I appreciate your feedback Scribu.
As you pointed out, we are all guily of doing some reinventing the
wheel. and it turns out that *most* of the time, those efforts (
whatever the subject matter is ) end up with nothing but re-inventing
the wheel. And this practically causes us to waste a lot of time
leading us to think we just made a fool out of ourselves. I do see
that and we should be aware of that when we embark on new
But sometimes, ( I grant you it's rare), some very interesting
results and horizons may be achieved if you were to stick to that
original idea - whatever it was. When you are on the something, that
original idea may lead you to keep on building on it and you may end
up not reinventing the wheel but introducing something different and
something that has appeal. The problem is you can never know if you
were on to something worthwhile unless you bring your idea at least to
a workable level and test it out in the open. It all depends on how
much passion you have towards that thing and how much you believe in
it. The framework I have in mind is not just a bunch of
string/validation/etc functions that wraps some existing functionality
into more specialized versions. That's just the functions library
part. What excites me in getting into this is NOT those 200 functions,
but what I plan on doing with them in the framework I have in mind. -
which I did not want to get into in the original email.
_Your_ input is very valuable to me and I'm super curious to know what
your take is on the following issues;
would you implement the whole thing based on class/object/methods or
would you go for the good old functions route?
and as to "the needle or the haystack first", which argument order
makes more sense to you?
On Sat, Mar 10, 2012 at 9:57 AM, scribu <scribu at gmail.com> wrote:
> blp_rightof() seems like a re-implementation of substr():
> So, I'm inclined to think that instead of taking the time to learn what PHP
> (and WordPress) already offers, you're inventing your own wheel, which will
> make _you_ more productive, but will place a burden on other developers who
> are already familiar with PHP.
> Disclosure: I'm a little bit guilty of this myself, in my own framework:
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers