2
12 Comments

What is your favorite Frontend stack?

I'm just curious. Which stack you LOVE to use for frontend development?
I know that you have to choose the best for the project and not for yourself, but what if you have the freedom to choose it for yourself?

on February 24, 2020
  1. 3

    I'm really loving vue.js for the js framework and Bulma for styling. I've had so much fun converting a project from a Bootstrap 3 admin template I bought - it was simplicity itself to recreate all the widgets and so on just using the core Bulma components. They've really nailed it. Vue is a joy as well, although I was disheartened by a rather negative thread about it on Hacker News at the weekend. I've been very productive using it as a replacement for jQuery. I was very put off React when I compared the two by the mixing of js and html. I know that's all the rage but I've been doing this a long time and it really goes against the grain.

    1. 1

      I can relate about mixing html and js too.

  2. 2

    Next.js, React, Material-UI, Node.js, PostgreSQL.

    I've been using the free AWS tier because I wanted to get some solid experience with it, but I'm starting to look for something simpler now.

    1. 1

      When using Postgres with Node do you use any type of ORM? Like Sequelize?

      1. 2

        I don't use an ORM. I have a lot of past experience with Hibernate and GORM back when I was doing a lot of Java and Groovy/Grails development as my full-time job. I've also used Mongoose in node.js, which is ODM for mongodb. There are pros and cons to using ORM (and in my opinion the cons are pretty significant), but the main reasons I've stopped using ORM are that I don't like the complexity and leaky abstraction, and now I tend to write code in a more functional style. Data is just data (no behavior associated with it), and my functions operate on that data. I warmed up to this approach when I was working with Clojure.

  3. 2

    Next.js, React, Tailwind, Zeit Now (and Firebase for backend)

  4. 1

    ClojureScript, shadow-cljs, React, db-view

  5. 1

    Vue for SPAs. Gridsome (uses VueJs. And is modelled after Gatsby) for marketing websites.

    Vue is smaller and easier to spin up new simple projects.
    But most functionality out of the box for larger more complex projects.

  6. 1

    I use react, graphql and mongoke

    Mongoke generates the graphql api to serve a Mongodb database based on their collections schema, check it out here https://github.com/remorses/mongoke

    Using mongoke i can also create mock fake data for the database to test how frontend looks like during developement

  7. 1

    My goto frontend dependencies are:

    React, Redux, Redux-Saga, Reselect, React-Router, Formik, Yup, Lodash, Moment and maybe Material-UI/material-table

    I like React Native for mobile, and to use TypeScript instead of JS whenever possible

  8. 1

    React! I've used GraphQL before as well, I'm still debating if I'm going to use it again. It adds some complexity that's not there in REST. I don't know if it's worth it honestly.

    I've been using Gatsby for static pages/blog. It's been kind of scary amazing. Super fast. Easy to use.

    1. 1

      The benefit of graphql is that you can generate a typesscript client and that prevents a lot of errors related to data field names and structure,

      but the game changer is that i can generate a graphql client for my Mongodb database based on the collections schema thanks to mongoke, that really speeds up my developement by a factor of 3 at least
      Check out mongoke here https://github.com/remorses/mongoke