Hi Ben,
I work at Twilio with Notify. Thank you for the feedback. We recently started auto-generating our helper libraries (before it was a manual process.) This let's us ship new products and new features into all of our supported languages very quickly. It also opens up the opportunity to add additional languages. I'd love to hear more about languages you'd like to see (sounds like Go is important, others?) and hear more about how you are using Twilio to see if we have a better solution for you. Drop me an email: bchia [at] twilio [dot] com
With new offerings like Copilot and presumably this, they get a chance at a fresher start BUT unless you want to handle interacting with Twilio's endpoints directly you're going to have to wait for your client libraries to catch up, which might not be a problem with NodeJS, but for instance my company uses a third-party Golang library that's two years old and has only received minor tweaks in the past 6 months. It will probably not be updated with new features soon or ever, and should I want to utilize these new features I would have to extend or re-write the library myself.
Finally Twilio provides no ways of including metadata in an SMS submission (which is a huge freaking oversight) and makes it very difficult to associate a number with an account. The most accepted answer for that problem currently is to use the Twilio number as a foreign key for an account, which a) does not work with Copilot as you have no control over which number will send the message and b) requires each account to have its own ($1) number, which does not scale.