The ward is a factory for the Combine
Category Archives: WordPress
it appears, some captain Nemo can change a ticket milestone in the .org trac (yeah, no Sandbox for you) without leaving any tracks.
congrats on 2.6 release! wander how many more tickets have had their milestone mass shifted this nemo way?
and, yes, I like knitting (it’s almost as good as wanking). for quite a time, didn’t you know?
While you bring up some good visual issues that should be considered I think there are some more fundamental usability issues that need to be addressed first, mainly with regards to flow and interaction. That’s where developments in 1.3 are focused right now.
The prettiest UI in the world that follows every possible convention is still completely unusable if it doesn’t behave in an intuitive manner. People adapt to aesthetics, as Michael has shown, but cognitive disconnects in the interface will bug them forever.
Matt, September 08th, 2004
I couldn’t agree more with this but I’ve finally got to close the following tab (any cure against a multi-tabosis?) which I stumbled upon via Django community news:
I had no idea it was there, it never occurred to me to look in Manage -> Import to convert data already in my blog.
Peter Harkins, 2008-04-17
this guy wrote his own tagegory convertor. sometimes it could be faster than to find something in admin.
not sure if attempt #5 would worth it; an attempt #4 hardly could be considered as a too nice one.
so, yeah b2\cafelog, almost forgotten but nevertheless very important GPLed PHP3 hack, got its page removed from PediWikia. WP Happy wikipidors considered b2\cafelog as “Not notable” enough just because it “cannot stand on its own” despite it’s still being used (because it used to be the default blogware of online control panels provided by the hosts).
funny enough, but since 25 August 2007 b2\cafelog page gets redirected to the article on another PHP3 hack also famously known as WordPress™, which is due to b2 of its mere existence (as you surely know WP is a forked version of b2, that fork was possible primarily because b2 had been released under GPL). even more funny that although WP article mentions b2 as its precursor, but there’s not a single link to its site.
any bets when the article on b2evolution (yet another fairly popular b2\cafelog fork) is going to be merged with WP?
Collin is puzzled:
So, if PHP is currently at 5.2.4 then why the hell are all my hosts still running 4.4.2 or 4.4.3? Am I using shit hosts or are all hosting companies this slow to respond??
the short answer because PHP sucks, the longer one is really simple as well:
- there are too many well-known PHP4 apps (including those that power control panels of hosting providers themselves) which will be borked on PHP5 without a serious code redone to workaround PHP5 backward incompatible changes.
- it’s too much of a maintenance hassle for web hosts to reliably run both PHP4 and PHP5 on a shared hosting.
the only path PHP.net offers is a "Migrating from PHP 4 to PHP 5" appendix document with quite a few of "User Contributed Notes", but you won’t find any documentation neither provided nor merely approved by the PHP.net on how to reliably run both PHP4 and PHP5 on a same box.
in a year I expect the fun times:
PHP 4 end of life announcement
PHP 4 will be discontinued.
The PHP development team hereby announces that support for PHP 4 will continue until the end of this year only. After 2007-12-31 there will be no more releases of PHP 4.4. We will continue to make critical security fixes available on a case-by-case basis until 2008-08-08.
also, in the comments to the same Collin’s post cited above, Trent links to just an exciting PHP 4/5 speed comparison "test" by Barry of Automattic Inc. who found "php5 was 33 % slower than php4!":
Here are the results of a simple apache bench test of a phpinfo page.
[snip: test results here]
From these preliminary tests, php 5.2.2 seems about 33% slower than php 4.4.6. Surprising…
surprising? not at all, never seen such a meaningless test to measure a PHP performance:
hello, ApacheBench is "a command line computer program for measuring the performance of HTTP web servers, in particular the Apache HTTP Server", not that for measuring the performance of PHP itself.
of course, first of all httpd had to be thrown out of the loop and the performance of PHP should be measured using the CLI.
- let alone phpinfo() outputs different stuff on different versions of PHP, will anyone ever be calling this particular function in a production environment like so many times Barry did in his "test"?
can’t imagine any more pointless test than measuring the speed of phpinfo() by the Apache Benchmark tool "to see if upgrading to php 5 is something we want to do on WordPress.com". admittedly, I haven’t profiled WP but phpinfo() is definitely not something like a WP bottleneck!
(nor I suppose an echo() — hat tip to Matt ;-)
Using Safari you cannot see the toolbar editors – either the Rich Text Editor or the basic one. This is not the fault of WordPress.com. It is a fault in Safari in that it uses a non-standard way of rendering the necessary code.
it should be said that wp.com Rich Text Editor (TinyMCE) uses a specific extensions (quirks) of Microsoft® Internet Explorer (since v5.5; in this case even proprietary) and Mozilla Foundation (since v1.3; or to be exact a Gecko) based family browsers.
and, currently, THERE IS NO SUCH A ’standard way of rendering the necessary code.’
therefore, plain truth is so called ’Rich Text Editor’ which describes itself as a cross platform* is available to users of only two mainstream browser family TMCE supports.
oh, and yes, of course: “We have no plans to support Markdown or Textile at present“. apparently, Markdown or Textile users don’t belong wp.com target audience which is probably supposed to be a crowd of a complete dummies who can only push a fancy WYSIWYG buttons, which alas does not even work with a Safari browser.
*) WTF, why the hell browser is platform??? or, even better, why MSIE & Mozilla are the platform and others ain’t one?