My vision of Maravel ecosystem generated with the help of Gemini and manually fixed in Gimp
I had this vision in my head ever since I copied and started improving Lumen 10 and Laravel 10 — under their MIT license — into Maravel and Maravelith, respectively.
In rally racing, you take a production car and modify it to make it safer, stronger, faster, and more responsive, with better braking, acceleration, and cornering — all within budget constraints.
Of course, you can rent a pre-built car or even buy one, but I’ve always been more of a “do it yourself (DIY) for better value within the same budget” kind of person.
That’s also why I started developing maravel-rest-wizard (and MaravelQL) back in 2021, despite negative feedback suggesting that “magic” like this couldn’t exist — which ironically inspired the “wizard” name.
Using the maravel-rest-wizard library suite is like injecting NOS into the engine while simultaneously sharpening the car’s steering, gear shifting, brakes, suspension, and overall handling during a rally.
But you can only push a car so far before hitting its limits. Eventually, you need to enhance the base car’s core capabilities — things that can’t be fixed just by adding a library.
That was the need that made me create Maravel, Maravelith and their kernel, Maravel-Framework. By doing it, I was able to disable the heavy automated systems set in place by the manufacturer, like ABS, EBD, ESP, TCS, SRS (runtime overhead like reflection, unoptimized execution steps etc.), and replace them with 6 points mounted harneses (failing jobs on memory exhaustion), racing seats (data leak prevention while eager loading), helmet (no dev and test code in production), rollcage (circular dependency prevention), ALS (increased boot speed) and so on and so forth.
Why start from version 10 and not 11 or 12?
- Because 10 was/is stable.
- Because 11 had its API routes disabled by default.
- Because Lumen IS still needed.
- Because LTS IS needed.
- Because 11 takes controll away from the developer just like modern cars.
- Because 10 started to be infected with PHP Attributes read AT RUNTIME via reflection, which by now can be disabled/avoided in maravel-framework.
- Because seasoned developers can decide for themselves how to code.
Top comments (0)