Earlier quoted context omitted.
Indeed, that is why Microsoft has created teams to support React Native for macOS and Windows, on Windows case it makes use of UWP, which new roadmap (WinUI 3.0) was announced at BUILD 2019, with more details to come up on Ignite. Yeah, Microsoft bashing never grows old.
Yeah ok, fair point. Someone at Microsoft cares a bit about Windows, just not anybody working on the UX bits.
Electron 7.0
281–289 of 289 posts
Re: Electron 7.0
#282Earlier quoted context omitted.
I think this peaked some time around 2015. Back then, I remember many developers getting up in arms about following Apple's guidelines to a T, or insisting that Android apps look like a hyperactive stack of colorful paper cutouts under a direct light. Since then, I think many of us have gotten tired of looking at overdesigned sameness that by now we all know will age quickly. Programmers no longer see the sense in ch…
You are right but at the same time I am willing to bet you 5 years later someone else will make the opposite argument and be upvoted the same. It's a pendulum.
Re: Electron 7.0
#283Earlier quoted context omitted.
Yeah ok, fair point. Someone at Microsoft cares a bit about Windows, just not anybody working on the UX bits.
Given the market size of laptops, 2-1 hybrids and graphical workstations running Windows, the UI/UX toolings that are available, I fail to see what you mean.
Re: Electron 7.0
#284Earlier quoted context omitted.
Microsoft Office has gotten way better over the years. They used to design the UX around the idea of "Office Users", not "Mac Users"
This is very frustrating when supporting a mixed team of Mac and PC users on office. I would prefer it to be the same everywhere.
Re: Electron 7.0
#285Earlier quoted context omitted.
It’s clear that you aren’t their intended audience. Due to a choice you have made to not use a more common platform. Your responses sound like you’re upset; why? You made your choice. They made theirs. Accept the reality, accept the trade offs, or make changes. Complaining about the decisions made by other people isn’t useful.
Due to a choice you have made to not use a more common platform. Actually I'm primarily using MacOS as a desktop these days. I've happily paid for a variety of apps (e.g. Omnigraffle, Monodraw, Lightroom). Your responses sound like you’re upset; why? You made your choice. Beyond the usability issues that constantly dismissed out of hand by developers, Electron is a crass and dishonest attempt at redefining portable a…
You don’t think the crass and dishonest part is a story that you’re telling yourself? To me, it’s an engineering trade off. There is no need to criticize what others have chosen, and afaict, no evidence to support this hyperbolic questioning of their intentions.
Re: Electron 7.0
#286Earlier quoted context omitted.
As someone who has worked a lot with both Qt and React at my current job, I feel that React is significantly easier for almost everyone. Qt’s complexity negates a lot of its benefits in most hands.
Maybe it is my age showing off, but React easier than Qt??!
Re: Electron 7.0
#287Earlier quoted context omitted.
You are right but at the same time I am willing to bet you 5 years later someone else will make the opposite argument and be upvoted the same. It's a pendulum.
I'd bet on the next UI standard being a cross-platform library. Electron-like, but with much more efficient stack, and with binding to multiple languages.
Re: Electron 7.0
#288Earlier quoted context omitted.
I'd bet on the next UI standard being a cross-platform library. Electron-like, but with much more efficient stack, and with binding to multiple languages.
I'd bet on "if you can't beat em', join em". Reactive component-based architectures a la React/Vue have won. The DOM has won for the view layer too. And with wasm, you get your bindings to multiple languages. See: Blazor (it's just the first, more are coming). As for desktop apps that could benefit from proper concurrency, lack of a browser sandbox, full system access, etc. - server side Blazor is quietly pioneering…
As a front-end dev, I'm not entirely sure I agree with that. The DOM has some annoying performance limitations, and I'd love to be able to use something better for rendering. I think what the DOM has shown, is that cross-platform and the ability to easily do custom look and feel are crucial.
Re: Electron 7.0
#289Earlier quoted context omitted.
Well, Slack is currently taking almost 3 GB of memory on my machine. Not entirely sure if that's due to Electron or Slack, but I have never found an Electron app that didn't consume vast swathes of memory. https://imgur.com/GscRFD7.png
It is not because of Electron. An empty Atom window containing 5 source code files consumes about 120MB of RAM. For comparison with native apps, an empty iTerm2 window uses 100MB, and so does an empty Notes.app window. The base memory footprint imposed by Chromium is not that significant.