Earlier quoted context omitted.
The biggest benefit to Django, in my opinion, is the orm and admin tooling. Being able to fix things in your app without having to open a repl or open a database tool is absolutely killer.
I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately. Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why t…
Ask HN: What would be your stack if you are building an MVP today?
361–370 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#362Earlier quoted context omitted.
That's exactly what I do - I build a monolith using the self-contained deployment feature and zip it up to the server to run. The management of certificates, configuration, etc. is built directly into any product I work on. Outsourcing this stuff to IIS, et. al. is exactly how you wind up hating all of this tech in the first place. Prerequisites are zero if you do this right. I can take a blank EC2 server, copy the b…
How do you setup your webserver. This is the most challenging part for me. Here's my process. Build locally, publish, upload to server, dotnet run... Now what?
Re: Ask HN: What would be your stack if you are building an MVP today?
#363Earlier 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 ?
Re: Ask HN: What would be your stack if you are building an MVP today?
#364Definitely old schools. I am building a MVP right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why. 1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want "fully built out" services, then we have a plethora of free and paid templ…
It’s funny that only in our industry “time tested”/“battle tested” is called old school and frowned upon. No wonder we see software bloat everywhere.
Re: Ask HN: What would be your stack if you are building an MVP today?
#365Of course it heavily depends on what your actually building.
I prefer to do most of my logic in the frontend and Flutter is great for this.
Re: Ask HN: What would be your stack if you are building an MVP today?
#366Could deploy to a VPS or AppEngine. Can run it locally.
Re: Ask HN: What would be your stack if you are building an MVP today?
#367Earlier quoted context omitted.
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…
> part of this is that people have accepted the poor experience of non-realtime applications my experience has taught me the exact opposite: people have accepted the poor experience of real time applications (client side crashes that bring down the entire page, half-baked routing that is essentially just rebuilding the browser navigator, inconsistent client vs server rendering processes). developers tend to completel…
People complain about that stuff all the time.
>stick their head in the sand when these issues are occurring. there's complete classes of problems that simply go away when you're not building an SPA.
Well, yes. If you don't actually build a real time application you won't get the benefits of a real time application.
>in the long run, yes, but in the short term you're probably not going to get your mvp out faster because you chose TS
Once there's even a moderate level of complexity (i.e. 2-5 devs for 1+ months) the type system helps you catch issues. Even if it only saves you one 4 hour debugging session you come out ahead.
That assumes you sit down and write out your MVP without any significant refactoring. If you do have to make changes then TS will save you significant time there.
It also assumes that you're not writing tests that duplicate what a type system does. If you do write those tests then again I think you're slower.
Rails does have the advantage of there generally being one "Rails way" of doing things. That can short circuit a lot of design discussions and other sorts of bikeshedding. But you can also just not do that and, IMHO, come out better.
Re: Ask HN: What would be your stack if you are building an MVP today?
#368Semi-related side note: I do use TS/react in my 9-5, but the more I use it professionally, the more I'm convinced there is no need for it outside of trying to get a job, IMO.
Re: Ask HN: What would be your stack if you are building an MVP today?
#369Having said that, the answer is Python+SQLite.