/dev/null
Sign in

Commit

bf35e60

NoFate Technology - Luis V. Penados@nofatetech
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!
QuotingCACaleb Abebe@k4l3b4
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.@garrettw
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 interpreted languages work on end users' computers, so that's why we have the ECMAScript standard, and for another client-side language to be viable, it would need to be adopted as an additional standard, which is naturally a much higher bar than what's needed on the server side.

commit bf35e60