zlacker

[parent] [thread] 4 comments
1. bitbas+(OP)[view] [source] 2025-12-03 16:43:08
It's almost like trying to magically wire up your frontend to the backend through magical functions is a bad idea.
replies(4): >>dizlex+W9 >>beders+9d >>bossyT+Od >>divisi+pO
2. dizlex+W9[view] [source] 2025-12-03 17:24:52
>>bitbas+(OP)
ikr, no way this could have been predicted and warned about for months and months before now.
3. beders+9d[view] [source] 2025-12-03 17:38:25
>>bitbas+(OP)
One could get the impression that the only really really important non-functional requirement for such a thing is to absolutely ensure that you can only call the "good" functions with the "good" payload.
4. bossyT+Od[view] [source] 2025-12-03 17:43:09
>>bitbas+(OP)
CV driven development needs new ideas for resume padding regardless of whether the idea is good or bad. Then you get this
5. divisi+pO[view] [source] 2025-12-03 20:35:47
>>bitbas+(OP)
This reminds me of the recent SvelteKit Remote Functions GH discussion:

> Even in systems that prevent server functions from being declared in client code (such as "use server" in React Server Components), experienced developers can be caught out. We prefer a design that emphasises the public nature of remote functions rather than the fact that they run on the server, and avoids any confusion around lexical scope. [0]

[0] https://github.com/sveltejs/kit/discussions/13897

[go to top]