Is it a bad idea if i choose to build my own framework rather than using Laravel for example? I took a look at Laravel and it's a hell of folders, in addition you start coding in laravel not php lol so it has to be taylor's coding style, next, what happens if you use Laravel 12 then Laravel 15 is released, the update won't break the current version?

I need your opinions specially from those who created their own php framework just for the sake of stability and simplicity, i don't need all the bloatware from laravel, I'm using MVC concept and following PSR conventions....

That's perfectly fine. Only reason I won't do it is the te be seen as less professional since many people have the "other people who are better than me already made such stuff, won't do it myself." blanbla. Total loser beta shit. When I started it was common to make a whole webshop for one customer without framework. I'm working lately on a product without a framework and it's super comfy. And when it comes to security - I had a html injection recently. Not in my component, but in a popular template plugin for jinja. I mean, that would've not happened with me. So, on certain level, if you things yourself and keep it simple, it can even be more secure.

So, yes go for it. And only make the stuff YOU NEED. Why would you spent time on i18n and shit.

Also, what I mostly do, I use aiohttp for example. It's like very minimal framework that only does the routing very well and file streaming. I'm sure such frameworks also exist for php.

Edit: I did make my own php frameworks btw! Mvc

Actually, the mvc basics are done in less than a hour if you know it's done. If you render a page in a class for example you can just do $this->Blabla in template and so on. Php is so versatile.

> what happens if you use Laravel 12 then Laravel 15 is released, the update won't break the current version?

- Use php5.6 version mate. Seems like the best solution for you if a framework updating is the biggest problem for you.

I mean I built my own framework. it didn't have a name and it was in node js/js. you learn a bunch and it's easier to use since you built it (I built it before frameworks existed actually...)

and then if you think you hate frameworks now you'll hate them more later

It is a bad idea. I did the same long time ago from the same reason also in PHP. Also I wanted to do it more performant as those files and folders appeared inneficent to me.

What I've made after dozen weeks was an unmaintenable monster that was also slow as fuck compared even to slowest php framework at the time.

At that moment I finally understood the phrase - do not reinvent the wheel. You are not smarter then thousands of people that collectively developed a framework.

If you don't like Laravel, look into Symfony, Laminas, Yii, Phalcon etc and just pick the one that suits you and learn to deal with its shortcomings.

But don't reinvent the wheel - that is if you don't like to throw your time around.

I mean, all the big frameworks were someone's "I'll build my own" at some point

@myss can you share what you did back then in a github repo?

You were based on what when you created it, it shouldn't be slow at all

Mine is similar to laravel without all the laravel packages, I named it X, maybe should have call it Laravel-less haha

@TheBeardedOne totally true, when you take a deep look, a frameware is just a bunch of folders that organize the code (MVC) with PSR convention and all the composer packages that makes things easier....

@SidTheITGuy I'm not sure if you were joking or not, but are you aware that php8. 2 is required to run Laravel 12?

PHP5.6? HAHA you made my day

@SidTheITGuy even going near a machine running that would make me put on a facemask

well, if laravel is your point of reference, even "stabbing yourself in the eyes" seems sane.

if you're stuck with PHP, at least use zend as basis.