Twitter | Search | |
Sean Thomas Larkin (肖恩) Jun 12
(Ive never been able to say this yet) πŸ™‹Well Actually!πŸ™‹ All of Office 365 is (almost finished) being completely rewritten in this little scripting language called . And Skype And Microsoft Teams And And all of Debug Protocol (instead of C++) nbd
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 12
Replying to @jfbastien
Also, C++ is RFCs for adopting JavaScript's module system because it's so damn good for static analysis. 😍πŸ”₯😍πŸ”₯ cc please make me look stupid if I'm wrong
Reply Retweet Like
Sean Thomas Larkin (肖恩)
And in case you were wondering. This is the goal and beauty. (At least the pieces I can talk about 😏)
Reply Retweet Like More
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
To clarify since this someone exploded a bit πŸ˜‚πŸ˜‚ 1. We've been talking about our use of react-native and react-native-windows for a bit now! Here's the git repo! Feel free to learn more! 2. The "never have been able to say before" pt was 'Well Actually'
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
Here's some more react-native-windows resources!!!! Hopefully we can standardize on the JavaScript compilation pipeline to match what is cannonical in the community ()
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
And here's ReactXP which is baked in to Skype (consumer) to make it possible to ship cross plat and single code base native applications with consistent UI
Reply Retweet Like
Scary Mary Branscombe Jun 13
Replying to @TheLarkInn
why does it need electron on win32? How could that be remediated away?
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @marypcbuk
Well think like legacy win versions that don't support the UWP plat. I can't confirm honestly if that's what O365 is going to handle it but we have that compiler target for those cases.
Reply Retweet Like
Scary Mary Branscombe Jun 13
Replying to @TheLarkInn
a .NETlike UWP runtime for Win7 would solve a lot of problems ;)
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @marypcbuk
Sounds like somethings that are above my paygrade :-) to even speculate on. <3
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
Another great blog to tune into our work with react-native react-native-windows!
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
Reply Retweet Like
Jonathan Kupcho Jun 13
Replying to @TheLarkInn
Does this mean we’ll be getting Microsoft support behind Linux and macOS bindings for React Native given that VSCode is multi platform?
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @jrkupcho
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @TheLarkInn
Okay since this thread keeps going, and getting shared, I have some points of clarification that I think you should know about!!!
Reply Retweet Like
Jake Dohm Jun 13
Replying to @TheLarkInn
No good deed goes unpunished πŸ˜‰
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @JakeDohm
In CYA mode. πŸ˜‚
Reply Retweet Like
Stan Chang Khin Boon Jun 13
Replying to @TheLarkInn
Do you see wasm improving the native bridge more in the future?
Reply Retweet Like
Sean Thomas Larkin (肖恩) Jun 13
Replying to @lxcid
In my opinion, I think WASM can improve the Native Bridge (in general) for any products. However, without DOM support for WASM, its hard to see it bridging UI capabilities.
Reply Retweet Like
Raymond Siu πŸ¦€ Jun 13
Replying to @TheLarkInn @Microsoft
Is there a reason why went with react-native-windows instead of contributing or even taking over the proton-native library? Proton-native looks promising to get native performance for desktop apps across all major desktop platforms.
Reply Retweet Like