231–240 of 736 posts
Why? Mainly because I'm familiar with them, and would be most productive with these.
I'd almost like to reach for Blazor, but if it's at all public-facing, I don't think I can justify using Blazor at this time.
Hhere is quick survey : Regarding backend choices: curl "https://news.ycombinator.com/item?id=34530052" | grep -i Django | wc -l 36 curl "https://news.ycombinator.com/item?id=34530052" | grep -i supabase | wc -l 17 curl "https://news.ycombinator.com/item?id=34530052" | grep -i rails | wc -l 28 curl "https://news.ycombinator.com/item?id=34530052" | grep -i node | wc -l 15 curl "https://news.ycombinator.com/item?id=345…
Backend Choices:
for backend in "Django" "supabase" "rails" "node" "elixir" "phoenix" "fastapi"; do
count=$(curl -s "https://news.ycombinator.com/item?id=34530052" | grep -i "$backend" | wc -l)
echo "$backend: $count"
done
Frontend Choices:
for frontend in "svelte" "React" "htmx"; do
count=$(curl -s "https://news.ycombinator.com/item?id=34530052" | grep -i "$frontend" | wc -l)
echo "$frontend: $count"
doneThere is only one good answer to that, you should use what you already know, if you build an MVP it's to deliver a product, it's not meant to spend 2-3x more time to learn new tech.
At least that's the value I'm getting out of everyone's answers that actually talk about their favourite stack (vs just saying "use what you want" etc)
Node.js, express.js, Typescript for the "central command" server that acts as any client's first port-of-call.
Central command fans out to whatever tech is required for the job. Very typical for me is fanning out to various python Flask servers to do ML/image proc/etc. work or connect to GBQ.
PostgreSQL for persistence because it's pretty much the undisputed pereto-optimal solution: solves 80% of problems with 20% of the effort. Does almost everything you need until you get to the big scales, which by then you can afford to just pay the wizards to do the Cassandra, Dynamo, Redis, haskell, etc. magic
T3 stack - Typescript, TRPC and Tailwind (uses NextJS, Prisma, etc). This is the closest in the JS/TS world to something like Django and end-to-end typesafety can enable you to go blazingly fast. Copilot became pretty good at autogenerating my queries/mutations for me too which was nice.
I'm going to buck the (numerous) trends here and keep it simple at the same time. C# REST APIs on Linux with PostgreSQL and the front-end framework of your choice. I generally stick with Angular.
Earlier quoted context omitted.
At the core there is a custom crawler written in Rust, with the goal of eventually releasing it as an open source standalone application. But everything else, including scheduling the execution of this crawler, and parsing its output, is done on the Elixir monolith.
How does Elixir interacts with the Rust code ?