Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#35143 closed feature request (worksforme)

Make WordPress do the Kessel Run in less than twelve parsecs.

Reported by: frozen-coder's profile frozen-coder Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.6
Component: Cache API Keywords:
Focuses: performance Cc:

Description

While WordPress can be heavily cached and it's performance has been improving year upon year. It still can't do the Kessel Run in less than twelve parsecs.

Some might say it's as bloated as Jabba the Hutt, but any real starship captain, WordPress developer knows it's can certainly keep up with the majority of space cruisers that run WordPress. But having the performance of ship that can do the Kessel Run in less than twelve parsecs still eludes all but the Millennium Falcon.

I'd like to change that.

Attachments (1)

vy67k.jpg (67.2 KB) - added by frozen-coder 10 years ago.
Some encouragement if needed

Download all attachments as: .zip

Change History (6)

@frozen-coder
10 years ago

Some encouragement if needed

#1 @boonebgorges
10 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Like most FLOSS CMSes, WordPress is strictly bound by the laws of theoretical physics.

This is not the force_balance_tags() you are looking for.

#2 @afercia
10 years ago

This ticket would have had a better chance if it mentioned Yoda Conditions.

#3 @michaelarestad
10 years ago

Technically, it already does the Kessel Run in less than twelve parsecs. Since a parsec is a unit of distance and the Kessel Run has been posted about on some WordPress install somewhere, it's accomplished the task in just over 0 parsecs.

Last edited 10 years ago by michaelarestad (previous) (diff)

#4 @jorbin
10 years ago

  • Resolution changed from wontfix to worksforme

Based on Micheal's comment, it is clear that this issue has already been fixed.

#5 @ZaMoose
10 years ago

Fewer than 12 parsecs.

C'mon.

Note: See TracTickets for help on using tickets.