[lil1729]

I have looked at Android code. It is awful. Now, I don't form opinions about Google engineers based just on that code.

I meant to say, generalizations don't always work well. They may have bad engineers. But they have great engineers too. Kent Dybvig and his team who wrote Chez Scheme works for Cisco. There are many others. Jonathan Rosenberg who wrote many Internet RFCs on fundamental protocols that run the Internet voice/video works for Cisco.

Let's not generalize. It hurts people!

[_pmf_]

> 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]

Out 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

[Fargren]

For 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.

[Mickchicken2]

Event bus mostly

[MichaelGG]

Not disagreeing that they have very talented people. But I would not point to the SIP RFCs as commendable work in any way. It's a mess.

[lil1729]

I didn't say it is commendable work. SIP is what we have at the moment as a standard and is being used by a lot of products out there and it was written by a Cisco employee. That is all I said. I am not intimately familiar with SIP to comment on its pros and cons.