Post 9yn6saOvRpMuRFYC5Q by jlhertel@mastodon.technology
 (DIR) More posts by jlhertel@mastodon.technology
 (DIR) Post #9ymv8cxQVn8JYCZRh2 by jwildeboer@social.wildeboer.net
       2020-09-03T17:04:47Z
       
       0 likes, 1 repeats
       
       #UnpopularOpinion - the inflation of web standards and APIs make it impossible to develop a browser from scratch. Competition is eliminated. The web is failing. It cannot be saved.
       
 (DIR) Post #9ymvC7B2c2Mo8ybMu0 by mewmew@blob.cat
       2020-09-03T17:05:34.567977Z
       
       0 likes, 0 repeats
       
       @jwildeboer If it cannot be saved, it already has failed.
       
 (DIR) Post #9ymvMtW3kC5qxbZaPA by jwildeboer@social.wildeboer.net
       2020-09-03T17:07:12Z
       
       0 likes, 0 repeats
       
       @mewmew it’s just that we collectively fail to recognise use the simple reality. And that we haven’t collectively thought about a new approach. It will happen. I’m optimistic.
       
 (DIR) Post #9ymwJhK4ioteEG0Uuu by tychi@fosstodon.org
       2020-09-03T17:17:53Z
       
       0 likes, 0 repeats
       
       @jwildeboer what if we just freeze the innovation?
       
 (DIR) Post #9ymx11eV0tCxjQDjf6 by wauz@mastodon.social
       2020-09-03T17:25:47Z
       
       0 likes, 0 repeats
       
       @jwildeboerThere are many ports left to use. Internet≠ wwwWe could create w2 or whatever we call it
       
 (DIR) Post #9ymxGfhuN8IAItH9e4 by jwildeboer@social.wildeboer.net
       2020-09-03T17:28:38Z
       
       0 likes, 0 repeats
       
       @tychi OK. Let’s construct a list of standards and APIs a browser should support right now. Where do we start? Here’s chrome’s list of stable APIs. https://developer.chrome.com/extensions/api_index
       
 (DIR) Post #9ymxUuR6PIVo2TChXc by tychi@fosstodon.org
       2020-09-03T17:31:10Z
       
       0 likes, 0 repeats
       
       @jwildeboer I think the best way to tackle it is in the pick/ban style.I'll go first: let's keep debugger, it'll probably help with building the *gestures* everything.
       
 (DIR) Post #9ymxv5Xbk34e0djJVg by jwildeboer@social.wildeboer.net
       2020-09-03T17:35:57Z
       
       0 likes, 0 repeats
       
       @tychi it’s not that simple to find a curated list of standards and APIs a browser should support. That’s where the problem starts.
       
 (DIR) Post #9yn6saOvRpMuRFYC5Q by jlhertel@mastodon.technology
       2020-09-03T19:16:08Z
       
       0 likes, 0 repeats
       
       @jwildeboerThat is indeed sad.But also, I put the blame of this mostly on Apple and Google, as they cannot agree on a damn standard to develop applications for their mobile OSs, so they pushed all the shit to browsers, so they act as a middle layer.Progressive Web Applications is the end result of this dispute and mostly why we have so many web-APIs.Who needs the damn webGL stuff after all?
       
 (DIR) Post #9yn72mXz8y8f0MeLx2 by jwildeboer@social.wildeboer.net
       2020-09-03T19:18:12Z
       
       0 likes, 0 repeats
       
       @jlhertel https://caniuse.com/ - only 429 standards to implement. Piece of cake ;)
       
 (DIR) Post #9yn7O24obHwDFZ8fT6 by jlhertel@mastodon.technology
       2020-09-03T19:22:00Z
       
       0 likes, 0 repeats
       
       @jwildeboer429? Nahh, just a weekend and we are done. </sarcasm>
       
 (DIR) Post #9ynGo19fY6O1VYsIKG by jens@social.finkhaeuser.de
       2020-09-03T21:07:29Z
       
       0 likes, 0 repeats
       
       @jwildeboerWell now *that's* something I can agree with. Unfortunately, I guess.On some level, though, we shouldn't be surprised: java, flash, now the browser, and unity, we always seem to be looking for a universal OS abstraction to build applications on. That's fair, IMHO.But I don't think that the hypertext idiom is the right distribution medium for such a platform.