Conversation

Notices

1. Embed this notice
   Gabe Kangas (gabek@social.gabekangas.com)'s status on Tuesday, 21-Mar-2023 09:14:34 JST Gabe Kangas
   Every time I hear people talk about the future of frontend Javascript frameworks they talk about how it's all going to be about the backend. As somebody who has no interest in writing backends in Javascript this makes me worried about what building for the web is going to look like. Just because I want to use X on the frontend doesn't mean it should limit my options on the backend. I know it's not limited now, but I feel like the writing is on the wall.
   • Embed this notice
     Gabe Kangas (gabek@social.gabekangas.com)'s status on Tuesday, 21-Mar-2023 11:07:48 JST Gabe Kangas

     in reply to

     • ty
     @tychi I guess I don't see why any backend code ever needs to worry about frontend. It never had to. They're two different concerns. The fact that things are moving to "If you want to use React on the frontend you need to render Javascript on the backend" is upsetting to me.
   • Embed this notice
     ty (tychi@merveilles.town)'s status on Tuesday, 21-Mar-2023 11:07:50 JST ty

     in reply to

     @gabek it sounds like a joke, but i am very interested in exploring the idea of “clientless” apps. like, there is obviously still a client, but what if you as a backend engineer didn’t need to worry about frontend code at all and could just call a function in your native tongue, like go.

     it is a half baked idea, but this file i wrote a few years back is the closest thing i have to exploring it.

     https://github.com/tylerchilds/tag/blob/main/examples/todo-list/index.html

     the gist, i broke out client features atomically and then composed scope.