411–420 of 736 posts
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…
I’ve been working on a side project that aims to provide a really simple UX to spin up full-stack web apps with CI and scalable infra by default. The idea is that you would simply enter a domain name you want to purchase and then the tool would do the following: 1. Purchase the domain name using AWS Route53 (perhaps you’d need to setup an IAM role for the website to access your pre existing AWS acct) 2. Setup fronten…
Combination of LAMP and Go, which is what I have been doing for years. You can knock out a functional MVP in PHP faster than anything else and iterate very quickly. Then spots where performance is an issue work in some Go microservices. This has done my team very well for years.
You can also run a Go FastCGI server to deal with whatever you don’t want to put in PHP (jobs, complex business logic, performance sensitive logic, etc. )
Ecto is the best ORM-ok-fine-it's-not-an-ORM I've ever used and Phoenix is a lovely framework that borrowed a ton from the success of Rails. Deployment used to be a bit of an achilles heal (in that it was uncharacteristically difficult compared to everything else about using it), but that's gotten _so_ much better in recent years. Even more simple if you just use something like Fly.io, which has incredible first-class support for Elixir/Phoenix.
I'm building an MVP solo. Rust for the core application, Elixir for the backend, frontend, API, data layer. Javascript is pretty much non-existent, all client-side interactivity is done by LiveView. Packaged into a podman container and deployed to a Hetzner dedicated server. Storage on PostgreSQL, probably the only thing I would rather not have to manage, but honestly single node is perfectly fine for an MVP. Provisi…
I love Rust and program in it a lot...but I would never use it for an MVP Rust is the tool you use when you are done prototyping, not when you are just beginning
If it's an MVP it doesn't need to be optimized with fancy frameworks until it has active users.
It helps to use the best language that your entire team knows. It severely limits your startup if the team is learning a new language together. Align tech decisions with the capabilities of the team, unless the common denominator is Perl. If the team each has at least 5 years of development/engineer experience and you're going to need to invest in a common language, give Elixir and Phoenix Liveview a try.
HTML, css, js, (maybe jquery and font-awesome if I want to get fancy) and all static files dumped in an S3 bucket for as long as I can get away with it, then django if I need anything more. Not that I think python/django is the "best", but it is what I know and it's got all the batteries included out of the box. I've never made a sufficiently advanced UI that required react/vue/etc. So I still just stick with html/cs…
One difference: I am in the process of stripping out jQuery from old projects. So I would not use it in new projects anymore. Plain JS is just awesome these days. And it is easier to reason about event listeners you have set yourself than wondering "Where does this mouseover event come from? Maybe its from jQueries hover function? Wouldn't that rather use mouseenter?".