I have been searching on sites like freelancer.com for projects that contain PHP. Some projects give to understand that they are talking about core PHP(but I think they are talking about frameworks), and some projects do talk about core PHP(they mention it specifically). But I look on google and reddit and find a lot of people saying that core PHP is dead. I think I found one article saying that it is relevant and not going anywhere. So my question is, is it okay to learn core PHP and MySQL(and I am not talking about PHP frameworks like Laravel or Symfony)? Especially in terms for freelancing. I am aware of RESTful APIs and using cURL and maybe a front end with vanilla JS. But will I be making a mistake developing core PHP web apps? I find it more easier and more productive when using core PHP compared to Django or Flask for Python or Express for NodeJS. A lot easier. So do any of you still use core PHP either freelancing or for work in 2025?
To be honest, I have no clue. Hence I asked AI out of curiosity (which aligns about my own very tiny experience of PHP)
My main experience is hosting a PHP forum. Lots of dependencies and need constant updates. So maintain may be the weakest point of PHP (IMO).
With a market share of over 70 percent (web sites a great deal by Wordpress), they must have been doing something right. About no 13 of popular languages.
Why Core PHP Is Still Used
Simplicity and Speed: Core PHP allows for rapid prototyping and development without the complexity of frameworks.Hosting and Deployment: PHP is supported by nearly all web hosts, making deployment straightforward.
Ecosystem and Community: A vast ecosystem of libraries, documentation, and community support continues to drive PHPās relevance.
Continuous Evolution: Modern PHP versions (8.x and beyond) bring performance, security, and language improvements, keeping core PHP competitive.
When to Consider Alternatives
Modern Architectures: For real-time apps, microservices, or projects requiring advanced concurrency, languages like Node.js, Go, or Python may be preferable.Enterprise-Scale Projects: Frameworks (Laravel, Symfony) offer structure and features for large, complex applications, but still rely on core PHP principles.
Conclusion
Core PHP is far from obsolete in 2025. It remains a practical, in-demand skill for web development, especially for maintaining legacy systems, building lightweight apps, and understanding the foundations of PHP frameworks. While not as trendy as some newer languages, its massive installed base, ongoing improvements, and strong job market ensure its continued relevance.
All advices you will get, has a touch or religion. There is no black and white. It took me a couple of years to find my language of choice. Testing, chatting and evaluating.
Yeah I had trouble finding some information on this to, not sure to switch or use a framework. But thank you for taking the time to reply anyway! I think I will just switch and see where it takes me if not Iāll just go back to Djangoā¦
I evaluated Python (not Django) a bit and was close to jump on this train. But choosing between PHP and Python, I should stick with Python. As Python is currently more popular than PHP among professionals, especially in fields beyond traditional web development.
You will find that people have been saying this for a very long time. But itās still here in spite of that.
I beleive itās largely an opinion held by some of those who have a different preferred language which they use instead. What they actually mean is: itās dead to them, but assume that to apply to the rest of the world too.
PHP is may be less relevant than it once was, with alternatives becoming more popular.
But so long at they keep maintaining and updating it, and people continue to use it, PHP is alive and well.
Yes I agree. Thank you for you feedback! It helped me reassure myself that core PHP is no dead to everyone.
Question is what you are targeting.
When you want to create websites with Back- and Frontend being in one code, PHP might still be a valid choice even if Python is taking over.
When you want to be able to create web applications, PHP is rarely used. Here need to be able to separate Frontend and Backend completly and there you will find more modern solutions like React and Node Express.
Correct, it may depend upon the context of what you intend to develop.
For many website projects, PHP is still a solid choice.
For Apps and sites with a more interactive experience, there may be better alternatives.
Take a look at this topic:-
In order to use Lavarel or Symphony youāll need to learn the PHP Core first. If you donāt is like a building a house without a base, eventually (sooner rather than later) will collapse.
I am no saying you have to use frameworks, but the core need to be learned.
From a broader perspective, most programming languages donāt die. When I started in the computing industry in 1981, I was programming in COBOL, and I remember colleagues saying it was better to learn something else because that language was going to disappear any minute, replaced by systems that generated code, the āframeworksā of the time. We tried a couple of them, but none worked well enough to replace anyone.
Anyway, 44 years later, COBOL is still being used in large organizations, and as the people who have that knowledge retire, it has become harder to maintain those systems.
That said, when you write that youāre more productive using core PHP compared to other tools, it might be because you need to get more experience with them.
As @SamA74 wrote, a lot of people are saying that a language, any, is dead because it suits them, and some are in some sort of religious war against that or that language for reasons I find hard to understand, but that doesnāt mean it is true. Iāve had customers ask, āWhy do you develop in .NET? Iāve been told itās an obsolete platform and WordPress is better.ā When I asked who told them this, the answer was always another web developer working with WordPress who didnāt know .NET and was trying to get an edge on my offer. By the way, unless asked, I rarely tell my clients what platform Iām using.
Long live to PHP (I am not using it!)
A bit off-topic, but youāre stating something really remarkable and I donāt see any other way to ask this question: With Wordpress you can only make websites and -shops. How do you use .NET for that purpose?
You might want to specify what you mean with web applications, because everything is called an application nowadays. So, a website can be seen as a web application as well.
Of course there are hybrids.
But my general personal view is that the main purpose of a āsiteā is to sell, inform or create opinion. And the purpose of an āappā is more to use in your daily work as a tool.
SEO is important for a site. SEO is not generally relevant for an app.
But I may got it completely wrong?
Usually the answer i get to any of these sorts of questions is one of two things: no answer (aka āI dont knowā) or āits common knowledgeā AKA noone is saying it but its a myth.
There are very different definitions out there. For example, i would define a site as something you visit; an application is something you install.
I have a more diversified definitionā¦
1. Web Sites
Primarily content delivery. Sell, inform, blog or create opinion
- Static or dynamic HTML pages.
- Minimal interaction beyond reading/viewing.
- Often indexed by search engines.
- Focus on SEO and fast load time.
- Often built with some sort of CMS.
2. Web Apps
Application logic runs in the browser and server. No installation needed.
- Often requires login.
- Backend can be API and database.
- SEO is not a big concern.
3. Hybrid Web Site + Web App
Blend of content and functionality. Site + stores, booking etc
- Public parts as site, private/app parts behind login.
- Needs both SEO and interactivity.
- Common in business apps or e-commerce.
4. Hybrid Web App + Web Desktop (PWA)
Web apps that mimics a desktop app but runs in a browser.
- Can either be āinstalledā or run in a browser.
- Uses Service Workers and Web Manifest.
- Bridges the gap between browser and desktop.
5. Native Web Apps
Look and behaves like an old desktop app
- Full access to system APIs via platform bridges (camera, file system etc).
- Deeper offline support, background syncing.
- Launchable like native apps (from home screen or OS menu).
- Installable via App Store / Microsoft Store or outside stores
- Must be signed and on Mac Notarized.
6. Old-Fashioned Installable Applications
Installed on the OS like traditional software from the last century.
- No browser involved.
- Can connect to database as āclient-serverā
- Best for performance-heavy apps.
- Must be signed and on Mac notarized
More or better definitions?
Actually, I started working with Microsoft technology last century. I was a Visual Studio developer in the mid-1990s (for a US private banking institution in Geneva), then I started investigating development on the Internet, in my spare time, what was done using something called HTX/IDC extensions using FrontPage before moving to Visual Interdev and then to .NET.
Over time, Iāve put together my own custom CMS using .NET.
It handles all the backend management for the websites I build, including all interactions with the database. So, whenever I start a new site, Iām essentially using this homemade āframeworkā that Iāve developed.
Great question ā and honestly, youāre not alone in thinking this.
Core PHP is not dead, especially in the freelancing world. While itās true that modern development often leans toward frameworks like Laravel or Symfony (for structure, scalability, and security), there are still tons of small to mid-sized freelance projects that use or require core PHP ā especially maintenance jobs, legacy system upgrades, or quick-and-dirty tools for clients who just want something that works.
Since you already find core PHP more productive and easier to work with, thatās actually a strength ā particularly when paired with solid MySQL knowledge and some understanding of REST APIs and JS. A lot of freelance clients value fast delivery and affordability over trendy tech stacks.
That said, hereās a balanced take:
- Yes, continue learning core PHP, especially if youāre actively picking up gigs that use it.
- Start slowly introducing yourself to Laravel, even just the basics, because some clients may want modern PHP practices down the road.
- Being good with raw PHP gives you deeper understanding, which is great even when you eventually transition into frameworks.
Can we take a moment to justā¦ underline that anything PHP based - Laravel, Symfony, whateverā¦ is built on core PHP.
You cantā¦ have Laravel without core PHP. You canāt have Symfony without core PHP. Like you cant say you use React, but not Javascript.
Frameworks arenāt independent entities. If their root dies, they die too.
You remember learning Math? How you learned to do addition before multiplication before exponents? Same deal.
Imagine learning only exponents, without being able to unwrap it; you can tell me that 2^3 is 8, but not unwind it to show me that 2*2*2, and thus 2+2+2+2 is 8, so that when your exponent doesnt work, you cant tell me what 2+3 is.
Should you continue to learn core PHP? Yes. Why? Because when something breaks in your framework, you work around it in the underlying language.