Like in Java 7 days Android didn't support NIO, randomly didn't support certain forms of exception handling, had random holes in library support (core Java libraries mind you, not the sun stuff)
The odds you could take a random XML parsing library for example and use it in an Android project were low. Random namespaces would be missing, cryptic errors tied to missing language support, the works.
Like you realize the idea of having a kinda-almost-the-same language being damaging is already known. J++ was not the same set of circumstances, but it shows that yes, you can make a language similar enough to benefit and at the same time be different enough to damage.
I mean literally QNX had better support through some vendor we were using at the time, but somehow Google couldn't do better?
Like in Java 7 days Android didn't support NIO, randomly didn't support certain forms of exception handling, had random holes in library support (core Java libraries mind you, not the sun stuff)
The odds you could take a random XML parsing library for example and use it in an Android project were low. Random namespaces would be missing, cryptic errors tied to missing language support, the works.
Like you realize the idea of having a kinda-almost-the-same language being damaging is already known. J++ was not the same set of circumstances, but it shows that yes, you can make a language similar enough to benefit and at the same time be different enough to damage.
I mean literally QNX had better support through some vendor we were using at the time, but somehow Google couldn't do better?