Sometimes we're forced to interact with bad software, or at least feel forced to. To use it temporarily, or to implement compatibility with it - to negotiate with bad software. But that is what bad software wants, and bad software rarely holds up its own end of the deal.

Being an email client

At my job, we develop a web service that provides customer relations management features. Our clients wanted the ability to email a customer from within our application. We discussed a few ways to do this and ended up biting the bullet and making our web service act as a rudimentary SMTP client. I hated this, of course. But I thought we would just implement basic SMTP functionality and be done with it. If we had've known the slippery slope of negotiating with additional bad software we'd end up on, we wouldn't have done this.

The first price we paid was the need to know the SMTP settings for each provider. There are protocols for discovering this called autoconfig and autodiscover, but many providers implement neither, so we had to manually find out the settings for the providers used by each of our clients. Also, some providers don't allow SMTP access with your actual login password; you have to use a separate "application password", and we usually find this out when a client complains to us that it doesn't work for them. This is an ongoing price.

The second price we paid was to Microsoft, for Outlook dropped support for SMTP AUTH PLAIN in 2017 in favor of AUTH LOGIN.

Yes, this thing. Documented as obsolete in fucking 2003, in favor of AUTH PLAIN. Yes. Far as I can tell, Microsoft dropped existing support for a modern replacement in favor of a system that was deprecated 14 years earlier. Microsoft dropped existing support for a modern replacement in favor of a system that was deprecated 14 years earlier.

And naturally since AUTH LOGIN is obsolete, the Go stdlib doesn't support it. I had to copy some unexported code from net/smtp to implement support for AUTH LOGIN.

The third price we paid was that as soon as the feature was released, our clients demanded HTML emails, sending me in search of a Javascript rich text editor library to pollute our app with. It proved much more difficult than expected to find a library that suited our use case. We settled on Quill as the least bad option, using a hack to make it work in shadow DOM, but discovered too late that it has a serious problem: the way it represents its content as HTML relies on having a lot of Quill-specific CSS, so it would show up wrong if you pasted Quill's output into an email. But at this point the customers had become very impatient, so my orders were to negotiate with Quill by parsing and fixing its HTML server-side - which I could only do a partial job of because fixing the way it represents nested lists was too complicated to be practical.

But at that point we couldn't back out. Our clients had already got half the feature and we couldn't not finish it for them. What looked like an acceptable sacrifice at first - implementing basic SMTP client functionality - roped us into an endless quest of increasing sunk costs and customer frustration and new pieces of bad software we had to negotiate with.

Wix

I once accepted a freelance gig that involved working with Wix. I was well aware that these cookie cutter website platforms are nasty, but I'd never worked with Wix before so I did a quick google search and found out that you could write Javascript, so I thought "no problem, I'll be using custom Javascript for all of this job so I won't have to deal with Wix itself too much". I was wrong. Wix features and limitations crippled my efforts at every turn, turning what should've been a one-week job into a one-month job that severely lowered my overall happiness.


Bad software has a vision for this world entirely incompatible with ours. Do not negotiate. Do not compromise. We must expel it from our lives, even if that makes them harder in the short term. Bad software is your enemy, and this means war.



This page was last modified 2021-12-03 00:10 (UTC).

Subscribe via RSS feed: https://yujiri.xyz/rss.xml

This site doesn't host comments because that would be against my principles: discussion belongs in a dedicated, decentralized medium like Lemmy (tag me if you start one!).