3 ms·
Go for backend. Yes it’s a bit more tedious. But in return you get deadass simple builds and pretty amazing performance. Also tbh it’s not that tedious to write
by moomoo11 3y ago
Go for backend. Yes it’s a bit more tedious. But in return you get deadass simple builds and pretty amazing performance. Also tbh it’s not that tedious to write SQL and tests. I’ve almost always run into issues with ORMs when things get complex.
Use Postgres and embedded db for cache. With SSD and Nvme you can leverage the embedded db for crazy performance. These days you can get a lot of storage space. Swap file and 5gb of space for the db as cache and you’re speeding. Save money and the network call, don’t need Redis.
React or svelte for UI. Don’t use next or any of that bloat. Use vite and lazy loading. If you need SSR don’t use SPA tech, maybe sveltekit would be good. I use sveltekit and react mostly.
For anything else like using sdk I use node if it’s not available for Go.
- aliyfarah 3y agoGo has also been my go to choice for backend for many years, but these days I feel it’s almost like malpractice not to use Typescript. The advantages in productivity & code robustness were just too great. With libraries like zod & trpc, Nextjs api routes/RSC, I don’t see how Go can compete for simple CRUD apps or quick prototyping.
- moomoo11 3y agoPerformance. Especially any real time systems or websocket stuff. TS is awesome and I love Zod, but for a little extra effort I get massive performance boost and lower costs.
- dysoco 3y agoI personally very much prefer Typescript as a language to Go; my biggest gripe with it is the ecosystem is far more complex, vast (in the bad way, when you have 1000 options for everything and nothing completely stablished), fast moving and breaking. You have to cope with things like transpilers, etc. I know this is improving, libraries like React have been #1 for a good while, but even then, they introduce breaking changes constantly.