Reader's Corner No. 75: How HTTPS Works, Removing jQuery from Github.com Frontend, and the Accessibility Cheatsheet

September 19, 2018

Keeping true to our roots in our 75th edition of Reader's Corner with some very technical picks from our developers! The first staff-share is a neat infographic on why we need HTTPS, then comes the Github.com engineering department's explanation for removing jQuery from their frontend, and finally a great tutorial on all things accessibility.


Why Do We Need HTTPS?

Amanda Hart

Source: How HTTPS Works

Takeaway: HTTPS (Hyper Text Transfer Protocol Secure), the [secure] protocol over which data is sent between your browser and the website that you are connected to, can be complicated to understand for laypeople. That being said, it's still an important concept for all web users to at least know the basics about and why it's important (especially as Chrome discourages visiting sites without SSL certificates installed). This comic is both cute and informative and is a great way to explain HTTPS to people who prefer visual learning.

Tags: #HTTPS, #SSL, #Infographic


Removing jQuery from GitHub.com Frontend

Jay Roberts

Source: GitHub Engineering

Takeaway: jQuery was a critical tool for web developers when the iPhone was brand new. Now, more than 10 years later, the standard technology of the web has progressed greatly and we move on from jQuery in favor of native browser capabilities making pages faster and lighter.

Tags: #JavaScript, #jQuery, #Programming


The Accessibilty Cheatsheet

Frank Yonnetti

Source: bitsofcode

Takeaway: Web accessibility is hard to test, so any help I can get to develop for it correctly is a huge value for me.

Tags: #Accessibility



Tell us about the most interesting advancement in IT that you've read about lately!


Comments

jQuery has many convenience features such as chaining, for example: item.addClass('selected').siblings().removeClass('selected'); and you don't have to check for nulls after each selection.

Many functions such as closest() and remove() have no equivalents in IE11, and other things such as replaceWith() and before() are not available even in Edge.

For simple sites it is easy enough to remove jQuery, but for more complex javascript applications, especially apps that have a lot of interactivity, removing jQuery will result in more code, or you will end up writing a lot of utility functions thereby creating your own little clone of jQuery.

Add new comment