diffify

We’ve just passed an important milestone for diffify: our app for tracking Python and R package releases has just turned 1 year old! To mark this exciting occasion we are delighted to announce an “anniversary update” featuring numerous quality of life improvements. This post will outline the latest changes and tease at some exciting developments in the works… First, though, we would like to take this opportunity to thank everyone that continues to use the app and welcome any new users to the service.

It has been 6 months since the launch of Diffify, our website for comparing package releases. We are delighted to announce that, in addition to CRAN’s 20,000 R packages, you can now track 1600 popular Python packages! What’s included? The current criteria for a Python package to be included in Diffify are: The package is listed in the top 2000 PyPI packages according to download statistics. The package has had version releases since 1st May 2020.

We’re now three months on from the initial release of Diffify, and what a few months it’s been! We thought now seemed like a good time to give you an overview of the big updates that Diffify has been through since it’s launch. Recognition and user feedback We are delighted to see that our app has been quickly adopted by the R community: R Weekly now displays links to Diffify for updated CRAN packages!

This is part two of our two part series Part 1: Theming diffify for accessibility: Part 1 Part 2: Theming diffify for accessibility: Part 2 (this post) In Part 1 of this two-post blog series I covered contrast sensitivity and colour vision deficiencies and related terminology. Here, in Part 2, I’ll cover the changes we made to diffify.com and take a quick look at some tools we used to help us.

This is part one of our two part series Part 1: Theming diffify for accessibility: Part 1 (this post) Part 2: Theming diffify for accessibility: Part 2 For most web developers the switch from desktop or laptop to mobile device will be something they do most days. We know what a designed-only-for-desktop experience feels like on a mobile device and it isn’t great. But accessibility on the web isn’t just about checking that your website is largely agnostic to the physical size of your users’ screens, it’s also about making your content available to those users who have physiological impairments.

You know that sinking feeling that you get when you’re months into a big project and you log in one day and nothing works? Turns out something has updated and things have been removed that you needed and now you need to spend hours-days figuring out what’s changed and your masters deadline is getting closer and … ok, apparently this took me back to a very specific event. But I’m sure most of that sounds familiar to you if you’ve ever programmed something over a longer period of time.