What tech stack would you use for your next small/middle project?

Question

getting out from the big company where we used MS tech stack for years, with some modules using .NET MVC and the others are using even older asp.net webforms... The API was written in SOAP :)... I want some restart and looking forward for kind advices, since what I see out there its all about backend API (nodejs, or whatever stack) + frontend with React/Next, Angular or Vue... ? thanks

d3nj4l · Accepted Answer

Phoenix! Elixir is a lovely language with genuinely useful language features you'll miss in other languages (like with and partial function defs), Phoenix is elegant and once the immutable model clicks with you you'll wonder why you ever lived without it, and Ecto is a brilliant DB access layer that avoids many of the pitfalls of ORMs. All that and you'll be as productive as you're in any ol' MVC framework, great tooling in VS Code, and you get LiveView, which makes JS SPA frameworks redundant unless you really need the SPA interactivity. Just try it out.E: I know with is elixir's version of do notation. Please don't badger me about that.

ozzythecat · Answer

Rather than picking a &ldquo;stack&rdquo;, I would encourage starting with what&rsquo;s the problem being solved, for who, and then figure out the tech from there.It sounds like your area is specifically on a service and web front end. Can you describe what you&rsquo;re wanting to do, even at a very high level?Node, React, etc. this might all just be overkill.

mikewarot · Answer

Lazarus/Free Pascal - It's all I use these days. It avoids the hassle of .NET, produces small executables, and just works.If I had to do something on the web, I'd use the LAMP stack at my ISP.

midrus · Answer

Laravel, and the TALL stack. Maybe also Unpoly for certain parts.I'd avoid SPAs as hell. Just a total waste of my time/money and end user's resources. If employer wants to use his money for SPAs, I'd build them happily.

What tech stack would you use for your next small/middle project?

Lazarus/Free Pascal - It's all I use these days. It avoids the hassle of .NET, produces small executables, and just works.
If I had to do something on the web, I'd use the LAMP stack at my ISP.

Laravel, and the TALL stack. Maybe also Unpoly for certain parts.
I'd avoid SPAs as hell. Just a total waste of my time/money and end user's resources. If employer wants to use his money for SPAs, I'd build them happily.