491 karma · joined January 17, 2015
Even if they lose money by manually reviewing a small ad that was flagged as possibly political, it doesn't mean it costs more to review 1/100 low-volume ads. They're also paying to classify useful data to train their model.
Proper enforcement is hard. They won't get there soon. It'll come slowly for a few years to avoid mistakes. When AIs get reliable at detecting lies/harassment, enforcement will become the norm. (my prediction)
So when companies like Apple are offering great security, people are scared Facebook is reading their conversations, continuously tracking their location, and listening to their microphones.
Actually, it is much easier to build a pipeline, now that I think about it..
Ask any woman/minority, domestic abuse victim, etc. They don't want people spying on their messages.
Would also be cool for auto-complete suggestions. I'm thinking more along the lines of extracting larger patterns than for loops, such as stubbing out classes that follow a projects existing style. For example, adding an auth check at the start of a web request handler if that's what it sees elsewhere.
For battery life concerns, I can see them implementing some of the fall detection logic in hardware as well. For example, a high shock or shaking could trigger the fall-detection software to wake. Although, with the 60-second period, they probably wake the main processor often enough anyway that hardware detection might not save much power.
I personally don't think there's a market for non-js users. Most of the web is pretty broken without. I've never encountered someone in the real world who lives this way, even in the tech world. At most, someone will install a no-script browser plugin. That makes whitelisting and enabling javascript dead easy for the user. The only legitimate non-js use cases, IMHO, are for extreme political cases where you'd also be using TOR.
For "vanilla js," I can still have compilers, type checking, advanced ECMAScript 2019 features, local storage, webgl, etc. Without that understanding, you could qualify something as "vanilla js" in lots of different ways.
If someone said "vanilla c++," they might mean c++ without the recent language features, or they could mean the latest language spec but no standard library. Maybe it's still okay to link OpenGL but not okay to use a desktop GUI framework? Maybe OS frameworks are okay but nothing more? There's no communal understanding there that I'm aware of.
* webapps -- we tried this (iPhone v1) and they were awful. The web keeps improving but apps have consistently been years ahead.
* native software -- still too difficult to secure reliably.
We haven't really been suffering from fragmentation. We've essentially consolidated down to two platforms. You can also develop for the web or use a cross-platform framework.
Not really sure what you see as flawed. The app model has been wildly successful.
Wow, I'm surprised that has never occurred to me before. I guess that to most people, such as myself, the trade-off is so obvious from a personal safety point of view that we don't think too deeply over it. This is a great point.
Ignoring the windows store, this is really more of a "let developers handle their own updates" situation. The vast majority of modern windows software updates itself directly or through a loader (steam, etc). Windows developers can easily tie into distribution services that offer update mechanisms. The default user experience is not 'no automatic updates.'