Iframely VS OpenSilver

• “No code”
  Instead of API calls, an option to use our HTML template and some JavaScript spice.
• JSON
  Only two endpoints to choose from and connect: complete Iframely data or a simple oEmbed connector. Both have the html field for you to embed.
• Cards and URLs previews
  Engage your users with URL preview cards, just like they expect in a modern app. Change cards design easily in your settings.
• React and JavaScript
  React, and other JavaScript runtimes won’t let you run third-party scripts. Iframely fixes this by hosting media in an iFrame instead.
• Responsive embed codes
  Rich media will resize and fit your site’s design on any device, with a correct aspect ratio or a horizontal height.

• Cross-Platform Compatibility
  OpenSilver enables developers to create applications that run on multiple platforms, including web browsers, by leveraging WebAssembly, which enhances the reach and accessibility of applications originally written in Silverlight.
• Silverlight Code Reusability
  Since OpenSilver supports C# and XAML, much of the existing Silverlight code can be reused, minimizing migration efforts and reducing time and costs associated with redevelopment.
• WebAssembly Based Performance
  By utilizing WebAssembly, OpenSilver applications can achieve near-native performance, leading to efficient and responsive user experiences in web applications.
• Open Source Flexibility
  As an open-source project, OpenSilver offers developers the ability to contribute to and modify the platform, fostering a community-driven environment and encouraging innovation.
• Integration with Modern Web Technologies
  OpenSilver allows integration with modern web technologies and frameworks, enabling developers to enhance applications with contemporary features and functionalities.

Possible disadvantages

• Incomplete Feature Support
  Not all of Silverlight's features are fully supported in OpenSilver, which might necessitate additional workarounds or re-implementations for complex applications.
• Learning Curve for Migration
  Developers familiar with Silverlight may need to learn new patterns and practices related to web development and WebAssembly when transitioning to OpenSilver.
• Browser Compatibility
  While WebAssembly aims to be universally compatible, some differences in performance and behavior might occur across various browsers, potentially requiring additional testing and optimization.
• Community and Support Maturity
  As a relatively new and open-source project, OpenSilver might have a less mature support ecosystem compared to more established platforms, impacting the availability of resources and community support.
• Dependency on WebAssembly
  OpenSilver's reliance on WebAssembly means that any limitations or ongoing development challenges associated with WebAssembly could directly impact the capabilities and performance of OpenSilver applications.

Tracking Iframely since Mar 2021.

• Show HN: Browser-based .NET IDE with visual designer, NuGet packages, code share

  - XAML autocompletion, AI error fixing, split editor views The visual designer is the differentiator: 100+ drag-and-drop controls for building UIs. But the NuGet and sharing features work even if you ignore the designer entirely and just... - Source: Hacker News / 8 months ago

• .NET MAUI Is Coming to Linux and the Browser, Powered by Avalonia

  Beside already mentioned, there is OpenSilver[1]. Supports Silvelight and WPF. Renders to DOM+WASM. They are also planning support for MAUI. [1] https://opensilver.net/. - Source: Hacker News / 12 months ago

• Revisiting WASM for F#

  I would also say that IF blazor worked on a browser plugin like silverlight did, today that's not the case it is built on the webassembly standard which and it is being adopted in the browsers which means once it gets on the web, it is... - Source: dev.to / almost 3 years ago

View more