Open Menu
AllLocalCommunitiesAbout
lotide
AllLocalCommunitiesAbout
Login

What is your favorite software stack for full-stack web development?

⁨45⁩ ⁨likes⁩

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨CoderSupreme@programming.dev⁩ to ⁨programming@programming.dev⁩

source

Comments

Sort:hotnewtop
  • Knusper@feddit.de ⁨1⁩ ⁨year⁩ ago

    Rust in the backend and frontend, via WebAssembly. I’m using the Leptos framework for the frontend.

    source
    • DogMuffins@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

      How do you find Rust for the frontend?

      source
      • Knusper@feddit.de ⁨1⁩ ⁨year⁩ ago

        I enjoy it a lot. It’s the first time that I find frontend actually fun.

        A lot of the memory management aspects of Rust are bypassed by Leptos, so that doesn’t come up as much as one might think.

        And I do find Rust’s type system really helpful for actually portraying the UI state. For example, if you execute a function that can fail, you don’t have to catch some exception and then pass the error message separately into the UI or whatever.
        Instead, you get a Result-type from that function, which contains either the data you want to render in the UI or the error information you want to render instead.

        So, you can just pass that right through to your rendering code. And then there’s pseudo-HTML inline in the code, where you can do full-blown Rust-pattern-matching to properly handle such a Result-type and simply render the appropriate UI element.
        No horrid multi-line ternaries, no uninitialized variables, no separate boolean checks before accessing a variable. You simply know at all times what information is actually available.

        What’s also really nice with backend and frontend in the same language, is that you get compile-time-guaranteed compatibility between them, because you can simply use the exact same model types and API route constants.

        It is still a relatively young ecosystem, so there are still breaking changes every so often. And well, obviously you won’t find anywhere close to the number of UI component libraries as you can find for JS. So, for an experienced JS dev, it is likely a step back in productivity.

        But if you’ve got Rust expertise instead or only backend folks on your team, then I heartily recommend it.

        source
      • MonkCanatella@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

        Check out Greg Johnston’s interview with Primeagen. Greg’s just an awesome dude all around. I just hope one day there comes a solution for the large bundle sizes associated with wasm frameworks

        source
  • starman@programming.dev ⁨1⁩ ⁨year⁩ ago

    Vue/Nuxt + ASP.NET Core + PostgreSQL

    source
    • Flyberius@hexbear.net ⁨1⁩ ⁨year⁩ ago

      I’ve used Nuxt a few times, but I end up in absolute hell sometimes tracing down bugs and incompatabilities. More so with Nuxt 3. Probably not an issue for more experienced Devs.

      I find myself coming back to the simplicity of running a separate backend, even though that reintroduces a lot of the problems that Nuxt alleviates.

      source
    • philwills@programming.dev ⁨1⁩ ⁨year⁩ ago

      /me Sort by top

      wat

      source
  • marwwin@suppo.fi ⁨1⁩ ⁨year⁩ ago

    HTMX, Python, JavaScript.

    Though I would like to try Go for the backend if I would just find some time for it.

    Also Svelte and Sveltekit is very nice

    source
  • wantd2B1ofthestrokes@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

    php + cobol

    source
    • otter@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      :(

      source
    • railsdev@programming.dev ⁨1⁩ ⁨year⁩ ago

      Honestly I’d love to learn COBOL just for fun but I have to work for a living 🥱

      source
      • coltorl@programming.dev ⁨1⁩ ⁨year⁩ ago

        It’s honestly not that hard, the language was made to be simple. The complexity associated with the language largely has to do with the legacy applications the language supports. If you look at a greenfield project (eg CHADstack) you’ll actually pick the language features up pretty quickly.

        source
  • LPThinker@lemmy.world ⁨1⁩ ⁨year⁩ ago

    TypeScript React (although I like Svelte better, it’s hard to pitch for business projects), C# ASP.NET Core API, Postgresql.

    source
  • OffByOneError@programming.dev ⁨1⁩ ⁨year⁩ ago

    svelte front end, golang backend, postgres for database.

    source
    • Slimy_hog@programming.dev ⁨1⁩ ⁨year⁩ ago

      Choose technology because it’s the right fit for the job, not because it’s your favorite.

      100000%

      source
      • didibear@lemmy.world ⁨1⁩ ⁨year⁩ ago

        Well it’s difficult when the main difference between technologies is mostly preference. Real pros and cons require tons of analysis.

        source
  • CoderSupreme@programming.dev ⁨1⁩ ⁨year⁩ ago

    go, react, graphql, postgresql

    source
    • jelloeater85@lemmy.world ⁨1⁩ ⁨year⁩ ago

      How’s Go for a backend? I’ve used it abit, stupid fast.

      source
  • jonwah@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

    React / TypeScript / Vite (sometimes Redux) for the front end, C# .net / SQL for the backend…

    Fast-ish to get up and running, scales to a medium-large project with minimal headaches

    source
    • douglasg14b@programming.dev ⁨1⁩ ⁨year⁩ ago

      Yessss.

      C#/.Net backends are the best. The long term stability, DevX, and the “it just works” nature of all the tooling makes it a great choice. It’s also fast, which makes scaling for most applications a non-issue.

      I’ve switched to postgres for DB from SQL server, have never looked back, would recommend.

      source
      • jonwah@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

        Yup all valid points. And I find Nuget to be a heaps less painful package manager than other ecosystems

        source
  • railsdev@programming.dev ⁨1⁩ ⁨year⁩ ago

    Hanami, Ruby on Rails, Lucky

    source
  • crowfx@crowfx.web.id ⁨1⁩ ⁨year⁩ ago

    HTMX + Go.

    Go as a backend has a very nice multithreading model to extract more speed and value from your app.

    The built-in standard libraries provide many good abstractions.

    Also the templating engine is very nice to use.

    source
    • apd@programming.dev ⁨1⁩ ⁨year⁩ ago

      I hate go templating, I really really do. I don’t even really know why. I just hate it.

      source
  • kSPvhmTOlwvMd7Y7E@programming.dev ⁨1⁩ ⁨year⁩ ago

    React +python + postgres/sqlite

    source
  • DmMacniel@feddit.de ⁨1⁩ ⁨year⁩ ago

    markdown+frontmatter+handlebars, bun, sqlite.

    source
  • douglasg14b@programming.dev ⁨1⁩ ⁨year⁩ ago

    .Net + Vue + Postgres.

    I can get applications built extremely quickly, and their maintenance costs are incredibly low. The backends are stable, and can hang around for 5, 10+ years without issue or problems with ecosystem churn.

    You can build a library of patterns and reusable code that you can bring to new projects to get them off the ground even faster.

    Would recommend.

    source
    • 32b99410_da5b@lemmy.world ⁨1⁩ ⁨year⁩ ago

      But .NET has a 3 year LTS schedule unless you’re on the invincible .NET Framework 4.

      You’ll have to update your server OS at some point and then your .NET version will be too old to be installed and then you’ll have fun bugs to squash from all the new versions of things interacting…

      source
  • nitefox@sh.itjust.works [bot] ⁨1⁩ ⁨year⁩ ago

    Nuxt + graphql or C# (the latter I’m still studying but it’s not bad).

    Definitely not JS or Java

    source
    • lemmyvore@feddit.nl ⁨1⁩ ⁨year⁩ ago

      How are you doing Nuxt and GraphQL without JS?

      source
      • nitefox@sh.itjust.works [bot] ⁨1⁩ ⁨year⁩ ago

        I meant as in with Express and similar

        source
  • Nomad@infosec.pub ⁨1⁩ ⁨year⁩ ago

    Typescript, svelte, django, postgresql with a dash of celery, redis and pushpin

    source
  • Olap@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Typescript React from cloudront Typescript express on ecs. PSQL on RDS

    source
  • mark@programming.dev ⁨1⁩ ⁨year⁩ ago

    Express, JavaScript (with TS via JSDocs for type-checking) and Postgres

    source
  • magnus@lemmy.ahall.se ⁨1⁩ ⁨year⁩ ago

    Javascript/Preact/Lesscss on frontend with a backend written i Go using Postgres.

    source
  • outcide@lemmy.world ⁨1⁩ ⁨year⁩ ago

    SvelteKit + PocketBase + CapRover.

    source
  • livingcoder@programming.dev ⁨1⁩ ⁨year⁩ ago

    My current favorite is mostly Rust-based with the tide crate, tide-jsx crate, postgres crate, and Postgres in Docker. Super easy, super fast (to develop and run), but I haven’t made any large web projects with this stack yet, just small stuff.

    source
  • asyncrosaurus@programming.dev ⁨1⁩ ⁨year⁩ ago

    Depends:

    For websites: Htmx + AlpineJs on the front end, ASP.NET Razor Pages and PostegreSQL on the backend.

    For Web Apps; Blazor and PostgreSQL

    source
  • kohana@kuu.kohana.fi ⁨1⁩ ⁨year⁩ ago

    Go and Next.js. For data, Postgres or SQLite depending on the need.

    source
  • Flyberius@hexbear.net ⁨1⁩ ⁨year⁩ ago

    Vue + Express + Typescript + Postgres

    Though I am playing around with Firebase and Firestore at the moment so that simpler projects have less backend overhead

    source
  • PHLAK@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Laravel (PHP) + Vue (JS)

    source
  • Akisamb@programming.dev ⁨1⁩ ⁨year⁩ ago

    WordPress wirh custom templates running on a LAMP stack.

    source
  • philwills@programming.dev ⁨1⁩ ⁨year⁩ ago

    I’m seriously very surprised to still see so many relational databases in the top responses… guess I’m just in fantasy land. I hate writing SQL… good at it, but it’s not fun (to me).

    source
    • mundane@feddit.nu ⁨1⁩ ⁨year⁩ ago

      I hate when I have to work with non SQL based persistence.

      To each their own I guess. 😇

      source
      • philwills@programming.dev ⁨1⁩ ⁨year⁩ ago

        API gateway all the things… it’s annoying at times, but I don’t want to have to manage a dbs… or write SQL.

        Of course, there’s always some data store to manage, but I prefer the ones with fewer switches and easier scaling (like DynamoDB).

        In the end, it’s a matter of preference. I prefer writing custom map reduce functions, you prefer SQL indexes.

        Honestly, the amount of requests and data I’m handling for personal projects could be easily handled by the filesystem… so, ddb is great and I stay free tier… like always.

        source
    • onlinepersona@programming.dev ⁨1⁩ ⁨year⁩ ago

      Use an ORM. With NoSQL on relational data, you’re guaranteed going to write a worse, relational solution than what relational databases provide. SQL is shit, but rewriting relational logic is worse.

      source
      • philwills@programming.dev ⁨1⁩ ⁨year⁩ ago

        Except when you’re not worried about scale because you’re building a small side project… I don’t want to pay for a db (or the hardware to host it) for my play projects. My in-home play server is a very old home PC that is very underpowered for today’s software.

        source
        • -> View More Comments
  • MonkCanatella@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Leptos + SurrealDB

    source
  • donio@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Go with the frontend kept as simple as possible. No frameworks, only libraries.

    source
  • ShrimpsIsBugs@programming.dev ⁨1⁩ ⁨year⁩ ago

    Does streamlit displaying data from a csv file count?

    source
  • datelmd5sum@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Mocha, C, Informix

    source
-> View More Comments