1–10 of 22 posts
Never really bothered to change stacks, but I'd want to know what's something that's faster/cheaper/more scalable/modern
What's your guys' go-to stack?
The fastest is the one you already know. The cheapest is the one you don't use. More scalable requires more complexity. More modern is probably completely useless until it's not modern anymore.
This reminds me of a technical discussion I was involved with regarding picking a language to develop a microservice. We chose Java because the vendor recommended it for easier integration with their service. It turned out they didn't have a Java library, it was just an HTTP API and nothing about the integration was made easier by using Java. The vendor just only worked with Java so that's what they recommend. I was an advocate of C# primarily because that's what we use in our other services.
Anyway, my point is "faster/cheaper/scalable/modern" are marketing terms and you should be wary of anyone selling you a solution based on these.
Personally, my stack is Bottlepy (Python) and VueJs for frontend. Bottlepy is so simple and never changes, you just learn it once (and in a day) and you get stuff done. VueJS is a lot easier to learn than react and it just gets stuff done. React have other advantages such as bigger community, more tools, a bit more structure - but if you're small team I think VueJS shines more.
I used to use Django/Vanilla JS like you by the way :)
Recently went through this discussion with two friends. For now we are doing PocketBase for a simple, extendable BaaS, Flutter for front-ends.
We are starting to drool looking at Elixir, Phoenix, and LiveView from afar. But the learning curve would slow us down for the next MVP that we need to put out on a schedule.
My go-to stack is Node and React. The fastest is the one you already know. The cheapest is the one you don't use. More scalable requires more complexity. More modern is probably completely useless until it's not modern anymore. This reminds me of a technical discussion I was involved with regarding picking a language to develop a microservice. We chose Java because the vendor recommended it for easier integration wit…
I usually prototype this way and then move things to a different stack piece by piece when others get involved, as the interop with Java and JavaScript is great.