Commit

34a49e7

Good morning nullers! My time in Brisbane is coming to an end and as usual, I had a blast at #LaraconAU! I plan to make the native desktop app for /dev/null public as soon as I am back home, but before that, I have another thing: Laravex - a Laravel port in Elixir. What’s wrong with PHP? Nothing. Laravel on PHP is excellent. Laravex isn’t a rejection of PHP - it’s for teams that want Laravel’s application shape and DX on the BEAM (OTP, concurrency, supervision, long-lived processes). Why not just use Phoenix? Phoenix is the right default for most Elixir web apps. Laravex exists for a different bet: keep the Laravel mental model (app/, routes/, artisan, Eloquent-shaped models, Blade, middleware groups) instead of adopting Phoenix contexts, *_web, and LiveView as the primary UX. If you want idiomatic Elixir/Phoenix, use Phoenix. What’s the intention of Laravex? Port the Laravel 13 application skeleton plus a thin Illuminate-shaped runtime to Elixir — faithful layout and APIs, not a line-by-line clone of every package. Is it a drop-in Laravel replacement? No. APIs aim to feel familiar so Laravel muscle memory transfers, but this is Elixir: immutability, pattern matching, and OTP replace PHP’s request lifecycle and some Illuminate internals. Expect gaps; see the Limitations wiki page and AGENTS.md. Who is this for? Laravel developers curious about Elixir who don’t want to relearn an entire web stack on day one, and Elixir developers who prefer Laravel’s request/controller/resource style over Phoenix’s conventions. So, if you want Laravel with Elixir instead of PHP, here you go: https://github.com/offskip-dave/laravex
GitHubGitHub - offskip-dave/laravex: An Elixir port of Laravel 13An Elixir port of Laravel 13. Contribute to offskip-dave/laravex development by creating an account on GitHub.

commit 34a49e7