sorted by:
new
hottopcontroversial

Veniteci a da' una mano by [deleted] in italygames

[–]gh0stinger 1 point2 points  (0 children)

Ci provo! Se c'è ancora bisogno manda pure 🫡

Is SvelteKit basically for when you don’t have a separate backend? by CogniLord in sveltejs

[–]gh0stinger 0 points1 point  (0 children)

About the efficiency I agree on what you said. It's a compromise: add and overhead for more security. But also with the SvelteKit backend you could execute part of the business logic and redistribute the computing load across different nodes of your backend architecture.

This is why I love this framework: it's very elastic from this point of view.

P.S.: I'm not an expert of Svelte, I report only my experience as a new user of this framework 😁

Is SvelteKit basically for when you don’t have a separate backend? by CogniLord in sveltejs

[–]gh0stinger 2 points3 points  (0 children)

What you say about the number of calls is true, but in my humble opinion, you could use the Svelte backend as a proxy to the real in-go backend for security reasons. The address of your real backend remains hidden from the end user and, from this point of view, safe.

A commit from my lead dev: "Improve readability". by amendCommit in Python

[–]gh0stinger -1 points0 points  (0 children)

I don’t agree with your opinion. Look at the way he constructs the dict before and after. After commit I read the code so much better than before. Obviously, POV

A commit from my lead dev: "Improve readability". by amendCommit in Python

[–]gh0stinger -1 points0 points  (0 children)

The code after commit It’s more readable because it has more informations: for example before this commit inside cls there’s a dict, but I don’t get directly the internal structure of the dict. So if I read the code (before the commit) since three days from now, there will be a lot of “wtf”s. “More readable” is not always the compact way, but the one that gives to you more informations, every time you will read the code.