[cjk]

Mighty is such a great example of attacking the symptom(s) of the problem ("Chrome/the web is slow") rather than the root cause (rampant page size/complexity bloat, inefficient use of RAM/CPU, etc.). What a waste of talent and money.

[AlmostAnyone]

How exactly should this talent and money change other's apps and companies? They are solving a problem, you're just talking idealism.

[cjk]

Idealism? Hardly. The fact that anyone thinks that Mighty needs to exist signals a problem with the entire web and/or app development ecosystem, in my opinion.

We should be talking about ways to either 1) make it possible to develop performant and resource-sensitive web apps, or 2) make it dramatically easier to make native/native-feeling apps in a way that doesn’t involve so much legacy cruft.

The lack of a solid reason #2 is why Electron-based apps exist and are thriving. Making native apps for each individual platform is hard and resource-intensive.

I have long been a proponent of native apps, but I will be the first to admit that it’s not that simple for small/resource-limited teams. The rise of Electron/etc. is a failing of the pro-native segment of developers. We need a better alternative.

[AlmostAnyone]

Sure, it signals a problem - I just don't get what you think this group of people should've done with that problem other than what they're doing. They're solving a real problem with a real solution - you're just talking about what the ideal world would look like, but it's not actionable by a team like Mighty in any way.

[6510]

If you give the devs 2 extra clock cycles they find ways to use 4 extra without doing anything new.