4 ms·
I mostly agree, but: > Sometimes APIs on the web are difficult because they're poorly designed. > But sometimes APIs are difficult because they're solving rea
by flohofwoe 8y ago
I mostly agree, but:
> Sometimes APIs on the web are difficult because they're poorly designed.
> But sometimes APIs are difficult because they're solving really hard
> problems that developers aren't aware of. Before those APIs are thrown
> in the trash, we should take a step back and think about why they were
> built in the first place.
I think the reality is much simpler. Most Web APIs are bad because they have been designed to solve an overly specific problem, with the assumption that Javascript is too slow, and finally messed up by too many cooks.
The worst examples are WebAudio and WebRTC. A good Web API (unfortunately
about the only one) is WebGL.
Most Web APIs deserve to be thrown into the trash TBH.
Browser makers and web standard makers need to read the extensible web manifesto again and again and again:
https://github.com/extensibleweb/manifesto https://github.com/extensibleweb/manifesto