HN Showcase
Back to browse
Maravel Framework 10.63 avoids runtime reflection on DI

Maravel Framework 10.63 avoids runtime reflection on DI

by marius-ciclistu·Feb 17, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●MidNiche GemWizardry
The Take

autowiring:cache now includes constructors, letting Maravel instantiate large class graphs without hitting reflection at runtime and improving cold-starts in complex apps. There's a pragmatic fallback to the old reflection path when contextual bindings or mixed positional/auto-resolved parameters appear — useful for real-world apps, but you need to obey the 'pass constructor args as a list' rule or pay the exception-cost.

Target Audience

Backend developers, PHP/Laravel maintainers, performance-conscious engineering teams

Similar Projects

Developer Tools○Pass

Maravel-Framework 10.62.8 speeds up the console via commands:cache

It precomputes a map of command names and bindings so Artisan doesn't reflect or instantiate every command just to discover its name — a small but practical win for short-lived CLI processes like php artisan queue:work --once. Clever, low-risk optimization for framework forks; valuable if you hit reflection/instantiation overhead, but incremental rather than game-changing.

Niche GemWizardry
marius-ciclistu
104mo ago
Developer Tools○Pass

Updated Maravel Micro-Framework and Maravelith Documentation Available

The commit here is maintenance and polish: docs were updated against Laravel/Lumen 10 and the Templates/Maravelith docs now reflect fixes up to Maravel-Framework 10.62.8, which will matter to anyone already using MaravelQL or the companion libraries. The Medium landing post is fine as an announcement but doesn’t make the case for choosing Maravel over vanilla Lumen/Laravel — still, for Laravel-aligned teams wanting a smaller, template-driven micro-framework, this is a useful refresh.

Niche GemShip It
marius-ciclistu
104mo ago
Developer Tools●●Solid

Skybolt Reflect – C++ header-only runtime reflection library

Macro-driven registration plus a header-only option makes the API trivial to drop into an existing codebase, and the SKYBOLT_REFLECT_EXTERN pattern to force linker inclusion is a nice practical fix for the usual static-init gotcha. It supports member/getter/setter/lambda-backed properties, std::vector and std::optional, property change callbacks, and even calls out DLL-boundary behavior — the README shows concrete examples and a Qt-backed property editor, which makes the library feel engineered for real tooling use rather than being an academic toy.

Niche GemWizardry
matt128
204mo ago