5 ms·

People want better browsing experience from their browsers, not a terrific MIDI experience. If you want those, native apps would be a better choice from a techn

by waon 6y ago

People want better browsing experience from their browsers, not a terrific MIDI experience. If you want those, native apps would be a better choice from a technical standpoint.

robbrown451 6y ago
Why are they better? I'm developing for browsers, and it runs amazingly well. I wouldn't know how to build such a thing natively (for one thing, it layers on top of and syncs with music videos), and wouldn't have bothered. There are tons of web apps, games, etc that "people want." Maybe you don't want them, but other people do. Even HackerNews is more than browsing, since you can post to it. I get that some people want their browser to do a very limited subset of the things that a browser like Chrome can do. I don't think that is actually the view of Mozilla, but if it was, and they actually advertised that, I suspect they'd have even lower usership.
- fsflover 6y ago
  Because fingerprint https://panopticlick.eff.org/ https://panopticlick.eff.org/ is already very bad and we do not want even more tracking.
- waon 6y ago
  Because creative apps tends to be heavy on resource, requires hardware access, and benefits from native libraries and native UIs.
  - robbrown451 6y ago
    Isn't that kind of a circular argument? So I should develop my creative app as a native app because it needs hardware access and browsers don't support that. And browsers shouldn't need to support hardware access because app developers should just build native apps. Maybe you should try my app. (try it at https://pianop.ly/grid.html https://pianop.ly/grid.html ... it works ok in Firefox in "player piano" mode) All the other stuff other than MIDI, browsers support just fine. (including one critical thing, ability to embed, synch with and overlay on top of youtube videos) Browsers support an awful lot of things, because people want that. I can tell you with regard to my app, I highly doubt a single developer could build it as a native app that was available to as many people.
- fsflover 6y ago
  Because it not a good idea to combine all functionality in one single program (in this case the browser). It leads to bugs and security problems. See also: https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_a...

by waon 6y ago

People want better browsing experience from their browsers, not a terrific MIDI experience. If you want those, native apps would be a better choice from a technical standpoint.

robbrown451 6y ago

Why are they better? I'm developing for browsers, and it runs amazingly well. I wouldn't know how to build such a thing natively (for one thing, it layers on top of and syncs with music videos), and wouldn't have bothered. There are tons of web apps, games, etc that "people want." Maybe you don't want them, but other people do. Even HackerNews is more than browsing, since you can post to it. I get that some people want their browser to do a very limited subset of the things that a browser like Chrome can do. I don't think that is actually the view of Mozilla, but if it was, and they actually advertised that, I suspect they'd have even lower usership.

fsflover 6y ago
Because fingerprint https://panopticlick.eff.org/ https://panopticlick.eff.org/ is already very bad and we do not want even more tracking.
waon 6y ago
Because creative apps tends to be heavy on resource, requires hardware access, and benefits from native libraries and native UIs.
- robbrown451 6y ago
  Isn't that kind of a circular argument? So I should develop my creative app as a native app because it needs hardware access and browsers don't support that. And browsers shouldn't need to support hardware access because app developers should just build native apps. Maybe you should try my app. (try it at https://pianop.ly/grid.html https://pianop.ly/grid.html ... it works ok in Firefox in "player piano" mode) All the other stuff other than MIDI, browsers support just fine. (including one critical thing, ability to embed, synch with and overlay on top of youtube videos) Browsers support an awful lot of things, because people want that. I can tell you with regard to my app, I highly doubt a single developer could build it as a native app that was available to as many people.
fsflover 6y ago
Because it not a good idea to combine all functionality in one single program (in this case the browser). It leads to bugs and security problems. See also: https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_a...