Re: Sessions and Objects
| From: | Szii | Date: | Sat, 17 Jun 2000 23:44:45 +0000 |
| Subject: | Re: Sessions and Objects | ||
| References: | 1 | Groups: | php.dev php.general |
| Request: | Send a blank email to php-dev+get-21648@lists.php.net to get a copy of this message | ||
Pfft. You just lost a lot of respect with that post.
PHP has a problem. You are saying that "Hey, I
don't have a need for it." Wrong. You have a very
vested interest in the life and death of PHP as you're
doing a whole lot of consulting these days. PHP has
a serious problem, and it's causing a lot of users to
lose a lot of time and patience. Would you prefer that
everyone who needs session objects move away from PHP?
If the answer is no, then perhaps you should consider fixing
PHP or your consulting business will dry up right fast - or at
least take a dive since PHP will be deemed unusable in
a session-requiring application. Once it becomes common
knowledge, so will your book-writing career (at least for PHP.)
Me, it took me 3 weeks to learn PHP. I code in a number of
different languages. Transitioning to ASP or some other
equivalent tech would be less work then me learning PHP's
internals. Despite your "following" and the respect/admiration
of many for PHP (including myself) I'd think you'd have more
interest on a problem that is just now showing it's head and
will only continue to be more of problem.
Zend, as well as yourself has a SERIOUS interest in PHP.
Perhaps someone over there cares enough to fix this thing
since you're obviously too "busy for charity work" on PHP.
It's all about doing what you want, going from point a to point b
in a rapid fashion without sacrificing performance, scalability,
or hassle. If PHP cannot do that, perhaps I need to take some
time and evaluate other tech.
Or perhaps you're right and I need to contribute. Working two jobs
(only one of which is PHP) and trying to prep for my wedding
leaves me PLENTY of time to fix your (PHP dev group's) bugs, right?
I'll look at it tonight, or so. If you (PHP group) did your jobs correctly
then the fix should be minor. If not, then I'm unwilling to proceed from
here without some compensation. It's only fair, right? None of us are
in the charity-consulting business, after all....
-Szii/Mike
Note: As for whining about it, the only way to effect change is to call for
it.
If you feel that we're "whining" about it maybe your should reconsider your
own viewpoint. I've been to one of your PHP informal groups. I went in a
small group, all interested "to hear what the creator of PHP has to say."
We ALL, to the person, came away thinking "what a punk." Your post simply
backs up that observation. You made a good point; "write it or live
without it."
That point could have been made much more tactfully, in the light that the
devteam has no interest in fixing this problem. No fix coming, fine. Say
that.
We heard NOTHING from ANYONE. PHP is no longer about "immediate need."
The business model needed for this product is no longer a single company's
internal plaything. For PHP to live it'll have to compete and you don't
compete
with "immediate need." You compete with innovation, superior product, and
superior turn-around time on fixes. Linuxcare should have taught you THAT
much.
People like MS 'cause at least with MS they trust a name. Linux doesn't have
that branding, that name, and therefore is rather amorphous. Sure MS has
their
many faults but at least MS has something physical behind the name. Linux
doesn't,
and for Linux (or a Linux product) to compete it'll have to work/be that
much better.
I guarantee you that if you keep PHP on an "immediate need" basis that ASP or
something else will destroy you.
At 03:05 PM 6/17/00 -0700, Rasmus Lerdorf wrote:
>Despite popular opinion, none of us are in the charity consulting
>business. Right from day one PHP development has been driven by immediate
>need. I needed a tool to solve a problem. I wrote such a tool. As
>people needed particular features, they added them. If you ask for a
>feature or a change and there is no response, chances are nobody on the
>development team has any need for that feature or change. At this point
>you have two choices. Implement it yourself and submit it, or live
>without it. There is no point in whining about it.
>
>I personally have absolutely no need for session objects, so my motivation
>level for even looking at this issue is close to zero.
>
>-Rasmus
>
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
>For additional commands, e-mail: php-general-help@lists.php.net
>To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>
>