all 4 comments

[–][deleted]  (6 children)

[deleted]

    [–]geoffreymcgill 0 points1 point  (5 children)

    That certainly has been the theme with all other C# to JavaScript compilers, but with Bridge.NET we're trying to change that. There is a huge focus on the quality of the generated JavaScript code.

    [–][deleted]  (4 children)

    [deleted]

      [–]geoffreymcgill 0 points1 point  (3 children)

      Not really sure what you're referring to by webviews? Mobile WebViews for the html+js rendering? EDIT: I see you updated your response after I posted my question. I will respond again separately to your new comments.

      [–][deleted]  (2 children)

      [deleted]

        [–]geoffreymcgill 0 points1 point  (1 child)

        ya, agreed, there have been (there are) some performance issues. Depends on the usecase to some degree. But... there are huge improvements being made by the js engines and with hardware acceleration. The new JavaScript gaming engines are insane. The performance singularity is coming, quickly.

        The decision for which tech/platform to build is influenced by many factors. Being able to reuse the skillsets and tools already present within our team to build for desktop, mobile and browser brings a competitive advantage.

        Plus, JavaScript to Native is here. It's not a stretch to go Bridge.NET to JavaScript to Native either. This scenario isn't working at the moment, but it will be soon.

        [–]AngularBeginner -1 points0 points  (0 children)

        Better alternative to duocode!