Because I see it too often, I started to compile a list of blog posts about PHP shaming and how irrelevant this is.
Now as expected whenever talking about PHP on the Internet, people are quick to grab their pitchforks and rehash the same classic criticisms of PHP over and over like a mantra. Is it to feel superior? Do they think they're doing a public service? I don't know. What I do know is that they're right to some extent; PHP isn't the best-designed language by any means, largely because it changed organically and incrementally over time. It certainly hasn't stopped PHP from becoming as popular as it has.
Among the many strategic decisions a business needs to make, one which we as developers are involved with is the choice of tech stack—the tools and technologies used for software development. When choosing a backend language, PHP presents its list of strengths and weaknesses; this article examines these from a business perspective.
The reports about the death of PHP are greatly exaggerated. Learn the current PHP status quo and why it is here to stay. Backed by PHP developers from Iflexion, this article will give answers to all the burning questions and help you make up your mind about PHP’s wellbeing once and for all.
PHP is the most widely used language in the world for websites. It is also the most hated. And it’s pure hate. But why do so many developers hate it so much? Today we’re going to the origin of the hate, let’s see if it’s really justified.
Do you remember the popular "PHP: a fractal of bad design" blog post? The first time I read it, I was working in a crappy place with lots of legacy PHP projects. This article got me wondering whether I should just quit and go do something entirely different than programming. Luckily for me I was able to switch jobs shortly thereafter and, more importantly, PHP managed to evolve quite a bit since the 5.* days. Today I'm addressing the people who are either not programming in PHP anymore, or are stuck in legacy projects.
Remember when I ditched Laravel for Golang? Well, after 2 years on Go, our shop applications are powered by PHP again. Why?! You already said it was probably a bad business decision, and then you spend even more time on it?! Well, yeah, several reasons actually.
The fracas over Gutenberg and WordPress is the latest installment in the death of PHP. Take a deep breath everybody. Let’s ignore the trolls and take a look at what Mark Twain, Fidel Castro and PHP have in common — and more to the point, why PHP is still a reasonable choice for startups and small businesses.
I'm trying to wrap my head around why so many developers down PHP development like it is a second class language? Secondly, what are the better alternatives for web development?
What a small web-based business needs, no matter how big you think you will eventually get, is LAMP. For those who don't know, LAMP is an acronym defining your operating system, web server, database, and programming language. In this case, Linux, Apache, MySQL, and PHP. If you are a business oriented founder or senior non-technical leader and you rely on others to advise you on technology, you have likely heard LAMP (specifically the PHP or MySQL part) is passe, not good enough, "too simple," and doesn’t have the performance you need. That is complete nonsense. Facts...
PHP has a bad reputation among many programmers — some of them because of the language’s past mistakes, lack of standardization, security issues, and code styling. That’s why new programmers don’t see PHP as an valid option for developing their projects. For your information, PHP 7 has overcome so many past issues and improved speed. Now PHP is insanely fast and has type hinting for methods and return types, making the language more consistent.
One of the most common questions I’m asked by academees, applicants and even other developers, is, ‘why do you teach PHP?’ or, sometimes even, ‘isn’t PHP a dead language?’
I have several problems working with PHP on a daily basis, but one cannot close their eyes to the changes taking place in the language, community and the ecosystem. There is a long road ahead, but things are getting mature in the land of PHP.
Programming is an amazingly cliquish community. Every developer has a preferred language with philosophical reasoning or performance rankings to back up the choice. I love the variety we have when picking a technology, it keeps the industry exciting and nimble. However, I hate all of the constant derision that many programmers throw at languages they don’t use.
People shitting on PHP isn’t going to go away, it’s a symptom of a few things. PHP has a ridiculously flat learning curve so just about anyone can write code using it, this means a lot of amateurs and ‘get it done’ developers will choose php but...
PHP is one of the most popular language on the internet yet it’s also one of the most hated language thanks to it’s inconsistencies and issues, here is the list of known PHP issues.
It’s well known that PHP is a dead programming language and that its 22-year-old ecosystem is effectively useless now that we have Node and its fancy new asynchronous frameworks. Node’s superiority is evident because everyone knows that single-threaded, asynchronous, programs are better by default.
Slack uses PHP for most of its server-side application logic, which is an unusual choice these days. Why did we choose to build a new project in this language? Should you?
Yes, it’s a horribly designed language (read PHP: a fractal of bad design if there is any doubt in your mind), but by asking this question you’re misunderstanding PHP.