3 ms·
> I have looked at Android code. You just have to look at the API. From little details (wifiInfo.getSSID() returning either the quoted SSID, an unquoted string
by _pmf_ 10y ago
> I have looked at Android code.
You just have to look at the API. From little details (wifiInfo.getSSID() returning either the quoted SSID, an unquoted string of hex characters the SSID consists of, the special string "<unknown ssid>" or "0x") to the overall architecture (needlessly convoluted lifecycle, 2D rendering architecture from 2000s, the whole intra-app Intent bullshit that causes people to find alternative ways of communicating between Activities within the same app ...)
- 72deluxe 10y agoOut of interest, what's wrong with Intents?? As alternatives, do people just end up dumping to an sqlite database and polling it in each Activity? Haha that'd be madness
- Mickchicken2 10y agoEvent bus mostly
- Fargren 10y agoFor inter-app communication Intents are a pretty reasonable solution to a complex problem. But inside an app, I would just love to have constructor parameters for my activities. I make do with Intents, but I don't have type safety, I have to deal with partially constucted objects until I've read my Intent Parameters and any time I have to pass something that's not in the default types that a bundle can contain I have to build a Parcelable wrapper for it, or find some other convoluted solution. Overall I just feel like I'm working at the wrong level of abstraction.