gem1129.bsky.social
@gem1129.bsky.social
Reposted by gem1129.bsky.social
AH on the choice. Very reasonable imho. x.com/transitive_b...
Travis Fischer on X: "Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's @ahejlsberg explanation from his @wesbos interview: https://t.co/vmG1bRzGzn" / X
Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's @ahejlsberg explanation from his @wesbos interview: https://t.co/vmG1bRzGzn
x.com
March 12, 2025 at 12:05 AM
AH on the choice. Very reasonable imho. x.com/transitive_b...
Reposted by gem1129.bsky.social
React Native's networking stack is based on native primitives:
🍏 iOS & macOS: NSURLRequest
🤖 Android: OkHttpClient
🪟 Windows: winrt::Windows::Web:Http
They implement XMLHttpRequest in JavaScript based on JS-native bindings to those, and from there, they use whatwg-fetch to polyfill fetch().
🍏 iOS & macOS: NSURLRequest
🤖 Android: OkHttpClient
🪟 Windows: winrt::Windows::Web:Http
They implement XMLHttpRequest in JavaScript based on JS-native bindings to those, and from there, they use whatwg-fetch to polyfill fetch().
February 5, 2025 at 6:17 AM
React Native's networking stack is based on native primitives:
🍏 iOS & macOS: NSURLRequest
🤖 Android: OkHttpClient
🪟 Windows: winrt::Windows::Web:Http
They implement XMLHttpRequest in JavaScript based on JS-native bindings to those, and from there, they use whatwg-fetch to polyfill fetch().
🍏 iOS & macOS: NSURLRequest
🤖 Android: OkHttpClient
🪟 Windows: winrt::Windows::Web:Http
They implement XMLHttpRequest in JavaScript based on JS-native bindings to those, and from there, they use whatwg-fetch to polyfill fetch().