Ah, yes, let’s have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.
It’s a good time, for sure. That being said, I’ve stopped working with UI, and I don’t really miss it. I still do some side projects in Compose though, and it’s always way better than XML.
The whole ViewModel thing though I don’t love
When it clicks, it’s actually not that bad imo. I think the main problem is that Google aren’t really explicit enough about how to leverage them effectively, and as such they can be pretty hard to get right.
Reject Web technologies - embrace native mobile app development
Compose feels like React but without the bad JavaScript parts, really pleasant experience!
Ah, yes, let’s have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.
Funnily enough, I’ve found JavaScript to be by far the worst offender for expiring dependencies and vulnerabilities.
How are you supposed to develop web applications then?
That’s the neat part - you don’t.
I love Compose, creating UI is actually fun. The whole ViewModel thing though I don’t love
It’s a good time, for sure. That being said, I’ve stopped working with UI, and I don’t really miss it. I still do some side projects in Compose though, and it’s always way better than XML.
When it clicks, it’s actually not that bad imo. I think the main problem is that Google aren’t really explicit enough about how to leverage them effectively, and as such they can be pretty hard to get right.