Depending on when the channel was introduced, the backend implementation of a channel can vary wildly. Some were written in Node, others in Ruby, some where wri

Depending on when the channel was introduced, the backend implementation of a channel can vary wildly. Some were written in Node, others in Ruby, some where written internally, others were written by the service owners. When IFTTT released the developer platform, they were solving two needs: 1) creating a consistent channel infrastructure, and 2) providing a tool for developers to write channels so they don't have to. It seems like they are shutting down some of their legacy services, which is probably a good plan for a company with no revenue stream. Not a good plan, however, to make it look like it is the developers' fault.