Garrett W.: “I hadn't seen that one, but I am aware of php-wasm -- and wi…”

NoFate Technology - Luis V. Penados @nofatetech6ha6841c1

yeah! the 'one language' promise, that was needed because of bad communication between front and back teams probably, and is not a problem with Laravel/Inertia :) ..and I say well lets enable more languages for the frontend to balance it out!

CACaleb Abebe@k4l3b46h

1 reason might be because it allows frontend developers to not have to use another language to build backends, so basically it's a frontend dev's way of claiming to be a fullstack dev🙂

Garrett W.@garrettw5hbf35e60

I truly understand the appeal of that idea, but unfortunately it's a much bigger challenge. One person can host a website using the language of their choice, because at the end of the day, it speaks HTTP over the wire, which is a standard. But one person cannot control what…

NoFate Technology - Luis V. Penados @nofatetech5h040e8cb

Have you seen https://pyscript.net for example? I would totally use it, maybe we can integrate it with laravel/inertia hehe, and i would love to see option for _all_ languages for front.

Pyscript.netPyscript.netPyScript is a platform for Python in the browser.

Garrett W.@garrettw5h

I hadn't seen that one, but I am aware of php-wasm -- and without making individual languages themselves into full-fledged standards like ES, I think WASM is going to be the only way forward. That said, it's not really equivalent.

4:41 PM · Oct 24, 2026commit fb5805d

NoFate Technology - Luis V. Penados @nofatetechquoted5h

Yeah, its the bits of wisdom coming out in the only-js crazyness, but at least it gets us thinking of the better world, wasm doesn't sound so bad all of a sudden :)

Commit