"Most people I spoke to in Cuba work for the state and have zero incentive to deliver anything above the bare minimum. They get paid the same either way. Even the private restaurants lack the fervor of a competitive business, since the economic environment they work in is still completely controlled even if they themselves are private."
Interesting article, but this statement is completely opposed to my own experience. I went to Cuba 4 years ago and nearly everyone I met had something running on the side. One guy said that "everyone has two jobs, they job you're given and the job you love" (he was a tour guide who did photography on the side).
I a country where many (admittedly not all) basic needs are taken care of by the state, the people are able to pursue their own aspirations, as the guy featured in the article has done.
>One guy said that "everyone has two jobs, they job you're given and the job you love" (he was a tour guide who did photography on the side).
That is because that's the only way to survive. The top positions in Cuba are those which face foreigners, as there is always a non-trivial chance of receiving dollar-based tips, which are far, far more valuable than the official Cuban currency. When I went to a Cuban resort town, my barman had been trained in Physics in Moscow, and considered himself very fortunate to be in the job he was in.
Cubans are, undoubtedly, some of the most resourceful and entrepreneurial people I've met -- but by necessity. The statement that they have "zero incentive to deliver anything above the bare minimum" is absolutely right, because everyone knows that their well-being will depend on what else they can come up with on the side.
Firstly, I'm not a Windows developer so please forgive any platform specific errors in my response.
If you're talking about runtime libraries that let you interface with an operating system, then for me, that's not an API.
Even if those libraries are available for every language available on the OS. It's still not an API.
An API should be language agnostic. Granted there may be language specific libraries providing wrappers, but the API itself must use an open protocol, making no language requirements. Otherwise it not an API.
- Searchable history of all content that has been viewed on the app
- Age-based content/functionality restrictions, with sensible defaults
- SM account DOB set from device DOB, with no override
- Parental controls implemented consistently across all apps
- Free comprehensive public education programme for parents about using SM safety
Some of this already exists, but not widely and is rarely done well.