Comments for Matthew Turland

Comment on Top 10 Posts of 2011 by Matthew Turland

Matthew Turland — Sat, 31 Dec 2011 15:29:33 +0000

@Asho Depends on what you mean by “best.” Building offline-capable web applications seems to be a popular idea these days since most computers have a web browser and code can be written with the same technologies for both online and offline web applications.

On the other hand, while the capabilities of web applications to interact with the client’s operating system are advancing with HTML5, I’m not sure I’d say that they’ve reached the level of capabilities that desktop applications, at least not just yet.

When considering whether to use one technology or the other, you should first and foremost consider the functionality needed in the application you’re building and whether that technology can provide that functionality.

Comment on Top 10 Posts of 2011 by Asho

Asho — Sat, 31 Dec 2011 05:05:21 +0000

What is best?

Building application using PHP GTK or with Client side programming languages???

I am going to build a small app for myself. I am good in PHP but i am not that good in Client side scripting..

Please give me some suggestions.

Comment on PHP Master Published by SitePoint by Matthew Turland

Matthew Turland — Tue, 20 Dec 2011 15:53:27 +0000

@Les Feel free to leave an Amazon review to that effect! ;)

Comment on PHP Master Published by SitePoint by Les

Les — Sat, 22 Oct 2011 16:10:53 +0000

I downloaded the sample chapters and the quality is really excellent, yourself and the other authors have done a good job, particularly for the beginner/intermediate PHP developer however… for someone who has been using PHP for a number of years I
was (personally) expecting a write up on such tools to increase scaling options such as MongoDB?

But as I said, it’s an excellent book (based on sample chapters) IMHO from someone developing PHP for some years for those with
less experience (one or two years).

Out of 5 I give 4 stars :)

Comment on php|tek 2011 Slides by Gobi

Gobi — Fri, 08 Jul 2011 07:10:51 +0000

Hey Matthew,

Thanks for sharing wonderful slides and i agree your comments that PHP will be more versatile if it support desktop apps.

I like to do desktop apps with php since people doing in java,dot net.

Great keep posting

Comment on php|tek 2011 Slides by Matthew Turland

Matthew Turland — Wed, 15 Jun 2011 23:39:03 +0000

PHP wasn’t originally created to be embedded or used in command line scripts either, but it can be now. HTML and the internet itself are good examples of technologies that have evolved well beyond their original intended use cases. PHP desktop development can also be accomplished with the PHP-GTK extension (http://gtk.php.net/). I don’t think desktop development with PHP stands to harm its future; the capability makes it a more versatile language. So, I suppose we’ll have to agree to disagree on that one.

Comment on php|tek 2011 Slides by Saeed Neamati

Saeed Neamati — Sun, 29 May 2011 09:46:02 +0000

I saw your slides. I think creating desktop applications with PHP is not a big deal. I mean, PHP is not aimed for desktop applications and I believe that expecting such a thing can harm PHP’s future.
Whatever, thank you for slides and sharing them.
Also, let’s support CSS3. Read CSS3 Multi-Column Layout Module
Thanks

Comment on “New SPL Features in PHP 5.3″ Hits php|architect by Jonathan Baker

Jonathan Baker — Wed, 11 May 2011 21:29:43 +0000

Great article that I’ll definitely be referencing again in the future as I integrate SPL into more of my own projects.

Comment on PHP_CodeSniffer Article in php|architect by Matthew Turland

Matthew Turland — Fri, 29 Apr 2011 19:06:54 +0000

@Joel I don’t know if I mentioned this in my article, but to my knowledge, the Zend standard bundled with PHPCS is *not* the same as the Zend Framework standard. The only effort I know of to implement a PHPCS standard for ZF is being done by Ben Scholzen (AKA DASPRID), is for ZF2 specifically (I don’t know if there are any differences between the standards for ZF1 and ZF2), and is housed on github here: https://github.com/DASPRiD/ZFCS. As far as choosing an existing coding standard versus creating a new one, there are a few advantages to going with an existing one:

1) Existing standards are likely to have existing tools (like a PHPCS standard) to help you maintain conformance.
2) The decisions involved in creating a new standard are prime targets for bikeshedding. Using an existing one minimizes decisions you have to make, usually just instances where you want to veer from or supplement the standard.
3) If you’re basing your code on an existing project like ZF, it makes your code consistent with that code. While you may never submit a patch to ZF, if you do, you won’t find it being rejected for not conforming to the standard.

Comment on PHP_CodeSniffer Article in php|architect by Joel Clermont

Joel Clermont — Thu, 28 Apr 2011 23:59:15 +0000

When I downloaded the April issue of php|architect today, I jumped right to your article on PHP_CodeSniffer. I’ve just started trying to enforce standards with a remote team, so the timing was perfect. I definitely learned quite a bit more about the internals of how it works, which was much appreciated.

One question I had was why a team or company might decide to create their own standard instead of leveraging one of the more widely used standards included with the tool? I’ve decided to go with the Zend standard since the vast majority of our projects used Zend Framework and it seemed like a natural fit. While I don’t like all of the decisions they’ve made in the coding standard, I still felt a bit more comfortable picking a standard that was widely used. Part of my thought was that as we add team members, there’s a likelihood they may at least be familiar with this standard.

I’d love to hear your thoughts on this topic. Thanks again for the article.