I’m split, but I lean slightly towards no. On one hand, it could be good for discoverability, and it would help my efforts to make a client-side algorithm
On the other hand, it will make one of Lemmy’s problems worse - engagement. Some people will vote less, and it’s already feeling a little quieter around here as the numbers settled after the Reddit Exodus. I doubt it’ll be a massive change, but a .5% decrease in voting, permanently, could make a difference
Ultimately, you can see it on federated platforms, so shrug
It just makes too much sense… The only way to get past electron is a better electron. Or just fix electron
We’ve been going after this concept for decades now. That’s what java swing was supposed to be, what python gtlk was supposed to be, and I’m sure there were others before that and there’s been a hell of a lot since then
It’s all trade-offs between flexibility, ease of use, and performance. Also between maintenance cost, portability, and existing library support
Electron is a good compromise. The execution could be better, but it’s come a long way. There is no one size fits all solution, but there are some decent options that handle that compromise differently