Please don't do this! Han Unification causes your Japanese text look weird when displayed with a Simplified Chinese font, likewise with a Traditional Chinese or Korean font.
Yes, unless you run OOBE\BypassNRO.cmd from cmd to bypass the network connection step, since there's no "skip" button anymore.
Even this is somewhat broken. If you run this after connecting to the Internet then it doesn't do anything and still forces you to use a Microsoft account (unless you somehow get it to throw you back to that page).
By "base CSS" are you referring to using @apply? That's generally not recommended from what I understand, with componentization and reuse being preferred over most usages of @apply for this purpose.
> Showing the user nonsensical warnings like
"Someone is trying to steal your credit card information!!!!11" only creates
confusion and misconceptions about security.
So is this suggesting that browsers should automatically trust all certificates? The Kazakh government sure would like that to happen.
I found that my Discourse instance consistently took ~250 milliseconds to display the forum post list (according to the little box at the top left corner). After getting annoyed with Discourse, I went back to Invision Forum and I see about ~95 ms for the same thing, including sending the response to my browser.
#6: These are full-width brackets. Most Chinese input method editors will output full-width characters by default instead of the half-width ones that you're accustomed to.
For example: ，。；：【】
If you ever see an Amazon listing have full-width characters, they're almost certainly either Chinese sellers or sellers that are really good a copying and pasting from Chinese sellers.
On M1 Max with Safari 15.5, it took me about 40 seconds of fast scrolling to get it to start stuttering occasionally. Then, another 30 seconds to get it to start blanking out for a second at a time. And finally, another 30 seconds to get it to start taking seconds to render. I won't give the number of posts before it started lagging because I don't know the exact number.
On my phone (iPhone 13 Pro Max, albeit on the iOS 16 beta), it takes Safari about 15 seconds of scrolling before the scrolling drops to around 40fps from what looked close to 120fps. Then, another 20 seconds to start seeing things rendering halfway before jumping around and then rendering the correct post. This isn't necessarily a fair comparison due to the usage of beta software, but even on an M1 on production OS software it doesn't seem to be much better. Chrome 102 on macOS handles the exact thing that I did without any problem at all.
It's especially bad when you have a lot of videos on your dashboard. If you only have image posts, it might take a bit longer to start stuttering.
This has been the case for years, so it's nothing new. I remember this being a problem almost a decade ago, on an 4th generation iPad with the A6X SoC. Things have improved since then for sure, but those it's probably mostly hardware improvements that's helping.
I'll accept blaming Twitter's horrible performance on its use of React Native Web, but not Tumblr.
If I understand what you're trying to say correctly, I need to say that I'm speaking fully from a user experience standpoint as an end user. I am not a Tumblr engineer. Anecdotally, out of the few people I know that still use Tumblr, they use desktop and mobile Chrome to access the website. I don't have any statistics on how many people use the apps.
So, to me, Tumblr's website is already the main point of access, and these performance problems don't exist on Firefox or Chrome. I'm not talking about server-side response times, I'm talking about the time to render posts on the client. I find that a lot of times, after scrolling, you have to wait a few seconds before you see anything but the blue background that Tumblr has.
So, no, I'm going to pin it on Safari if (even) Firefox can deal with it.
Safari works amazingly for small websites, but for websites with infinite scrolling like Tumblr and Twitter, it becomes unbearably slow after the first hundred or so posts. Historically, Safari is slow to adopt new web features, and it STILL doesn't have web push notifications (and more).
You can run these same websites on Android Chrome just fine, even on a lower-powered Android phone. I'm not sure if they're using APIs that need to be polyfilled on Safari, or if Safari is just trash.
At this time, I'm convinced that if Apple allowed other browser engines on the App Store, this would not be a problem at all, not that I can test it out anyways.
It's even worse than that. Right before that, the article claims that the Chinese language is "almost the same as the first inscriptions from nearly 3,200 years ago".
https://www.scientificamerican.com/article/russia-is-trying-...