develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 35

                1. Really insightful survey! Like all surveys/metrics you must interpret them with a grain of salt. That said, after some (quick) skimming, I have a few thoughts... @atopal/1207711800780673024
                  Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
              1. …in reply to @develwoutacause
                Firstly, browser compatibility (and IE11) in particular are still among the biggest challenges. We've come a long way in the past decade but it saddens me to see that this is still such a big problem in 2020.
                Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -1 🙁
            1. …in reply to @develwoutacause
              File system access is a very specific need for being ranked as highly as it is. I hear a lot of people voicing (rightful) concerns about security, but I still believe file system access is the number 1 reason apps choose native platforms over the web. We need an answer to this.
              Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
          1. …in reply to @develwoutacause
            PWAs are still lacking the browser support it needs. For this experiment to succeed, we need enough browser support and apps to pierce the general cultural consciousness. When I find a PWA on my mom's phone, we will have officially succeeded.
            Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +10 🙂
        1. …in reply to @develwoutacause
          I'm surprised to see debugging tools as a frustration. I've always found web debugging tools (and Chrome #DevTools in particular) to be in best in class (honorable mention to @Microsoft). I'm curious to understand exactly what specific challenges developers are encountering?
          Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
      1. …in reply to @develwoutacause
        Complaints about the high velocity of framework and tooling churn reiterate the need for easy upgrade and migration paths. Tools like ng update need to become table stakes for the long-term stability of any significant dependency.
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
    1. …in reply to @develwoutacause
      Frameworks are often a hindrance just as much as a help. Solving common problems is great, but frameworks also need to learn when to get out of the way.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
  1. …in reply to @develwoutacause
    The top way developers overcome frustration is seeking help from the community. A strong community can overcome any adversity. Often the best tool **is** the most popular one. Not because it is the highest quality, but because someone else has encountered every problem you will.
    On twitter.com Twitter logo develwoutacause’s avatar Mood +10 🙂
    1. …in reply to @develwoutacause
      Again, it would be a mistake to over-extrapolate from a single source of data, no matter how it was collected. There is still a lot of useful info here and I'm really glad we, as an industry, can generate and use this kind of data to drive our priorities.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +5 🙂