Bash, Emacs, C.
Deployment: GitHub Actions and Pages
No databases, hashtables are good enough and around 1000x easier and faster.
Ask HN: What is your preferred/most commonly used stack and why?
31–40 of 71 posts
Re: Ask HN: What is your preferred/most commonly used stack and why?
#32Ruby on Rails, Hotwire, StimulusJS, SCSS, slim, Postgres, Redis, on Heroku or Render. Solid, mature, innovative, productive and pleasant to work with. 80% of SPA speed and reactivity with 5% of the effort. If I need complicated interactivity in a specific area, I use vuejs.
+1
:)
Re: Ask HN: What is your preferred/most commonly used stack and why?
#33For web apps:
F# + .NET + ASP NET on the backend F# + Fable on the frontend
Otherwise just F# + .NET - basically runs everywhere and is good for anything.
Re: Ask HN: What is your preferred/most commonly used stack and why?
#34Django / Postgres which might evolve to React / Django+DjangoREST / Postgres / Redis / ES / RabbitMQ
I agree, although I would swap out React for Vue.js V3.
Also, from experience RabbitMQ (with I assume Celery) is probably overkill for most projects and introduces more moving parts especially if you already have Redis. So I would go for Python RQ with Redis as the broker. (You can use Celery with a Redis broker but it has strange bugs and again probably overkill)
Finally, Ionic framework and Capacitor for mobile apps.
Oh, and increasing falling for TypeScript.
Supper quick stack to build anything.
Re: Ask HN: What is your preferred/most commonly used stack and why?
#35Backend: TypeScript, Node
Frontend: TypeScript (no frameworks)
Lint: TypeScript-Lint
Linux: Bodhi Linux
Database: no preference
I tend to build most everything else myself, the cost of low abstraction high performance execution.
Re: Ask HN: What is your preferred/most commonly used stack and why?
#36Bash, Emacs, C. Deployment: GitHub Actions and Pages No databases, hashtables are good enough and around 1000x easier and faster.
What type of systems are you building where hashtables are good enough?
Can you provide examples of a range of apps you've worked on with this stack?
Re: Ask HN: What is your preferred/most commonly used stack and why?
#37Linux/JVM/Postgres - the "boring tech" stack.
Yet solves probably 99% of use cases!
Re: Ask HN: What is your preferred/most commonly used stack and why?
#38LAMP with Dart+Flutter. Less and less C/C++ on backend these days.
Re: Ask HN: What is your preferred/most commonly used stack and why?
#39It depends on the problem but I stick with what I know.
Database: SQL Server at work, PostgreSQL at home (due to pricing but it's also great!).
Backend: ASP.NET Core
Front End: As little as possible but it depends on requirements going from
1. None at all
2. Use JQuery in certain spots for UX
3. Use Typescript/React (simple, no redux etc.) for a complex SPA-type app.
But 1 is the default because KISS.
No GraphQL or NoSQL DBs. Might use S3/Azure blobs though for caching.
ASP.NET/.NET/C# is used because I'm used to it. However even with that bias, I argue it is a great sweet spot for back end languages. Good typing system but not too complex like Haskell. Garbage collection works has never been something I've had to worry about. Also performant and great tooling.
Re: Ask HN: What is your preferred/most commonly used stack and why?
#40It depends on the problem but I stick with what I know. Database: SQL Server at work, PostgreSQL at home (due to pricing but it's also great!). Backend: ASP.NET Core Front End: As little as possible but it depends on requirements going from 1. None at all 2. Use JQuery in certain spots for UX 3. Use Typescript/React (simple, no redux etc.) for a complex SPA-type app. But 1 is the default because KISS. No GraphQL or N…
Thank you for saying simple React. I feel like I'm insane sometimes as I can do 99.9% of what I need without Redux.