type__error’s avatartype__error’s Twitter Archive—№ 13,691

  1. Lots of next.js complaints today. I've definitely become more pro-vanilla HTML/CSS/JS and pro-avoiding frameworks where possible. But Next is super useful for what we do at Monzo, where we have a massive customer service platform with loads of sponsoring teams contributing...
    1. …in reply to @type__error
      This is an app where we can dictate the browser and require good internet speeds (as they are staff). UX issues that we do have on the app come down to too many API calls, not enough caching, and a historical lack of design input.
      1. …in reply to @type__error
        For a highly interactive web based app with a ridiculous amount of data, vanilla JS can become very difficult to maintain. Had there been better frameworks around when it was built, we might have made some different choices idk (I wasn't there)
        1. …in reply to @type__error
          Ultimately in the absence of enough web developers to do _all_ the web work, React+Next gives enough of an abstraction for non-web engineers to contribute.
          1. …in reply to @type__error
            I don't really get the whole next/image thing, just use an img tag, but whatever
            1. …in reply to @type__error
              tl;dr: you might not need a framework yes, but sometimes it really helps