Source: https://twitter.com/solomonstre/status/1111004913222324225?l...
135 karma · joined January 24, 2021
Source: https://twitter.com/solomonstre/status/1111004913222324225?l...
> It resembles actual Thai sauce about as much as Kraft “American cheese” [sic] does a good English cheddar. (Although unlike this comparison, Sriracha arguably improved on the original.)
Thai people hate the americanized version of sriracha, so I guess your comparison is right that Huy Fong Foods sriracha is like the Kraft “American cheese”.
That might be true in the beginning but long term ad's add a lot of friction and frustration e.g. having to wait X amount of seconds before getting access to the content.
I have been a YouTube Premium user since day one and I can't imagine not using it.
What I would love to see more is having a choice of having a free ad supported version and the option to upgrade and pay to remove those ads.
Unfortunately you can't ignore Safari on iOS though, Apple only allows WebKit based browser, which makes any browser on iOS just a skinned version of Safari.
What websites are you visiting?
I am not from the US, but is this really all you need to "proof" your identity?
The most common thing I have seen in the EU when companies have a KYC requirement is that during the sign up process you will have a quick video call where you have show your ID card while they verify that your ID is legit.
How is only allowing ONE browser engine good for diversity? If anything it hinders diversity and progress on iOS.
> Websites would further go down the path of only testing on Chrome
If only it would be possible to test Safari on a non Apple device, Apple is partial it fault here
> And answer this: how would allowing other engines increase privacy?
Because then there could be competition between Safari, Firefox, Brave etc.
Answer this: why do you let Apple dictate what Apps you can install on a ($700 - $1100) phone that you own?
that sounds like a badly managed workplace.
Imagine how awesome webOS would be today with the support of PWAs?
Added benefit of having a physical keyboard is having shortcuts.
You just have to introduce a build tool like ncc (https://github.com/vercel/ncc) which will bundle your app into a single JS file.
This is only the case if you are using HTTP/1.1: https://stackoverflow.com/a/45583977/11383840
There is yew (https://github.com/yewstack/yew) which is a React inspired Rust framework that compiles to WASM.
Then starts to show off how easy it is to use heroku, while complaining about how complex it is???
And at the end there are some vague screenshots showing a supposedly easier method of deploying things than using heroku, but first you have to learn GitLab CI/CD, Terraform, AWS, and probably a bunch of other things?
And I don't want to download your 200Mb native app that I will only use once. Besides that, the average webpage size is 2Mb which IMO is still too big, where as the average iOS app size is 34.3Mb.
The issue that I have with safari being locked to a specific iOS version is that people on older model such as the iPhone 6 are being stuck with an outdated browser, even though the phone is still useable.
To be fair, Apple handles updating iOS a lot better than Android, but Chrome is not tied to the OS versions, this means I can update Chrome through the Play Store which means: 1) faster update cycle and 2) old android phones can still run the latest Chrome.
I agree users don't want notifications from web pages, but the web is much more then just web pages and I would argue that on web applications users are much more likely to allow push notifications if they get a clear benefit.
Apple is really the only one these days ignoring these standards. Even if it a "dubious process", if there is consensus among the majority browser vendors I would call it standard.
On Chrome you can trigger a add to home screen prompt from your own UI, making it a two touch experience. On iOS IIRC it only works on Safari and not in Chrome, but I could be wrong.
> no one wants notifications from random websites
I am not talking about random websites, but rather web applications that you interact with on regular basis, if Apple cared about the user experience they could have just moved the notification prompt behind a user interaction.
> shared worker ... They burn battery life
If you are building more demanding websites shared workers are a great way to share state and computing resources across and thus saving battery life. Spawing a Worker per tab is more demanding.