Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What would be your stack if you are building an MVP today?

news.ycombinator.com

Post reply on HN
Print view View original

481–490 of 736 posts

Re: Ask HN: What would be your stack if you are building an MVP today?

#481

Post by 0xblinq »

iambateman wrote: post #224

The best stack is the one you know. I guess I’m old school, but I built SimplifyRecipe.com in a few hours using Laravel. That’s not to say that Laravel is better than anything else, but I’m extremely fluent with that ecosystem. I will say, I believe that Laravel or Ruby on Rails would be my favorite starting point for a solo development effort. I spent 1000+ hours working on JavaScript framework development and found…

I’m very fluent in JavaScript (I’ve been a js dev for 10 years) and don’t have that much experience with Laravel yet. I totally agree with what you say.

Even. It being fluent with pho and the ecosystem I find it incredibly more easy to learn and more productive. A lot less foot guns.

Re: Ask HN: What would be your stack if you are building an MVP today?

#482

Post by RangerScience »

Rails if I want a database, Sinatra if I don't.

Ruby just... wants you to be happy while you're using it. And in the long run of life, that matters.

Python wants to be correct, Java wants you to not make mistakes, JS is still figuring itself out, Scala wants to do hard things...

Ruby wants you to be happy.

IMO - There's a lot of very worthwhile follow-on effects of that - everything from libraries (generally) being just that much easier to get going with, to lower-stress teams having better communication, to debates instead of fights (I'm looking at you, PEP572). Ruby is nice so we are nice :)

Re: Ask HN: What would be your stack if you are building an MVP today?

#483

Post by v3ss0n »

throw1234651234 wrote: post #128

MVP should be built on things you will use later. Which is C#/Java/Python, React, and Postgres SQL unless your product has unique needs outside of the traditional space (it's a game, ML project, IoT project, mobile-only app, etc). Firebase is too expensive. Only use case if you have only front end devs. Dynomo/Mongo/Cosmos all do the same niche thing - you don't need a no-SQL db for most apps. 4. Apparently a lot of…

Django/Rails make you a 10x developer. Thats why many who went for "Shiny New Things" are now coming back to Battle Tested frameworks , because nothing compares to those framework in terms of productivity in those shiny nodejs land of inventing wheel .

Re: Ask HN: What would be your stack if you are building an MVP today?

#484

Post by v3ss0n »

awb wrote: post #393

Current word count: * javascript / js: 95 * rails: 89 * django: 86 * postgres / postgresql: 77 * react: 75 * python: 52 * supabase: 52 * elixir: 44 * ts / typescript: 41 * nextjs: 31 * sqlite: 29 * laravel: 28 * vue: 27 * phoenix: 27 * net: 26 * htmx: 23 * node: 23 * html: 20 * github: 20 * tailwind: 18 * rust: 18 * ruby: 18 * aws: 17 * vercel: 16 * prisma: 16 * docker: 16 * graphql: 15 * firebase: 15 * php: 14 * fla…

won't be fair if you don't seperate frontend and backend , because theres no much choice in frontend land other than JavaScript.

Re: Ask HN: What would be your stack if you are building an MVP today?

#485

Post by petercooper »

Towaway69 wrote: post #398

I recently built a Web based MVP and used Node-Red as backend. Frontend was python+flask, postgres and everything dockerized. I've mainly used sinatra and rails for Web apps and always found it difficult to define a clear api on which the frontend was based on (I.e in order later to build ios or android apps off). Using Node-Red forced me to build an api for the frontend, the frontend has no direct contact with postg…

There is so little out there about using Node-Red in this way that I would certainly love to see a writeup of the experience if ever you fancy it!

Re: Ask HN: What would be your stack if you are building an MVP today?

#487

Post by veqq »

nelsonic wrote: post #447
stevenhuang wrote: post #427

Earlier quoted context omitted.

I really wanted to like LiveView but starting from 0 in the Erlang world meant learning a whole bunch of language semantics and idioms. In fact I found it perhaps harder to get started than learning Rust, especially because the language server seemed unable to offer as rich completions compared to Rust. In the end I did manage to understand most of the primitives and concepts in the basic sample app, but it did make…

Totally agree that the learning curve can feel steep learning Functional Programming style, Elixir Syntax and Phoenix framework in one go. But if it’s any consolation, our company has taken people who only JS or Python and got them fully up-to-speed in less than a week using the open/free tutorials we’ve written: https://github.com/dwyl/technology-stack HN feedback very much welcome.

Thanks for this link, I'll give it a go!

Re: Ask HN: What would be your stack if you are building an MVP today?

#488

Post by clusmore »

shpx wrote: post #474
skizm wrote: post #368

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…

Instead of an S3 bucket you can use GitHub Pages. You push stuff to the upstream git repo and it gets deployed. It’s free (you have to pay for GitHub Pro if you don’t want to make the source code publicly available) and comes with Fastly CDN if I recall correctly. You just have to configure your custom domain.

In the case of static HTML/JS/CSS, the webserver will make the source publicly available to your browser anyway, so that's not really an issue.

Re: Ask HN: What would be your stack if you are building an MVP today?

#489

Post by jarek83 »

I'd go old schoolish-ish with Rails with Turbo or Phoenix LiveView (both with PSQL) + maybe some CF Workers.

We see no reason to use extensive front-end as it has only downsides now - it loads longer, it exponentially balloons stack, it requires to hire front-end guys, it is not needed anymore for DOM manipulation.

Re: Ask HN: What would be your stack if you are building an MVP today?

#490

Post by RangerScience »

lelanthran wrote: post #405
caeril wrote: post #276

Earlier quoted context omitted.

This is the correct answer. It's quite shocking how many Django and Laravel answers there are in this thread. Performance and type safety appear to be completely irrelevant to HN. You should take a look at Vite ( https://vitejs.dev/ ) for a Vue development environment, if you haven't already.

> This is the correct answer. It's quite shocking how many Django and Laravel answers there are in this thread. Performance and type safety appear to be completely irrelevant to HN. I was wondering about that actually. Writing code in Python, Rails, etc is painful . A stupidly high percentage of the "unit tests" aren't testing logic at all, they're simply ensuring that incorrect types are handled properly. And then I…

> The devspeed differential between things like C#/Java/Go and Python/PHP/Ruby is large only at the very beginning of your project.

That's a massive hard-no for me. I generally only get faster the longer I get to work with a Ruby codebase, as I get to make it more and more into a DSL for the business situation. I never saw that happen with compiled languages; my speed tended to remain constant after the initial boot.

I know what you're talking about tho - it's the sharp knives + large team problem. The language doesn't maintain a standard of code for you, you (and your team) have to do that yourselves, and if you don't, things can very much get bad. If you're programming in a loosely typed language such that you're effectively having an explosion of types, you're suffering one of the more common downsides to typed languages and you're not using the common upsides to loose typing.

That said - when I'm working, the main difference I've seen with Ruby (and, to a lesser extent Python and JS) vs compiled is the iteration loop, particularly due to having a REPL console. Static languages have definitely made some gains there (looking at you, Scala REPL). Being able to drop into both any debug point in the program, as well as a console loaded with your code, makes certain explorative processes substantially faster.

Post reply on HN