Those are all good points, I don't really have large objections to any of them. Thank you for telling me, it's important to see where I place value compared to other people so I'm not just mad. It's fine to see different value in things, and I'm glad it works for you.
Most of the things you mentioned don't hold as much value for me, so although they are indeed positives when compared against other development environments, they don't outweigh the negatives, which happen to be in places I do place higher value.
For instance, I highly value long term support and stability for my users. I find that is EXTREMELY difficult to do on the web without writing everything yourself, and even then arbitrary decisions by browsers can also just randomly break everything (remember when browsers decided to add the slide to hide url, breaking the concept of view height? Remember when browsers added gestures to everything so now there's a forced 200ms lag to initial touch events? That wasn't always the case, and both of those broke my apps in a massive way). I don't like constant maintenance being thrust on me from third parties changing arbitrary things, and I don't like the idea of my users getting a randomly degraded or broken experience through no fault of my own, I feel like my users are getting attacked. It's why I don't use third party services, they always disappear or decide to start monetizing or change everything to make the experience worse for my users.
These desires also make it difficult for me to get into that ecosystem of rapid development with lots of frameworks and libraries for solving existing problems, because going back to work on apps that rely on those things is usually an exercise in futility. I'm sure you can imagine trying to open up a node app that you haven't touched in 3 years. I find it to be frequently impossible, or only possible with far more effort than it's worth. In the time I spend fixing it, I could've just rewritten the whole thing (and I find that's often what happens, even asking around).
Another thing I value highly is having bugs be my own fault. I can't leave things broken, I can't wait for others to fix things, it drives me crazy. It also drives me crazy to paper over bugs or introduce hacks due to bad design. And it REALLY drives me crazy when I'm trying hard to fix a bug only to realize it's not my fault. Now I just spent hours trying to fix something because I REALLY wanted to get it done, only to have to come full stop for months while I wait for someone to fix their crap (or send in a PR which also sometimes takes months and lots of bickering). THAT wrecks me so much more than small interruptions in flow state; now I have to stew for at LEAST a week on something I wanted to solve in a night. And I know I'm weird about hacks and bugs: IMO adding hacks ARE bugs in waiting, so really you're just adding more bugs.
When the bugs are my fault, I can fix them, so I tend to lean towards extremely well established and stable libraries that have always had a tightly focused scope vs large meandering libraries that solve every problem. I don't even use major database engines, everything I make uses sqlite because it's ridiculously stable and extremely focused. I've run into situations with several major database engines where queries that used to run fast are suddenly extremely slow because (insert arbitrary or extremely-opinion-driven change here). I know how databases work, I can design my own tables and indexes and reason about the performance of my queries, and I don't need a massive team or project lead (or worse: corporate) to decide that the way I'm doing things is "no longer a supported workflow" and change the performance of a database I worked so hard to perfect. I, the developer, know more about my own workflow than the people 1000 miles away from my project. And that's kind of like... the status quo of web development: you are at the mercy of browsers, you are at the mercy of frameworks, you're at the mercy of profit-driven progress. So while that all gives you a lot of great things, the very idea of third parties destroying a thing I spent hundreds of hours on for the sake of profit actually makes me sick. And I get that it's not always profit that changes things, but it's hard to differentiate when it seems like it's most of the reasons.
I'm sorry if that's a lot, and I understand if you completely disagree with any of that being a problem. I know I treat software development differently than other people (it's not better and doesn't make me better), and my desire to have long term support is seemingly at odds with my desire to not have to maintain things forever (at least there I do want to make the distinction that maintenance for my own bugs is perfectly fine, but maintenance simply because of arbitrary changes or bugs introduced by other people frustrates me). There are other, probably more pertinent things I could've listed that would've made for a better conversation, but I think my mind wandered off too far.
Thank you for having this discussion with me, I appreciate the positive things you expressed about web development. Maybe the next time I work on a web app, I'll see those things in a new light and place more value on them