6
18 Comments

Which technologies would you choose for your next web project?

  1. 3

    Laravel+Vue with a focus on centralizing microservices

  2. 2

    Supabase is nice. And you probably don't need Mongo since Postgres jsonb is so good.

  3. 2

    NuxtJS -> NextJS based on VueJS

  4. 1

    I like Next + Tailwind + Lambda

  5. 1

    Symfony with GraphQLite for GraphQL API

    Quasar Framework built on Vue for frontend.

  6. 1

    Svelte is very likely on the frontend, depending on what it is I decide to build next (it's possible what I build next won't even have UI). I've experimented with Svelte over the of the past year with smaller projects, including a mobile app utilising Svelte Native. I've been really impressed with it as a framework in terms of both ease of use and performance.

    On the backend will probably stick with NodeJS/Typescript via NestJS. Once I have an idea I tend to want to build it quickly, so using something unfamiliar at that point is completely out of the question.

  7. 1

    I’ve been thinking about this a lot lately as I’m just starting a new project. My backend is always Ruby on Rails and more recently my frontend tends to be React, however after taking into account the expected user experience of my new project, I’ve opted to go with Rails + Hotwire (Stimulus & Turbo). It’s been up and down so far, there are some things I like about Hotwire, it feels a lot snappier and a cleaner codebase, however I am certainly missing some of the flexibility I get from React.

    I’ll probably use Heroku to host it, in the past I’ve used Linode, which is great, but I’ve found myself dealing with DDOS and security issues a lot recently so I’m thinking this time I’ll just use Heroku and if it gets too expensive, be ready to move.

  8. 1

    Typescript + NextJS / Typescript + Express

    1. 2

      interesting that most opting out not to use Vercel's serverSideProps :)

      1. 1

        Maybe it's a habit thing, but I kind of like having the API as a different project because if it starts to get too big, I can always split it into smaller micro-APIs.

        I do like Vercel serverless functions, though, and I've been using them on my job.

        1. 1

          I thought it was mainly a cost thing (or at least most of the opinions that I have heard before). But thanks, I was just curious why not to use the in-built functionality :)

  9. 1

    The technology, I had used in my last project is JavaScript for the frontend and ExpressJs & MongoDB for the backend.

    https://www.indiehackers.com/post/selling-my-first-project-onlibrary-best-place-to-get-ebooks-f35a0f24cb

  10. 1

    TypeScript, React, NextJS, KeystoneJS, AWS Lambda, Docker, NestJS, AWS S3, Backblaze B2, Digital Ocean managed databases (postgres + redis). If AI is included, then also Flask, Pytorch, and Tensorflow. Anyway, that’s what I’m using so far 😄

  11. 1

    Clojure -> Clojurescript -> Reagent/React.

  12. 1

    Vue is my go to choice!!!! It's just easy, and super efficient to work with.

  13. 1

    This comment was deleted 2 years ago.

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 49 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 28 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 14 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments