@carloschida@vercel@leeerob Hey Carlos, thank you for reporting this! We shipped a fix earlier today, both formats should now respect your browser's locale.
@consolelogwill@asidorenko_ I've found a pattern that generally works for me is to have both live in the same file and define the skeleton as a property on the component itself:
function A({ id }) {}
A.Skeleton = function ASkeleton() {}
<Suspense fallback={<A.Skeleton />}>
<A id={1} />
</Suspense>
@Baconbrix@gabimoncha That's definitely one reason, but I think what plays an even bigger part is the ability to keep users around instead of handing them off to an external application
I'm surprised by the number of PRs I receive that don't have prettier formatting applied. It's no big deal, but I'm left wondering... Do people really not have format-on-save enabled?
@LinguaBrowse@eveningkid The separation isn't as clear cut in completely native applications, I agree. However, AFAIK it is very common for iOS apps to run operations in another thread with
```
dispatch_async(dispatch_get_main_queue(), ^{
// non-blocking code here
});
```
@LinguaBrowse@eveningkid Your third point is exactly what I'm saying, moving animations to the UI thread frees up the JS thread for application logic which seems to me like a positive thing.
@LinguaBrowse@eveningkid While I agree on the first point, I doubt it is fair to compare web performance to native in this case since I don't think most web applications offer the same level of interactions and gesture recognition as native applications.
@eveningkid@LinguaBrowse I think a big part of that is simply that the NativeScript model is inherently inferior due to being single threaded whereas React Native uses separate threads for UI and JavaScript - leaving more room for non-blocking animations and interactions.