WebAssembly’s post-MVP future

Re:WebAssembly’s post-MVP future by wild_preference on Monday October 22, 2018 @07:23PM (#18279462)

Meh, the issue with Electron is performance. The actual dev environment is decent, like how trivial it is to bring your own abstractions like React. Being able to inspect element and use Chrome's debugger. Being able to use whatever text editor you want. Using a compile-to-JS language. etc.

I'm certainly not using Xcode + Cocoa + the MVC abstraction for iOS/macOS apps because it's the superior way to build software. It has its own warts, like the effort it takes to swap out MVC with some other pattern, or how it comes with no async abstractions -- you'll just be writing callback code like JS developers had to before the Promise.

It's tempting to unmask "ugh, JS developers" as a bunch of idiots, but I think you'd only be kidding yourself if you think your pet environment is some global optimum.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by thrower123 on Monday October 22, 2018 @09:58PM (#18280194)

Every time I start doing anything moderately complicated in JS, I rage at how much more difficult it is compared to slamming together a UI in .NET.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by eksemplar on Tuesday October 23, 2018 @01:31AM (#18280935)

Really because WPF, web forms or razor all seem very inferior to me than VUE or react.

Hell when we were still building interfaces in .Net we paid a subscription to use Telerik on the frontend because the standard .net stuff is absolutely terrible.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by pjmlp on Tuesday October 23, 2018 @02:58AM (#18281302)

Where is Blend for Vue or React?

I never used Telerik, and we only bought ComponentOne once for a Windows Forms project, started before WPF even existed.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by voltagex_ on Monday October 22, 2018 @11:45PM (#18280586)

WinForms or WPF? I can throw together a (terrible) HTML page faster than I can remember how MVVM is meant to work.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by thrower123 on Tuesday October 23, 2018 @07:16AM (#18282374)

I'm a lover of WinForms, since I cut my teeth on VB6 and MFC... it's surprising how decent you can make things look with a little polishing.

It's nuts that visual layout editors for the web have, if anything, regressed from the WebForms editor in Visual Studio 2008.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by pjmlp on Tuesday October 23, 2018 @03:01AM (#18281315)

MVVM is meant to work the same way as Angular bindings work.

In any case you aren't obliged to use MVVM in WPF, it is just a best practice for easier unit testing and composability. Then again Web Components are only now starting to be a thing.

[ Parent | on HN ]

Re:WebAssembly’s post-MVP future by pjmlp on Tuesday October 23, 2018 @01:33AM (#18280948)

I do native across multiple platforms and Web, being coding since the mid-80's, so the experience is not constrained to a single pet.

[ Parent | on HN ]