On: Google Chromium, sans integration with Google

[hart_russell]

I’ve used Firefox as my daily driver for over 5 years. I’ve literally never encountered what you’ve described. The only reason I use chrome is to cast video to my Chrome cast

[robbrown451 → hart_russell]

So I guess you don't use MIDI. I do. (I develop for it too... you simply can't do stuff like this in Firefox, but you can in Chrome, and it's pretty cool: https://www.youtube.com/watch?v=NV6rdmdZnkA )

And I'm sure you've dragged tabs around, maybe you don't care about the different experience, but it's hard to deny you've seen it.

[waon → robbrown451]

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 → waon]

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 → robbrown451]

Because fingerprint https://panopticlick.eff.org/ is already very bad and we do not want even more tracking.

[fsflover → robbrown451]

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_a...

[waon → robbrown451]

Because creative apps tends to be heavy on resource, requires hardware access, and benefits from native libraries and native UIs.

[robbrown451 → waon]

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 ... 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.

[vanous → robbrown451]

This is very cool. It says 'runs in your browser', maybe change it to 'runs in your Chrome browser'.

[robbrown451 → vanous]

Thanks. Yeah I know, I tried to have the fewest words possible. Technically it runs in firefox, you just can't do the midi thing. (my daughter hates watching music videos if they don't have the colored notes displayed and making sounds)

I also suggest that pink is a color of the rainbow, which is an even worse offense from my point of view. :)