What the Maintenance guy can beothered to learn or not learn, is of no concern to you.
It's definitely of concern to me if I no longer get asked to quote on projects for that factory. There's no point in me being right and unemployed.
I agree with you that not learning ST would be doing yourself a disservice, because you're absolutely right, there are places where it is appropriate to use, and I have used it in those places.
But in my opinion, it's foolish to completely disregard the level of expertise and the particular role that the maintenance technicians play in the environment you're selling your product into. It may be different in different parts of the world, but in my neck of the woods and in my industry, it's almost guaranteed that within 18 months of us putting a system in, management will want a small functional change to how something happens, and they will want the guys that they are paying good money to be onsite 24/7 to be able to do it without having to call in outside contractors. If we sold them something that they couldn't do that to, we'd soon find ourselves without a lot of clients.
I'm not saying I never do it, I'm just saying that I want to be sure I've got a good reason for doing it.
"This is a very advanced and specialized part of the software, and it should not be modified ad hoc without advice from the machine supplier. It is a tried and tested function and we can guarantee that the code here will not be the source of any common problems" is a good reason.
"The maintenance technicians at this facility are well-trained and can understand complex code" is a good reason.
"This facility has no maintenance technicians and they will be required to call in specialized contractors for any PLC-related issues or modifications anyway" is a good reason
"It was quicker and we made more money from the job" is not a good reason
"I don't care about your maintenance guys, they just need to reach the same skill level as me" is definitely not a good reason.