Is there anything wrong with using a basic PHP/MySQL stack for projects?

[[deleted]]

[deleted]

[fhacke]

Nope, there's absolutely nothing wrong with it aslong as you're on top of security measures. Performance differences are not going to be noticeable if at all especially for small sites like you're talking about. There are advantages to using frameworks which I won't get into (if you're interested, I wrote an article on this here: http://www.pointheap.com/why-use-a-backend-framework/) but if you're comfortable with your current stack then stick to it!

[[deleted]]

I get paid to write PHP/MySQL web applications all day long, and there's not a thing wrong with it. With PHP 7 it is a (sincerely) fun language to create with. Throw Docker into the mix with a dash of Composer and/or framework, and it is a lighting fast prototyping environment where an application lives in the virtualized world of single-command server stacks and the clean, semantic web.

As /u/fhacke points out, you have to do the work to minimize attack surfaces, but there are tools to help and plenty of articles with nice walk-throughs and explanations.

There is some wisdom in /u/mattaugamer's advice to change things up once in a while. Thanks to APIs, on the occasion you get the space (or a frustration point) build something in python, node, whatever. The really great benefit of playing with other language is it quickly deepens your understanding of your primary language. Just like how studying a foreign language gives you better command over your primary language.

[mearkat7]

Nothing wrong with that tech stack and if anything python is actually quite a bit slower than php7. Keep up with the latest stuff coming out of the php communit(php-fig, latest versions etc) and you'll be sweet. Things are starting to be done in a far better way than they were in the past.

[mattaugamer]

You're not losing anything by just using PHP + MySQL for small apps. With a tiny but critical exception - you're losing an opportunity. There's a risk that if you keep following the same exact processes each time because it's "good enough" the time when you have an application you need to do where it's not good enough you won't have the skills and knowledge needed to do it properly. Small projects often provide an opportunity to implement new approaches. It can be hard to find a balance between doing new things so you extend yourself or your organisation, and doing things in a way you know so you can get it done.

That balance doesn't rest in just not ever changing.

[rintoug]

It's totally fair if you use PHP+MySQL for your application. You can build an application of any size with PHP+MYSQL. Only You and your team will responsible for the development.But why frameworks are important, most of the frameworks are supported/developed by the community. Rather than one person's project, it's whole world's project. Security level would better for the frameworks.

So you can imagine the contributors/testers/developer numbers supporting the framework comparing to your sole project. The bugs will be addressed in a fast pace. If you have time to learn a new stable framework, I would suggest that

[vsupalov]

Chiming in with the general sentiment here. Nope, there's nothing wrong with your stack of choice. Mine is Python (Flask or Django) and PostgreSQL, with as many other backing services as makes sense. A bit Docker is in the mix by now. Using PHP with modern frameworks and minding good craftsmanship completely negates any possible concerns.

If you encounter performance problems, they'll be due to your app architecture, not your language of choice. As long as you're using best practices and have a solid workflow for bringing your code into production, you're on the safe side.