Full stack web developer, interested in all the things, but especially the web, code, design, Linux, OS X, PHP, WordPress, JavaScript & robots.

Tagged: opinion

241: Rapidfire 77 – ShopTalk image/svg+xml

I hate WordPress and every time you talk WordPress. I don’t hate it because of what it is but because of its role and side effects in the web industry. Shouldn’t we as web professionals be the guardians of our industry and try to push to the right direction? And what is the right direction?

I always enjoy listening to Dave and Chris, but I especially enjoyed listening to their conversation about hating on WordPress. Well worth a listen.

A Response To PHP – The Wrong Way image/svg+xml

For anyone who isn’t aware, there is a site call, which is a summary of good (dare I say, best?) practices for writing PHP in 2016.

In addition, there now exists, whose aim is to provide a kind of counterbalance to and what is presently mainstream PHP culture. This article is a rebuttal to the arguments found in

Some people have way too much time on their hands. That said, I did enjoy reading — I’m definitely more aligned with “the wrong way” of thinking about these things.

What is React? image/svg+xml

My reply is usually the same: React.js, Ember and so on, they’re all a blip in the history of the web. They won’t be here in 10 years. Something else will be. I’m not too interested on these talks because they’re tied to a point in time, and I’m interested in what lasts. In my head, it’s akin to fashion vs style.

I’d also like to know more about React and why it receives so much attention, so I’m glad someone of Remy’s stature has asked this question. I’m hoping that there’ll be some good follow-up posts and discussions.

WordPress crusade against technical responsibility image/svg+xml

It is often stressed in WordPress circles that plugins and themes should be compatible to obsolete 5.2 version of PHP programming language.


Because otherwise you will break people’s sites.


Because people still run their sites on PHP 5.2.


Because they don’t know they should update.


Because we won’t tell them.


Because they don’t have to know.

Wait, what?

It took me a long time to grasp that “they don’t have to know” is one of the most important and least obvious WordPress principles.

I don’t agree with that.

I don’t agree with it either, it’s insane. WordPress has more than enough security concerns without the added issues of supporting dead versions of PHP. Bonkers.

BTW, this WP site runs on PHP v7.0.9 and it really wasn’t very difficult to achieve.

AMA with Eric A. Meyer image/svg+xml

I’m not normally interested in AMAs, but I’ve been following Eric A. Meyer for a good number of years so this AMA warranted a read. Anyhow, Eric thoughtfully answers a number of questions around the current state of the web design industry. The questions are mostly related to CSS and JavaScript, so if you’re interested in those topics, it might be worth a look.

360 million reasons to destroy all passwords image/svg+xml

If you think about this for a moment, you’ll realize that your password does not actually matter. The only thing that matters is that you have access to the email address that’s associated with your account.

Thanks to the password reset functionality that every website uses, every website already supports passwordless login — they just don’t call it that.

I’m not sure that password reset systems are as convenient as just entering a password, but maybe that’s the point. The widespread use of passwordless login systems would certainly reduce the problem of users who opt for lazy passwords, such as “password1”, “password2” etc. That said, if the same users were to continue using lazy passwords for their email, they’d still be screwed.

Passwords suck.

Has Design Become Too Hard? image/svg+xml

Digital design is not what it used to be, we say. The fun has gone out of it. An endless deluge of frameworks and technologies has leached the creativity out of what we make and do, and replaced the joy of craft with a hellish treadmill of overly complicated tools to master.

Many of us feel this way, but is it true?

An interesting opinion piece from Jeffrey Zeldman. Turns out it is true, but it doesn’t have to be. Shocker!

Where have all the MacBooks gone at Linux conferences? image/svg+xml

I recently returned from LinuxFest Northwest. One of the most noteworthy things from that event? I saw only one Mac laptop in use by the attendees of the event. One. And, you know what? It wasn’t running Mac OS. It was running Linux.

Earlier this year, I attended Southern California Linux Expo (SCALE). Similar situation there. I saw a good handful of Apple logos glowing here and there, but only a handful. Most laptops seemed to be happily running Linux of one flavor or another.

An interesting post from Bryan Lunduke regarding the decline of MacBook devices at Linux conferences. Why did I find this interesting? Because it conflicts with my own usage. Having spent just short of a year using OS X, I think I’d find it very difficult to switch back to desktop Linux. It would feel like a backwards step.

Also, I wonder how many new MacBook devices were at these events? I’d imagine they are less noticeable as they don’t feature the “glowing” Apple logos.

74% dread WordPress image/svg+xml

So, 74% of people who took part in the 2016 Stack Overflow survey dread the thought of working with WordPress. Why is this? If I had to make some guesses:

  • WordPress is nearly 13 years old. In terms of the web, where technology moves at a rapid pace, that’s pretty old. I would imagine that many younger developers would dread working with “old” stuff, I mean, it’s just not very “cool”.
  • Despite the wording on the WordPress site, “WordPress is web software you can use to create a beautiful website, blog, or app”, it’s still considered by many as just a tool for creating a blog. It’s actually much more than that, but many developers don’t seem to get past the blog thing. Hopefully, the new REST API will help to change that misconception.
  • WordPress has a poor reputation for security. This was made blatantly obvious to me when I attended a penetration testing event and WordPress featured heavily as a target for testing exploits. I don’t know of any developers who enjoy getting hacked.
  • WordPress is written in PHP. Or to rephrase, WordPress is not written in Python, JavaScript, Ruby, insert preferred language here.
  • WordPress has a low barrier to entry and you don’t need any mad coding skillz to use it, hence many rockstar coders consider it a joke.
  • There are thousands of themes and plugins available for WordPress, many of which are of questionable quality.

I’m sure I could go on, but I think you get the point; there are many reasons to dread working with WordPress. But, despite all of the above, I still really enjoy hacking on it.