_qjt0

Interesting, based on this experience, what must-have criteria would you look for in evaluating a tool? Ability to export the code if the tool proves too constraining? What else?

It would probably be worth it to restore trust: Refund all the money they've taken from this company for the last year, and apply a credit to their account for 3x that amount, say.

> things which cannot be measured in next quarter.

I'm all for long-term investments, but can these ever be measured? If not, it will take more than your claims to convince me that it's worth investing in.

There are other ways to appreciate art and culture, such as visiting museums, reading books, watching documentaries or other youtube videos on these topics, etc. These are all free or much cheaper than a course in a college. You haven't demonstrated how an academic setting is better and worth the cost.

Govt doesn't need to subsidise industry. I'd be fine if these loans are issued by private investors, as with Lambda school.

> capitalistic profit seeker is also a wasteful exercise

No, their benefit can be measured in GDP. Imperfect, sure, but 100x better than your hand-waving claims. No personal offence intended.

Interesting. Regarding developers not caring about security, that's why I suggested it should be the default, with an option to turn it off for performance or other reasons, rather than the other way around.

I wonder if there's an opportunity to reduce the privacy problem by having the phones log data to an intermediate server. The intermediate server will be open-source and run by a trusted entity (EFF, Apache Foundation, whoever). OnePlus will be able to submit whatever code they want to this server after a public privacy-focused code review by the trusted entity.

The proxy server will aggregate and anonymise the data before uploading it to upstream OnePlus servers. For example, it can strip out IP addresses. Eliminate data points which are too few and can therefore dangerous. Maybe if too few people are using an app, records about the usage of that app aren't uploaded to upstream OnePlus servers. If OnePlus wants to know how many photos an average user is taking, the intermediate server could just that information, or percentiles, not data about each individual user. These are all not possible to do on-device.

With this, we don't have to worry about what code is running on the phone, or what OnePlus servers are doing, both of us are closed-source and unavailable to us to inspect. But the intermediate server will be open-source.

Good to see that we don't fully disagree :)

Going back to the example of a doubly nested loop to determine if there are any two numbers in an array that sum to zero, it should take at most 1 minute for a smart engineer to figure out that it works. They don't have to speak before they've evaluated whether it works. The metric I use is: how long did they take to get to a solution that works, even if inefficient?

I didn't say I want quick but wrong answers. I said I prefer a quick but inefficient solution to a problem, as a starting point.

If I ask to determine whether an array contains two numbers that add to zero, a competent engineer should be able to give the naive answer -- a doubly nested loop -- in ten seconds, or at most a minute. If someone takes a lot of time to give me any answer at all, it's a concern.

Thanks for sharing Apple's rationale, but I disagree. The bottleneck is space, not speed, of SSDs. Few people need a GB per second of read or write more than they need space. If compression gives me even a GB of extra space on a 128GB SSD, I'd take it.

In fact, a 7200RPM hard disc is adequate for me.

I don't want even more updates to apply. It's a nuisance. And most of the time they don't make things better for me in any appreciable way.