Post #2207125

2019-06-24 07:32 UTC

For any concerned webdevs my advice is: 1. Most importantly: Test in multiple browsers 2. Avoid JavaScript, there's too much bloat there for new browser engines to afford. If you must use JS discuss how new web standards can help you move away from it 3. Use progressive enhancement/graceful degradation, this will help new browsers get started quickly 4. Don't worry about your pages looking the same everywhere, only care that they look good everywhere 5. Related to (2), try out Intercooler.js

Replies (2)

@alcinnz@floss.social 2019-06-24 07:45

But seriously I do want help developing a new browser engine! I've got enough on my plate, but as a browser developer I feel a certain responsibility. So if you're a developer who's also concerned about the collapse in browser divirsity, or even just security or accessibility, please tell me your interests and I might be able to suggest a smaller component for you to tackle in whatever spare time you have.

Open ##2207126
@alcinnz@floss.social 2019-06-26 07:09

I've expanded on these ideas in a developer guide on my site: https://github.com/alcinnz/Odysseus/blob/gh-pages/developer/web-bloat.md The points are basically the same but rearranged and collapsed together a bit. And I added a couple of points arguing that Web and Native should complement each other, and we need to be better about linking between them.

Open ##2207127