• 302 Posts
  • 4.81K Comments
Joined 2 年前
cake
Cake day: 2023年7月7日

help-circle






  • I continue to contribute in the most minor way to both, and it’s very true that Hughes LARGELY runs this repo. This is becoming a problem, especially since the majority of companies do not contribute, though they use the upstream just like everyone else.

    If Amazon, Google, Dell, Hetzner, Equinox, DR, DO…etc all paid their fair share, they’d be able to pay honest contributors just simply for making what is already available MORE readily available. That’s what this project is about.

    On the hardware manufacturer side: AMD, Nvidia, Intel, Realtek…etc are also not chipping in.

    This is a CRUCIAL project for larger adoption for home users. Yes, most enterprise-sized companies manage their own semver releases for firmware, but they still use these tools. They should contribute, not only because it’s the right thing to do, but a miniscule amount of money for them to do so to ensure the same people making this such a success can continue to do so.




  • Honestly, it seems kind of moot if it already works in the browser. It’s a negligible amount of work to make an app use a browser engine to run offline to run their stack, but some heavy lifting to do a direct port to any specific OS without an adjoining framework to help in the cosmetics of everything.

    That being said, they could also use a unified framework to do one release for every OS, which again is pretty much the same as making offline work for anywhere.

    My fear is they do something stupid like build in GTK, and then QT users have UI problems, or vice versa. Seems easier to just go with a unified (non-electron) kit that runs everywhere the same way.