jazzfool

No, this is a non-problem. If Microsoft stuck with Win32, just like how Apple stuck with Cocoa, this wouldn't be an issue.

There is no right way to design a GUI library, so ignore the people that insist you read a book and follow the paradigms it mentions to a T. In fact, we really need less of those OOP GUI libraries right now. Definitely try poke around with reactive, etc.

The "stateful" way you present is not at all how you would approach that problem in an ECS. I think you misunderstand what ECS refers to.

> It doesn't really matter if Electron has code you won't use.

It does matter very much when it negatively impacts your application's performance and user experience.

I definitely didn't dismiss the benefits Electron provides, in fact I completely acknowledge those benefits. The thing is, those benefits don't have to be exclusive to an unsuitable platform like Electron. What's stopping us from bringing that developer productivity to a desktop platform?

This post mostly focuses on app development for independent developers. However, these points are exaggerated even further for entire teams and companies where you actually have the time and resources to invest into the appropriate technologies instead of forcefully trying to reframe every development problem into a web problem (if all you have is a hammer...).

- Sent from my 32gb MacBook

So you'd rather use a website to do heavy photo manipulation (Photoshop), edit a feature-length movie (Premier Pro), or compose GPU-heavy 3D effects (Nuke)?