Earlier quoted context omitted.
This is a interesting topic because it exposes one of the great sins developers commit - we don’t pay each other. I’m not talking about nickel and dimeing your fraternity, but there is certainly a reasonable price for a lot of these packages and plug-ins we install that can create financial autonomy for a lot of people via modest efforts.
Developers are the toughest customers because we all think: "that's just a small script and a cron job" done in a weekend and basically worth $0. All the while staying each day in a meeting costing a cumulative $xx(x) just to announce what the job for today is.
I think the real problem is that most developers naturally plug in the value of their time on a hobby project/in school (which is ~$0/hr) when deciding if a time-cost tradeoff is worthwhile. Since the answer is almost always no if you incorrectly value time at $0/hr and management usually can not do the analysis themselves, management pattern matches and determines that spending money on developer tooling is essentially never worthwhile and that sums like $5k (which few people would spend on personal projects) are outrageous. If the correct time-value analysis was done, you would get outcomes more like electrical engineers (who generally make less than high-end software developers) where companies will spend literally $50k/yr/engineer on tooling to make them 50% more productive since that actually makes perfect business sense based on the amount they are being paid. In contrast, if you went to management in a software company pushing for a $50k/yr/developer expense they would probably laugh you out of the room or require some totally outrageous improvement like 10x for everybody.