Language Selection

English French German Italian Portuguese Spanish

Linux is Best for PHP Development

Filed under
Software

It's been a few years since I echo'd my first HELLO WORLD script. PHP has developed and evolved and yes, it has changed since it was first devised as little Perl extensions on Rasmus Lerdorf's localhost. Still, for a little Home Page script, it has grown into something that is now used on over 200 million websites around the world. That is nothing to be scoffed at. In this article we'll discuss the two most important things we should try to remember when developing in PHP.

While we all know that PHP is not perfect, I seriously doubt that anything can be done about that right away. That said, there are not many languages that can run pretty much the same in version 6 as they could in version 3 (Yes, I did read what I just said, and I have an old php3 script that still runs on PHP 5, and should run on PHP 6, ok? Ok.) Development in PHP is always a tricky road to follow considering that you are developing something that will not usually run on a server that you have real control over--unless you are lucky enough to be able to afford your own server--and be viewed on a multitude of browsers that all display elements differently, anywhere in the world, over a connection that is usually shakey at best.

Knowing all of this, what are the two most important things we should we try to remember when developing in PHP?

Rest Here




re: PHP Dev

Hopefully the guy writes code better then he does articles.

The guy's premise is that Linux is better for dev work. As his proof, he rattles on about mixed case differences between Linux and Window platforms. Then he throws in that your code is most likely to land on a *Nix box. Really?

That's it? One reason - and it's case handling?

With such underwhelming arguments it's safe to say I'm not convinced (especially since we do pretty much ALL our dev work on Window workstations for code that run's on Linux clusters - why you ask? - because the IDE, Dev, and Debug tools are WAY way WaY wAy WAy waY Way better).

Plus it's a moot point anyways because you can always run your target server in a VM on whatever platform you dev on.

It's "WAY way WaY wAy WAy waY Way better"?

OK, I'm convinced. Who can repute such a strong argument.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

systemd and DebConf16

  • systemd backport of v230 available for Debian/jessie
    At DebConf 16 I was working on a systemd backport for Debian/jessie. Results are officially available via the Debian archive now. In Debian jessie we have systemd v215 (which originally dates back to 2014-07-03 upstream-wise, plus changes + fixes from pkg-systemd folks of course). Now via Debian backports you have the option to update systemd to a very recent version: v230. If you have jessie-backports enabled it’s just an `apt install systemd -t jessie-backports` away. For the upstream changes between v215 and v230 see upstream’s NEWS file for list of changes. (Actually the systemd backport is available since 2016-07-19 for amd64, arm64 + armhf, though for mips, mipsel, powerpc, ppc64el + s390x we had to fight against GCC ICEs when compiling on/for Debian/jessie and for i386 architecture the systemd test-suite identified broken O_TMPFILE permission handling.)
  • DebConf16 low resolution videos
    If you go to the Debian video archive, you will notice the appearance of an "lq" directory in the debconf16 subdirectory of the archive. This directory contains low-resolution re-encodings of the same videos that are available in the toplevel.

Linux Kernel

Red Hat News

Android Leftovers