Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WebWindow, a cross-platform webview library for .NET Core

blog.stevensanderson.com

Post reply on HN
Print view View original

31–40 of 55 posts

Re: WebWindow, a cross-platform webview library for .NET Core

#31

Post by girvo »

bob1029 wrote: post #25
thdrdt wrote: post #8

Has anyone experience with Blazor in production? I would like to jump into it but it still feels a little immature to me.

I would recommend starting with the server-side variant of Blazor on a non-production test app to familiarize yourself. You can easily move to client-side WASM mode once you need to (or feel comfortable doing so) without any major changes to your codebase. Our long term plans (aka by end of 2020) are to rewrite all of our internal tooling from SPA (RiotJS) w/ JSON APIs to server-side Blazor. The principal motivations…

It’s so interesting to me that in some ways, it’s like old-school PHP (but very different and much better in others!)

Blazor has been on my radar for a while. I think it’s architectural choices and workflow are a boon to most developer shops!

Re: WebWindow, a cross-platform webview library for .NET Core

#33

Post by Benjamin_Dobell »

branchseer wrote: post #30
throwGuardian wrote: post #7

Alternatives: 1. Webview: https://github.com/zserge/webview 2. Lorca (Chrome): https://github.com/zserge/lorca 3. Carlo (js/Chrome): https://github.com/GoogleChromeLabs/carlo

And my shameless plug: https://github.com/patr0nus/DeskGap

This is the first I've heard of it. So I can't say much about the project itself. However, by the look of it DeskGap is at least taking the right approach, where as most these other projects (there seems to be a new one every week) miss the mark.

Electron Pros:

1. Consistent JS runtime/API

Electron Cons:

2. Huge distributions (bundling a full browser)

3. No re-use of components (every app is huge)

Electron Pro?/Con?:

4. Consistent rendering / WebKit monoculture

By the look of it DeskGap keeps Electron's biggest pro and solves its two biggest cons. The only "issue" is that there may be rendering inconsistencies. However, given we want to avoid a WebKit monoculture, I see this as a pro more-so than a con.

With that being said Microsoft have themselves migrated to WebKit; so the WebKit monoculture looks likely regardless. For consistency I guess that's even another tick in DeskGap's corner, although it'd be nice if on Linux (for example) it could use Firefox when present.

Carlo is interesting for a similar reason, but perpetuates the WebKit monoculture.

Re: WebWindow, a cross-platform webview library for .NET Core

#36

Post by Lord_Zero »

fbelzile wrote: post #18

This looks like a nice solution to save some time for cross-platform developers on .NET Core. I'm sure we're going to see a lot more of this once the new Chromium version of Edge is released mid Jan 2020 (which will include the new webview2 component). If you don't want to add an external library to do this, or your source is already platform dependent, just use the default web view component of each operating system…

Yes this is still a very alpha package, fallback support for non chromium-based edge has not yet been implemented.

Re: WebWindow, a cross-platform webview library for .NET Core

#37

Post by chrismorgan »

zamadatix wrote: post #29
saurik wrote: post #17

Earlier quoted context omitted.

So most of these techniques used to have the problem that on Windows "any browser" was always "Internet Explorer"; but while I don't disagree that this is still an issue, it is much much much less of an issue now that Internet Explorer is Edge and Edge is Chromium (which I am not saying is a good state of affairs for the web as a whole, but makes this use case not fall as easily to this complaint).

But I don't think Edgium is replacing Edge/IE as the system web component. It's no different than having Chrome installed except it replaced the Edge icon in the start menu instead of making a new one.

In each case, the new thing is added with a new interface, and the old remains. In this case, the new thing is https://docs.microsoft.com/en-us/microsoft-edge/hosting/webv....

Re: WebWindow, a cross-platform webview library for .NET Core

#38

Post by mappu »

fbelzile wrote: post #18

This looks like a nice solution to save some time for cross-platform developers on .NET Core. I'm sure we're going to see a lot more of this once the new Chromium version of Edge is released mid Jan 2020 (which will include the new webview2 component). If you don't want to add an external library to do this, or your source is already platform dependent, just use the default web view component of each operating system…

I think setting x-ua-compatible ie=edge doesn't mean use the Edge EdgeHTML engine - it means enabling "Edge mode" in IE, which means "the latest available version of IE" and you end up with IE10 or IE11.

EdgeHTML can be embedded, but only using the WinRT API, not the ActiveX WebBrowser control.

Re: WebWindow, a cross-platform webview library for .NET Core

#40

Post by ryanthedev »

justinmchase wrote: post #10
thdrdt wrote: post #8

Has anyone experience with Blazor in production? I would like to jump into it but it still feels a little immature to me.

No but I agree, it seems a little risky. I would wait for the next generation of web assembly changes to come down the pipe before investing in this too heavily. Very interesting experiment though.

There is no reason it couldn't run a wasm file? As long as the OS browser supports it.

I feel like this is the UI abstraction layer. If you want to run chromium, there is no reason you couldn't extend it.

Code is prime for extending and enhancing.

Post reply on HN