It's my understanding that iOS is generally considered a more secure alternative than Android, and that part of this is the app review process, that is part of the App Store. So isn't there at least some truth in that opening this up will create a less secure environment?
I'll add again that while this may have been true at a point (and was covertly marketed into our brains by big apple) it's just not true anymore. It's honestly scary how often i hear this and yet almost no one can say where they actually heard it.
Maybe if you’re using a Pixel with the latest OS updates but the average person like my mom is using some off the shelf budget Chinese/Korean phone full of apps with spammy ads and confusing interface flows. The privacy settings are confusing and unlike my dad who comfortably uses his iPhone my mom has barely scraped the surface because the Samsung OS UI is such a mess (ie, 2 different messaging apps named Messages came preinstalled) and it’s slow, the UI with fonts scaled up for vision hides entire buttons in 3rd party apps (a joy to debug over the phone) etc.
Just this week she had to install a work app for scheduling from Googles Store and got duped into a fake clone that installed 4 other apps with repeated pop up apps emulating a signup wizard.
Those non standard androids are far far more worrying and the Google App Store is way less locked down.
If my dad was in the EU I’d have to tell him never to install an app using anything but the Apple App Store.
I went back to Spotify because I find the playlist there a lot better. I only tried Apple Music for a couple of months, when the service was released, so things could easily have changed.
The homepage (https://github.com/marketplace/watermelon-context) states that Watermelon supports "C, C#, C++ and 7 other languages", but I can't figure out what these other languages are. Has anyone found this info? Is TypeScript a supported language?
First: Realize that React Query isn't a library for fetching data, but a library for caching the fetched data. So think about how you will be invalidating that cache. For us, the rule of thumb was that each fetch to the API should have it's own cache key in React Query.
Second: The data in cached in React Query is effectively globally available, so it comes with all the benefits and pitfalls that globals have. We use Storybook and do not use React Query in the components that have stories, so React Query is only used in the root components of the app.
ReactQuery state is not global. It's set in a context, and it takes two lines to write a Storybook decorator that ensures a unique cache for each story.
It may still make sense to keep react-query out of your storybooks though.
No, it will not, it is not supported with windows emulated machines. It will work for linux machines to some degree using the additional binfmt handlers which can call out to rosetta. But that's mostly in user space.
> My understanding of the “duplication is cheaper than the wrong abstraction” idea, based on Sandi Metz’s post about it, is as follows. When a programmer refactors a piece of code to be less duplicative, that programmer replaces the duplicative code with a new, non-duplicative abstraction.
I think one of the main takeways from Sandi Metz's quote is that you should postpone creating the abstraction until after you have the duplicated code. Sometimes you will remove the duplication when you have just two implementations, sometimes you will want many more. Once you have the repeated code it's relatively easy to make the right abstraction.
Why are there more than one dot in the big countries like The United States, Brazil and Australia? I would have expected a single dot for each of these countries.
Those countries all have plenty of languages which are native to their territory which aren't the dominant one in the country. Aboriginal languages in Australia, native American languages in the US, various tribal languages in Brazil.
