On Our Radar: PHP 7 Controversy and Dependency Injection

Share this article

Over the past eight months, we’ve enjoyed bringing to you the latest and greatest updates from the world of web development. But we’ve also noticed that discussions among web professionals on our forums have not been receiving nearly enough exposure as they should.

To change things up a bit, we’re going to start bringing to you items and information from those discussions that have caught our attention. Sometimes these discussions will be useful and interesting, and sometimes they may be challenging or insightful. Either way, they’re likely to bring new information to light that you haven’t come across before, and will help to provide insight and perspective on topics you’re interested in.

So let’s get started!

PHP 7 Controversy

The PHP 7 Revolution article brought on a vast amount of discussion in our forums. The article covered information on how PHP is skipping 5.7 and moving directly to PHP 7, that the new version will give us return types, and that the removal of PHP4-style constructors is certainly going to be a controversial change. Tony Marstron controversially pleaded: please don’t break our language.

An excellent response from rrcatto:

“If a business needs to run a piece of code, to me this also implies actively maintaining it. … If the language changes, code must also change. That is the only dev paradigm that makes sense, because progress is a good thing and we should not hinder it.”

The conversation continued at length, with great insights provided.

Dependency Injection is Evil

A highly controversial topic — dependency injection is evil — also came up in the discussion on PHP 7, and was (usefully) moved to a separate thread for examination.

It seems that some of Tony’s articles voice opinions that are controversial and oppose the norm, and this one on dependency injection really struck a nerve with some.

Jeff Mott summarized the Pro case quite well, with:

“Dependency injection makes code more flexible and more decoupled.”

Others too attempted to examine the reasons why Dependency Injection may be bad, to find out whether any of the claims had much ground to stand on. Another key point was also great to see:

“[R]equirements change all the time, and therefore software changes all the time. Today, an important factor that makes an architecture good or bad is how adaptable it is to change.”

While it can be tempting for dissenting opinions to color how you feel about that person, it’s vital for such conflicts to occur for it is only by shining the light of inquiry on the problem space of controversial issues that we can find out where we stand on the topic, and find the most suitable solutions.

It’s also illuminating how even though disagreement occurs on the techniques that are used, rarely do the parties involved resort to personal attacks. Instead, we see an examination of the ideas being presented, which is something that we can all aspire to.

Your thoughts?

That’s all from us this week. What do you think about the change of focus? Could we do with more threads being examined? Are there any important threads that we could do with examining next week? We would love to hear your thoughts.

Paul WilkinsPaul Wilkins
View Author

I'm a web developer living in Christchurch (thanks for all the quakes) where JavaScript is my forte. When off the computer I volunteer down at the local community centre, or enjoy playing tabletop games such as Carcassonne or Stone Age with friends.

dependency injectiondiscourseDiscussionforumson our radar
Share this article
Read Next
Get the freshest news and resources for developers, designers and digital creators in your inbox each week
Loading form