Now find not just one (anecdote) but a trend in HN comments that this tool is recommended to be used when it is clearly the wrong tool for the job?
Really depends on your definition of "reasonable". I could invoke Goodwin's law :)
> and all of their comments within
A majority of the following posts (with regards to Electron) are negative...
> ust promise yourself you'll eventually quit Electron. Electron is nothing more than a deal you make with the devil,
> Don’t just tinker... make it a grand North Star goal to lose Electron, and make performance your moat.
> It being Electron especially explains why it's so much more resource intensive than the other solutions.
> I hope you'll reconsider as your team grows.
> For me personally, memory usage has been a big concern with the growing number of Electron apps
> Indeed - a key competitor, Tuple, does not use Electron, and as a result I won’t even be taking a second look at Pop.
It's interesting that people on HN seem to be in such an obvious echo chamber but also see themselves as outsiders.
Under such conditions, expecting a consistent, well thought out, position from post to post is unrealistic. And not really even all that surprising.
However, since lots of software is still being written in Electron and... essentially none of the criticisms and drawbacks of doing so have been addressed, the anti-Electron group feels like they're being ignored. Because they are. So when they make posts about feeling ignored or complaining about having to repeat the same criticisms over and over without any improvement, that's because that's what's happening.
The anti-Electron people are not saying that nobody agrees with them. They're complaining that their arguments are clearly falling on deaf ears.
App developers want their user to have a good experience (I'm guessing). But it isn't great with electron. But its fund one team or fund 3 ui teams (Windows, Mac, Linux) and hope testing gets them all in sync.
Unfortunately there isn't a great cross-platform solution (qt?) that makes everyone happy (or at least not furious).
This kind of “reply-to-agree-and-pile-on” chain happens on HN a lot, but there are certain topics that really set it off, and Electron is definitely one. The commenters are commenting, the readers are upvoting, and what we end up with is an atmosphere where one side of the conversation is clearly getting more engagement.
> 1. Yes, we’re building on Electron. Yes, we are aware of the performance tradeoffs, but have decided this is the best choice for us. We’re shipping Windows, Mac and Linux clients along with browsers with a four-person team — it’s the only good way right now to do that without features taking six months. We’ve modified the screen sharing pipeline in Chromium to reduce latency as much as possible, because with interactive screen sharing, milliseconds matter.
Literally a massively popular post from this week, and all of their comments within are "Well yes, but theoretically VS Code got it to slightly over a hundred megabytes when idle so naturally Electron's perfect."
https://news.ycombinator.com/item?id=28223515