[wp-hackers] 2.next - faster

[Scott johnson]

Faster, imho, involves tradeoffs at this point. My gut just on web apps is
that faster means "look hard at the SQL".  For example I learned TONS about
mysql scaling at Feedster that I think is applicable but it starts to get
specialized like memcache support, write versus read servers, etc.,
seriously playing with your table structure, etc.

Faster in what environment???  I'm happy to contribute ideas but given the
spectrum of sites WP runs on this question has major ramifications

Scott

On 2/6/06, Roy Schestowitz <r at schestowitz.com> wrote:
>
> _____/ On Mon 06 Feb 2006 20:09:59 GMT, [Matt Mullenweg] wrote : \_____
>
> > The last thread about the next version of WP had some interesting
> > ideas in it, but I think the question may have been framed the wrong
> > way. What I'm far more interested in working on for the next version
> > is this:
> >
> > How can we make WordPress simpler in the next release?
> >
> > How can we reduce support requests on the forums?
>
>
> In my opinion, bugs should take precedence, then compatibility (browser,
> platform, and host testing) amd then comes the issue of extensibility
> (simplicity -> user independence).
>
>
> > How can we make it faster?
>
>
> Faster to /use/? Or is it a matter of load handling? Or responsiveness?
> It's
> a rope that you can always pull in different directions.
>
>
> > (To riff on an idea, consider starting a new thread.)
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



--
-------------------------------------------------------
J. Scott Johnson
Ookles launches 2/28/06 - have you signed up yet?
new startup: http://ookles.com/
blog: http://fuzzyblog.com/
podcast: http://techwarstories.com/
fuzzygroup at gmail.com
aim: fuzzygroup
cell: 857 222 6459
-------------------------------------------------------