I was wondering is there anyone uses Clojure or other Lisp languages for these kinds of things…
Ask HN: What would be your stack if you are building an MVP today?
141–150 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#142Earlier quoted context omitted.
I did so last year, and I cannot be happier. My only regret is that I wasn't aware of htmx/hotwire at the time. I went with Vue, and I regret it immensely. Rails is the fastest development platform I've tried so far, it is predictable, well crafted, structured yet flexible. You can't go wrong with it. Every now and then I try something new on a side project or I have to work on some other codebase for my customers, a…
IMHO, part of this is that people have accepted the poor experience of non-realtime applications. But there's a huge UX improvement if the application responds faster than users can input actions. Doesn't matter for all applications but if your users are going to spend significant time inputting data it makes a huge difference. Also IMHO, a flexible type system like Typescript makes development faster than without it…
Simply not true.
I've consulted on multiple teams across products built with Rails. Products that supported hundreds of millions of requests and generated a similar levels of revenue.
Rails scales - programmer productivity, traffic. It scales.
Re: Ask HN: What would be your stack if you are building an MVP today?
#143On top it's probably Tailwind, and if it's just me I'd use Svelte, but if it's more than just me I'd use React.
[0]: https://hasura.io
Re: Ask HN: What would be your stack if you are building an MVP today?
#144Re: Ask HN: What would be your stack if you are building an MVP today?
#145Re: Ask HN: What would be your stack if you are building an MVP today?
#146Personally big on Rails (use it at work every day). But, my last MVP I did with TS/Next/Mantine/Supabase/Vercel. Reasons: - I've been using Rails as an API only, so having to grok views felt like a waste. My React skills made me feel that learning how to make complex views in my backend was a waste of time. - One type of bug I hate is ensuring my API calls have the right schema. With Supabase and TS in the frontend,…
Same, Next.js, Vercel, Prisma, Supabase. I push to my GitHub repo and the site is live and deployed in less than a minute. With the stack you can use the same language, DTOs, libraries, etc.. both server and client side. Server side rendering ensures a graceful handoff between server rendered state and the resulting app state on the client. I’m also using MUI which includes all the components you need for a front end…
Re: Ask HN: What would be your stack if you are building an MVP today?
#147If it is a SaaS 100% Ruby on Rails Why: - has almost everything that I need usually in mature gems - battle tested in production - speed of development
I did so last year, and I cannot be happier. My only regret is that I wasn't aware of htmx/hotwire at the time. I went with Vue, and I regret it immensely. Rails is the fastest development platform I've tried so far, it is predictable, well crafted, structured yet flexible. You can't go wrong with it. Every now and then I try something new on a side project or I have to work on some other codebase for my customers, a…
Re: Ask HN: What would be your stack if you are building an MVP today?
#148There 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.
Re: Ask HN: What would be your stack if you are building an MVP today?
#149Re: Ask HN: What would be your stack if you are building an MVP today?
#150Building an MVP should be done with the tools you’re most comfortable with!