I wonder how this happens. If Apple has the capacity to detect grass strips between roads, how do they misplace an entire part of town (into the ocean, no less). Isn't there some sort of process in place to detect false positives?
This often happens when a map is made from data purchased from different suppliers.
Imagine you buy in the outline of landmasses from some other company. If you pay staff to 'correct' those errors, it will be mostly wasted effort, since those changes won't be sent back to the supplier and won't make it into the next version of the suppliers data.
Likewise, if you start merging your data and their data in a way which isn't 100% legally separable, you get into all kinds of trouble. Flagging up where your own street map is in conflict with the suppliers ocean map could could as 'deriving' your street map from their ocean map, meaning you no longer have all the rights to your street map.
I thought maybe who (or what, if it was automated) was tracing the map from a satellite view got confused by the mangroves in the middle of the island, since its dark color does sort of look like the nearby ocean... but it doesn't explain the ocean shapes on the west side of the island (around Seven Mile Beach and in West Bay)... and I'd have thought there'd be some double checking against traditional maps at the higher level.
What's really interesting for me is at the beginning on launch of Apple Maps, there was only the major road and the airport marked, now most of the roads are there.. overplayed on top of the body mass which is still wrong. Its almost as if , while updating their road mapping to be more accurate, they have never in the past 5 years or so updated the shape of the land masses themselves
According to the description in the linked article, only the first 5 characters of the hash of the password are sent to the API (and that API is not publicly available in the first place, apparently, but can only be accessed via Mozilla or 1Password's own APIs).
What exactly appears to be the problem?
The reasoning for this feature is clearly laid out, and the underlying "ethics of running a database breach search service", while controversial, are also something Troy has thought about very carefully:
I got the first model with the new butterfly keyboard and the touchbar in April 2017 and I still hate it. I appreciate the idea of adding a touchbar for regular users. After all, it might be nicer for them to just press "Next Song" when using Spotify than fiddling around with Fn+F*.
But for power users/developers, why do the most powerful MBP models come with these useless gimmicks? I'm using Dongles on 3/4 of the USB-C ports right now and that's not going to change anytime soon.
I wish Apple listened to developer's voices a bit more. To me, it's not a matter of price, either. I'd gladly pay more for a MBP with more/different ports and without a touchbar than I would for this model.
I agree. There are plenty of freedoms built into the REST way that enable you to create more or less detailed responses.
"I don’t care. Trees are recognized by their own fruits.
What took me a few hours of coding and worked very robustly, with simple RPC, now takes weeks..."
Weeks? For a REST API? No, I don't think so. REST gives you the tools to be pragmatic and quick, so use them.
It's one of the essentials principles of redux [1] that reducers must be pure functions without side effects.
If you violate that principle, then yes, your assumptions break. That's why you should keep it in mind. You can't really blame the framework if you purposely go against its basic rules.
I just wish they had a reasonable way to _enforce_ those rules (though I understand it's not really possible) – or at least make people really go out of their way to break convention.
If you render a more complex component this introduces another level of indentation. I can see why some people would prefer cleaner code but in my opinion, indenting ifs is a good thing as it increases the readability and allows you to spot if statements faster.
I commit everything that I want to be able to recover/share. If it's necessary to share (e.g. open a pull request), or if I want to have a distributed backup of my work, I'll push.
