4 ms·

So this is the nth reiteration of one part of a company trying to embed web-tiles into their native front-end to speed up development because the OS team are un

So this is the nth reiteration of one part of a company trying to embed web-tiles into their native front-end to speed up development because the OS team are under-developed on front-end aspects. Sony tried it on their store-front, as did Microsoft on their start-menu. Curious to what's changed now though to make this work? * Have they solved the security nightmares that cross-domain iFrame call's became? * Is performance and memory overhead just "good enough" now? * How does theming (dark-mode ect) stay consistent? * How does accessibility stay consistent between native->website->native (tabbing, narrator ect).

contextfree 5y ago
RN isn't a webview, it's a wrapper for the platform-native UI framework (in this case WinUI2/UWP); that's what the "Native" in the name signifies.
- throw_m239339 5y ago
  RN does run Javascript code though. The UI should be more responsive (i.e. less latency when it comes user interaction) than a web UI however.
  - oblio 5y ago
    We've had stuff like Tk since however, I don't remember anyone complaining about it. An interpreted language being clue code for native widgets doesn't affect UI speed that much.
    - throw_m239339 5y ago
      > An interpreted language being clue code for native widgets doesn't affect UI speed that much. Did you ever try PHP + Gtk? I beg the differ. All interpreted languages aren't made equal. Furthermore, it's not just "glue code" when all your business logic has to be written in Javascript as well in a React Native app.
- WorldMaker 5y ago
  RN today is WinUI3 and C++/WinRT (and no UWP sandbox). (That's what this Settings panel is shown to be.)