News for hackers. Stuff that matters.
Re:It’s Been Real, Android: Why I’m Retiring from Android by izacus on Thursday October 13, 2016 @05:52AM (#12699584)
I'm not sure about the meaningful distinction here. Programming on any platform will be greatly improved by using good (preferrably opensource) libraries. What difference does it make who made them and why? It's such a strange nitpick.
Re:It’s Been Real, Android: Why I’m Retiring from Android by samastur on Thursday October 13, 2016 @06:37AM (#12699731)
Difference is at the beginning. When I started using Python I absolutely loved that stdlib covered almost everything I thought I could need. These days packages I use mostly come from elsewhere, but at the beginning it was great.

I'm fine with Javascript development these days because I built my fundamentals years ago. I am not sure how comfortable I would be otherwise and when I meet people who are where I used to be, they often look lost.

I am also thinking about learning Android development and don't really know where to begin.

Re:It’s Been Real, Android: Why I’m Retiring from Android by pjmlp on Thursday October 13, 2016 @06:52AM (#12699776)
Because outside the startup world, in many enterprises developers are only allowed to use sanctioned libraries outside what the platform owner advises as best practices.

So everyone suffers when anything more complex than hello world already required third party libraries, specially ones that aren't even acknowledged by Google.

Re:It’s Been Real, Android: Why I’m Retiring from Android by Klathmon on Thursday October 13, 2016 @07:34AM (#12699952)
A self inflicted restriction doesn't make a language bad.
Re:It’s Been Real, Android: Why I’m Retiring from Android by pjmlp on Thursday October 13, 2016 @07:56AM (#12700073)
It is not self inflicted, rather imposed by customers.

Also the Android operating system isn't a language.

Re:It’s Been Real, Android: Why I’m Retiring from Android by Klathmon on Thursday October 13, 2016 @08:15AM (#12700185)
Regardless, it doesn't reflect on the language/os/ecosystem/platform/system/library/runtime

If a company wants to vet all of their software, good on them! But that doesn't mean that anything that's not vetted by them is somehow worse for the majority of users, just that they haven't vetted it yet. So any arguments about how "library x" isn't usable by them won't apply to the vast majority of people, because most don't have that issue, or have no problems vetting that library as well.

Somewhat off topic. Is there a word that encompses the langauge, platform, runtime, etc...? I hate the word "ecosystem", but it seems like the best bet. And using any one of the others brings out comments of "well it's not a language" or "it's not a framework it's a library" or something else.

Re:It’s Been Real, Android: Why I’m Retiring from Android by orangecat on Thursday October 13, 2016 @10:04AM (#12700809)
If you're using N separate libraries, that's N times the likelihood of breaking changes that force you to migrate at inconvenient times, and O(N^2) opportunities for bugs caused by incompatibilities.
Re:It’s Been Real, Android: Why I’m Retiring from Android by hinkley on Thursday October 13, 2016 @12:35PM (#12701995)
Two libraries can misbehave because they share a common dependency.

If you assume a roughly logarithmic intersection of shared dependencies that's O(N^2 log n) chances for a bug. But in some communities I'm sure even that is optimistic.