OpenSilver VS Ember-cli

• 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.

• Convention over Configuration
  Ember-cli enforces strong conventions for file structure, naming, and project organization, which reduces decision fatigue and makes it easier for developers to jump between different Ember projects with minimal onboarding time.
• Built-in Tooling
  Comes with a robust set of built-in tools including a development server, testing framework integration (QUnit), asset compilation, and live reload, reducing the need to manually configure and integrate third-party build tools.
• Addon Ecosystem
  Ember-cli supports a rich ecosystem of addons that can be easily installed and integrated into projects, allowing developers to extend functionality without reinventing the wheel for common features.
• Blueprints and Generators
  Provides powerful generator commands (blueprints) that scaffold components, routes, models, and other application pieces quickly, speeding up development and ensuring consistency across the codebase.
• Stable Long-term Support
  Ember-cli follows Ember's release cycle with clear LTS (Long Term Support) versions, providing stability and predictability for teams maintaining large applications over time.

Possible disadvantages

• Steep Learning Curve
  The strict conventions and unique architecture of Ember-cli can be difficult for newcomers to learn, especially those coming from more flexible frameworks or with no prior Ember experience.
• Smaller Community Compared to Alternatives
  Compared to tools like Vite, Webpack, or CRA used with React/Vue, Ember-cli has a smaller community and ecosystem, which can mean fewer third-party resources, tutorials, and community-driven troubleshooting.
• Build Performance
  For large applications, Ember-cli's build process can become slow, and while improvements have been made with embroider, some developers still report slower build times compared to more modern bundlers.
• Rigid Structure
  The opinionated nature of Ember-cli, while helpful for consistency, can feel restrictive for developers who prefer more flexibility in structuring their applications or adopting non-standard patterns.
• Migration Complexity
  Upgrading between major Ember-cli versions or migrating to newer build systems like Embroider can be complex and time-consuming, particularly for older or heavily customized applications.

No analysis of OpenSilver yet.

• 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 / 7 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 / 11 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

• Help! Why does chrome console inner text and my program inner text not return the same values? (spent nearly the whole day trying to extract an element). Turned to reddit as its always had the best community. Any help is MASSIVELY appreciated. Puppeteer!!

  The webpage is LinkedIn.com. While this isn’t a framework, I know that are using https://cli.emberjs.com/release/. Source: about 5 years ago