3 ms·
Ping me when it can WebKit EDIT: this was flippant of me, but I was trying to make a real point. I'm simply too used, as a front-end dev, to the flexibility I
by 1attice 4y ago
Ping me when it can WebKit
EDIT: this was flippant of me, but I was trying to make a real point.
I'm simply too used, as a front-end dev, to the flexibility I get from CSS and HTML and SVG and React, and React-Three-Fibre for fancy stuff. Put it in Electron and boom.
Yes, it's a horrible, horrible mess. Yes, it's ungainly. Yes, it's twenty layers of abstraction.
But Electron apps have come an enormous way. My favourite apps are now all Electron. While non-Electron apps make a strong start, they simply cannot keep up with the innovation made possible by here-you-go-ing the last 30 years of web progress.
Yeah, I know that's not the use case for something like this. Opposite! Opposite! But you know what? For most medium-sized 2022 front-end workloads, widgeting is a thoroughly solved problem.
By 2030, most apps will include an entire web browser, just as insurance for future market-competitive growth rate.
This is why adopting MAUI, Blazor, etc, is folly, and even this kit -- aside from it obvious hacker-cool minimalist street cred -- is the sort of 'meme dependency' (rhymes with meme stock) that HN adores despite the fact that it will see almost no non-toy use cases.
Get yourself a web browser. HTML is the VT220 of 2030.