diceduckmonk
Joined 4 years ago
Joined 4 years ago
It’s immaterial to Apple if I stole an iPhone from the Apple Store too.
> Also, he said that he's somehow stumbled into somehow having a commercial bottling license. If him, why not us?
Because he is a commercial bottler who is sampling from different supplier that he intends to source from for his business.
If you have thousands of resources in GCP, for example, the search is not super helpful.
People visiting for a few days go with a “10 restaurants you have to try in Portland” which are just mediocre chic restaurants you can find in every other city. They don’t realized how underrated Asian food in Portland is. One, Google Maps and Yelp reviews are negative signals of for Asian food. Restaurants that highly rated above 4.5 are so for the “ambience” rather than the food. Two, the restaurants are dispersed rather than being concentrated around a Chinatown or Little Saigon.
Any posts on the internet archives to understand the history ?
And Pokémon cards because this generation has less ability to afford big purchases like a house or having a child
Github/Gitlab would be a provider of the filesystem.
The problem is app developers like Google want to own your files.
https://endtimes.dev/why-your-website-should-be-under-14kb-i...
Photography and hobbyist drones are easy enough to control, and I would expect a manual passenger drone to follow that consumer model.
This website was from/for an era where you hotlink the scripts.
SaaS can provide “open core” or better yet simply sell a hosted version of their fully open source code. If the provider fails to provide, you can fall back to self hosting.
The API equivalent would be open sourcing the data. This is the OpenStreetMap model. If the API provider fails to provide, you can fallback to the underlying data.
I’m wondering if Apple Maps is doing something similar where they set a low official limit that they can walk back on / to in the future, as to avoid legal responsibility
It is someone's quarterly performance review and OKR to improve SLO. One such SLO is average load time. If you set such metrics as a goal, and financially reward people to do it, it's easy to meet the goal: arbitrary prune out the long tail, especially if the distribution of saved locations per user follows an Pareto/power law distribution.
They've since rolled back that experiment of payload sized limit, and instead used this number based limit. I guess it makes more a cleaner explainaton and internal documentation from a product sense this way as opposed to an arbitrary engineering limit.
The issue is still apathy and laziness from the engineers... they can have this per-request limits, but cache previously loaded pinnned locations, then incrementally append more to the list on subsequent requests. Instead, they attempt to reload the source of truth from the server everytime. There is a specific behavior where I see this is the case: they will load 3,000, you add another location which is now 3,001 locally, but after a few minutes they reconcile with the server and your local machine is back to 3,000. This is especially ironically considering the Google interview's emphasis on Dynamic Programming and building up a larger solution from previous solutions...
On Desktop, you can still load all your locations. There is some weird and intuitive behavior here how they reconcile edits to existing pin. The caveat on Desktop is that they will entire to render entire regions when there is too much (somewhere in the vicinity above 3,000 but below 8,000). I've noticed in recent weeks they've rolled out a quadtree implementation where in a given rectangular region, they'd limit and cap how much saved locations they attempt to render, versus before where it would be seemingly depth-first until they reach the 3,000 limit.