31–40 of 57 posts
None. I'd use Go with standard library templates and plain ol' CSS with a sprinkle of JS. If I was forbidden to use that, I'd probably use Ruby on Rails, Django or something like that.
Is it possible to build “nice” websites like that?
I'd use https://leptos.dev because you can use a fully typed language (Rust) that is super fast in the backend and also in the frontend (see https://krausest.github.io/js-framework-benchmark/2024/table... )
https://mdwdotla.medium.com/using-rust-at-a-startup-a-cautio...
It's not exactly the same as next/remix/kit, but does most of the same stuff and is a delight to work with. I love Svelte as well but SvelteKit, not so much
Next.js, Remix, Astro, and Svelte are another layer of abstraction i dont want to deal with.
None. I just use react and express. Does everything I need. I don't use ORMs, I write my queries in sql files. Deployment I use github actions or jenkins.
The problem with writing raw queries is that you don’t get that sweet sweet type checking
I'd say you almost never need file-based routing, I'd even go that far to say you don't need routing DSLs for backend (just use if statements, performance will be fine without compiled regular expression to match all routes). The fetch API has request and response objects, and URL and URLSearchParams. But in frontend I find react-router-dom very practical. I think they introduced file-based routing in NextJS and co, because it's easier to generate frontend code bundles per route by listing files at build time. Other than that it's just a gimmick.
And as already mentioned ORMs (object-relational mappers) will give you headaches really soon, it's probably not worth it.
You can use Vite for the frontend part which is more lightweight than NextJS and co. I'd say if you have or your team has already build a web application with such full stack framework once you probably know what is needed and what is not needed in frontend with Vite.
- It’s so much easier to manage file-based routing. 1 new page == 1 new file.
- Super flexible about client/server-side code on each page
- It’s concise, and easy to understand. The amount of code in a hello-world project is tiny, but scales up to large apps really nicely
- Easy to share things between client and server, typescript enforces type checking between client/server too
- It’s mature, has a huge community and backed by Vercel.
Some cons… I hope you like JavaScript
VueJS - syntax is very simple, you can start using it by importing it in tag, or you can set up a full dev environment with vite, you can use vue dev tools plugin in chrome. It also has a very simple state management system as well as an event bus, if you want to go that route. and for backend - fastapi. i never found those "all-on-one full stack" frameworks to be usable.
None. I'd use Go with standard library templates and plain ol' CSS with a sprinkle of JS. If I was forbidden to use that, I'd probably use Ruby on Rails, Django or something like that.
I have a side project im working with on with go as the backend. I haven’t worked in any frontend stuff yet, do u have any example repos or websites i can look at and take inspiration from? Is it possible to build “nice” websites like that?
I have made a number of fully profitable (and pretty nice) websites over the last few years using that stack.
I can't point to any specific resource for learning how to do it other than the official docs regarding writing web applications [1]. For me, it all started there and evolved over time.
I'd use https://leptos.dev because you can use a fully typed language (Rust) that is super fast in the backend and also in the frontend (see https://krausest.github.io/js-framework-benchmark/2024/table... )
1) is it like Phoenix LiveView? 2) is it production ready?
2) Yes and no, it really depends on your requirements. We have already created two customer projects with it and are very satisfied (although I personally still prefer the Elm approach to the reactive approach).