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

Ask HN: What is your preferred/most commonly used stack and why?

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 71 posts

Re: Ask HN: What is your preferred/most commonly used stack and why?

#53

Post by readonthegoapp »

leros wrote: post #40
quickthrower2 wrote: post #39

It 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.

doesn't that mean you still need Redux?

Re: Ask HN: What is your preferred/most commonly used stack and why?

#54

Post by readonthegoapp »

andrei_says_ wrote: post #9

Ruby 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.

i thought Hotwire was supposed to give us js without the js, but it seems like it needs stimulusjs and/or a mix of at least three other libraries and html-polluting attributes and code snippets.

i def don't understand that world yet, but i'm thinking...is there even enough of a payoff to step down from Vue?

slim looks cool. guess i have to check out laravel lumen, too. i thought lumen was just api support, so maybe slim is the same? i have to watch a youtube.

https://www.slimframework.com/

Re: Ask HN: What is your preferred/most commonly used stack and why?

#55

Post by schwartzworld »

readonthegoapp wrote: post #53
leros wrote: post #40

Earlier quoted context omitted.

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.

doesn't that mean you still need Redux?

No. Redux is an antipattern. Don't get me wrong it's an amazing tool for managing complex, changing global state. It's just that complex, changing global state doesn't belong in a react app. You can get all the certainty benefits of using redux by just learning to organize and abstract your stateful behavior properly.

Re: Ask HN: What is your preferred/most commonly used stack and why?

#56

Post by Jugurtha » 

  Stack:
    - Application:               
      - Flask            
      - PostgreSQL       
      - Nginx

    - Infra:
      - Google Cloud Platform
                       
    - Monitoring:      
      - Prometheus     
      - Grafana        
      - Sentry
         
    - Analytics:       
      - PostHog        

    - Containers:      
      - Docker images on GitLab registry                     

    - Repository management:                                 
      - GitLab:        
        - Issue templates for:                                   
          - Bugs       
          - Features   
          - Incidents  

    - Communications:  
      - Slack

Re: Ask HN: What is your preferred/most commonly used stack and why?

#57

Post by boogywoogy »

Everyone goes through this phase of creating a “starter”.

Maybe they evolve it to a pluggable framework.

But nothing will last the test of time.

Things change too rapidly and developers usually need to understand everything themselves when they want to customize stuff.

The best is having small packages that do one thing well that do not involve buy-in to a particular framework.

It’s a really tough challenge. Making something flexible yet works out of the box.

Re: Ask HN: What is your preferred/most commonly used stack and why?

#58

Post by rurban »

angrais wrote: post #36
rurban wrote: post #31

Bash, 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?

See my github. Mostly system stuff: languages, libraries.

https://github.com/rurban/

E.g. I preferred hashtables as database in phpwiki. There I needed sorted pagination, but even without btree's the simple server-less hashtable architecture was 20x faster than mysql/sqlite with its overhead. Also, why logarithmic btree's when you can have constant lookup. Not everything needs to be sorted.

Re: Ask HN: What is your preferred/most commonly used stack and why?

#59

Post by moooo99 »

Frontend: - NextJS - TailwindCSS + TailwindUI - react-query

Backend: - nestjs - PostgreSQL - docker on Hetzner or digital ocean for deployment

Im currently looking into Hasura/PostGraphile as a possible substitute for large parts of my backend stuff. I mostly build fairly simple CRUD apps, so I’m confident I can reduce complexity by quite a bit

Re: Ask HN: What is your preferred/most commonly used stack and why?

#60

Post by utf_8x »

Architecture - microservices mostly connected through GraphQL and gRPC (certificate based auth is the shit)

Languages - Java for backend, pure JS for frontend

Frameworks - Spring Boot on backend, pure React on frontend (I like to keep it simple)

Infrastructure - Mostly k8s (with helm to make life easier), Nix for more complex stuff

Databases - Postgres, Mongo, Redis, Elastic... Really depends on use-case...

Post reply on HN