OpenSilver – a plugin-free, open-source reimplementation of Silverlight

Re:OpenSilver – a plugin-free, open-source reimplementation ... by skrowl on Monday March 09, 2020 @02:14PM (#22527977)

If I recall correctly, not being able to do a plugin free version of Silverlight is one of the reasons Microsoft invented Blazor ( https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor ).

The devs listed it as one of their reasons for "why?" in a community chat.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by Ciantic on Monday March 09, 2020 @06:55PM (#22530816)

Blazor, while a good effort, is still an experiment. Microsoft Office etc. are React apps, and has one of the most maintained React libraries: https://github.com/OfficeDev/office-ui-fabric-react/

I will believe the Blazor effort if they start rewriting Fabric UI components with Blazor.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by pjmlp on Tuesday March 10, 2020 @02:18AM (#22533218)

Office is React, because of C++.

Office and WinDev teams are the main reason why Longhorn failed, their collaboration with DevDiv wasn't particularly stellar.

They were pretty happy to redo Longhorn ideas using COM instead, then rejuvenating it into what is now UWP, naturally creating an incompatible .NET stack in the process, which might finally be done with when .NET 5 gets released.

Also Office team is so deep into C++ they even maintain their own VC++ branch.

You won't see those guys touching anything .NET beyond the absolutely necessary.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by oaiey on Tuesday March 10, 2020 @12:49AM (#22532806)

Officially it is no longer an experiment.

Otherwise I agree. Blazor will never be what they imagine it will be. And why should the office team migrate to another tech stack. That is wasted money.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by luxuryballs on Monday March 09, 2020 @08:09PM (#22531375)

When I see how absurdly complicated these front-end JS frameworks are it makes me really hope that Blazor can deliver. But for some reason it also feels similar to times in the past where a word for promising tech was never more than a word. But please work, I don’t need or want two routing implementations and an entire MVC stack to manage on the damn client...

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by JamesBarney on Tuesday March 10, 2020 @12:32AM (#22532740)

I've now done two small client projects in blazor(server side) and it's amazing for small to medium sized cruddy apps with a small user base. I

On the fist project I was able to build out small apps almost twice as fast as react. And this was with 1 day of previous blazor experience before the first project.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by jjkaczor on Monday March 09, 2020 @02:45PM (#22528378)

Apparently OpenSilver uses Blazor (https://www.opensilver.net/announcements/introducing-opensil...)

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by brian_herman__ on Monday March 09, 2020 @02:24PM (#22528092)

Yeah blazor seems to be a re implementation of the same ideas with webassembly and a newer version of .net. I have a feeling it will have the same security holes eventually.

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by Moto7451 on Monday March 09, 2020 @03:17PM (#22528703)

Since it runs in the Browser JS sandbox there will be a lower security footprint than the NPAPI Silverlight plugin. JS libraries can certainly still cause other web security issues but you shouldn’t be able to escape the browser just because you’re running this library.

https://developer.chrome.com/apps/npapi

[ Parent | on HN ]

Re:OpenSilver – a plugin-free, open-source reimplementation ... by brian_herman__ on Monday March 09, 2020 @04:51PM (#22529653)

Oh thats reassuring I just thought since its similar to native code my bad

[ Parent | on HN ]