That's almost certainly not the point being made. Building a workflow around non-free development tools means that eventually you're going to find support for your favored tool evaporating.

Using non open source tools is Harlech ever a problem. Yes the support can disappear, but so can one for FLOSS software. I am working on a tool which is based on a graveyard of abandonned open source libraries and taking them over is absolutely not an option. The only thing you can do is to slowly move to an alternative and hope that it will get maintained. With tools the choice is usually very easy because you can switch to other tools any time.

This seems only be a problem for software developers though. Every other profession out there builds their workflows around proprietary expensive tools and it works out all fine.

But we software developers are a special kind. We expect people to work for free (as in no money) to create tools for us we then can use to earn money.