Why Foliopress WSYIWYG will be PHP5 Only

Thursday, January 3rd, 2008

One of the beta testers for Foliopress WYSIWYG has just complained that Foliopress WYSIWYG is not compatible with PHP4. Apparently PHP5 is still only 6% of the installed PHP base across all webhosts.

That figure should be enough to strike terror into any developer. But that number will change very soon as PHP4 has hit the end of the line.

PHP4 incompatibility started off not as a deliberate decision. Generally I like wider compatibility.

But on serious consideration, I'm not worried about Foliopress WYSIWYG being PHP5 only.

Why not?

  • Our own webhost no longer supports PHP4 (they will put up with it on legacy projects, but strongly discourage it).
  • foliopress kfm posting images right click
    One click image posting from Foliopress WYSIWYG
    via updated KFM right click: this image and caption
    were posted with a single click
    One of the core components in Foliopress WYSIWYG is Kae Verens's brilliant KFM (Kae's File Manager) which we have turned into an advanced image manager (see illustration right). Kae is no longer supporting PHP4 in future development: "PHP4 is a hindrance. My own project has already announced a similar plan - we will no longer be catering to PHP4 after the present release."
  • PHP5 has been available for 3 years now and is thoroughly tested and is at version 5.2.5
  • PHP5 has a lot of improved functionality over PHP4.
  • PHP4 will start to disappear like dry brush this year. In six months there will no longer be PHP4 legacy issues as anybody keeping their online applications up to date will have moved on to PHP5 for one reason or another.
  • Foliopress WYSIWYG target user profile: our users will be running PHP5 for the most part. If not now, in two months. Anyone who cares enough to change the default text editor in their Wordpress or Drupal install is likely the kind of person to be running PHP5 and not PHP4.

Sometimes releasing new software is great. One isn't hindered by legacy issues. We are looking to the future - Foliopress WYSIWYG will be PHP5 only. In any case, Foliopress WYSIWYG is good enough that it's worth upgrading in a heartbeat to PHP5.

Other Discussion: PHP4/PHP5 Compatibility Decisions

Alec Kinnear
By Alec

WordPress | 1 comment

Coding Languages, a developer’s new girlfriend

Thursday, November 29th, 2007

Why all this fascination with Ruby on Rails?

The success of 37signals...these guys have built some cool stuff in very small teams.

But in general I believe that a lot of the coding developers (as opposed to user interface developers such as myself) like trying new languages like some men like trying fresh girlfriends.

Each time a new language comes along they think this might be the one.

For those of us just trying to produce working applications efficiently for clients, switching languages is a waste of time and money.

i.e. we will switch but only if the incentives are enormous or our current technology has badly dated.

Many developers are choosing to remain in PHP. CakePHP is PHP's answer to the Rails framework on Ruby.

Dominican developer Kevin Lloyd has written a succinct list of the reasons to choose CakePHP over RoR:

  1. laziness
  2. speed
  3. shared host support
  4. cost

The big debate about Ruby on Rails versus PHP was set off by Alex Payne of Twitter's complaint about the speed of RoR in an interview:

All the convenience methods and syntactical sugar that makes Rails such a pleasure for coders ends up being absolutely punishing, performance-wise....there shouldn’t be doubt in anybody’s mind at this point that Ruby itself is slow. It’s great that people are hard at work on faster implementations of the language, but right now, it’s tough. If you’re looking to deploy a big web application and you’re language-agnostic, realize that the same operation in Ruby will take less time in Python. All of us working on Twitter are big Ruby fans, but I think it’s worth being frank that this isn’t one of those relativistic language issues. Ruby is slow.

Kevin adds:

I don’t do Web Development for my health or for fun. I design web applications for clients. A lot of my work involves redesign of already existing sites. How do I say to a client: Hey, although your current web host that you’ve prepaid a year for is sufficient for 90% or the stuff you can throw at it, I’m using this new technology and you need to shell out some more $$$ for a host that can handle it.

That's our situation as well. We love web development but it is a means to an end. User interface, front end, user convenience. Of course reliability and security are very important to us as well, but that is more a question of coding practice than coding language.

Read the rest of this entry »
Alec Kinnear
By Alec

WordPress | 3 comments