The web continues to amaze me. With all its variety and different changes to the platform it’s hard to see a straight pattern, if there’s even (just) one. But it’s wonderful to see what is being changed, which features are added to the platform, which ones get deprecated, and how browsers implement more and more technology to protect the user from malicious website attacks. It’s interesting to see that these security features nowadays are getting as much attention as a feature for developers which shows the importance of privacy and security and how unstable and insecure the web was in the past.

But the best thing about all this is, that it shows how important it is to stick to the things that people give us. Instead of implementing our own solutions for everything, it’s often way better to re-use an existing system. Not only is it safer to rely on, but also less work while more inclusive to extend a native DOM element with a custom element instead of writing our own custom element from scratch. If we think about whether we should build our own version of SSL or use an existing software for this, why would we build a clickable element based on nothing instead of altering the behaviour of an a or button element? And why would we check for resource host validation on our own, if the browser gives us an API for that? This week’s articles are all around these topics.