Yes but is it worth paying a monthly subscription in order to avoid some config files? I donno. Then you will have the problem in if things go wrong or if you do something very different it's closed source so it won't be easily fixed or prioritized since there is no community.

I dunno really. I'm pretty sure my organization will be willing to cough up the fee.

Me personally -- I would rather see it staying fully opensource and be funded through open collective or EU grants or something, like a lot of core stuff should. The fact this model doesn't work is sad.

I feel that something that the whole FE community gravitates to converge on should stay that way to prevent rag pulls and license dramas, otherwise it sabotages the process of converging on the same set of tools in the first place. Then the whole work will be wasted and eventually the project will die out and we get back to the same mess.

That being said, I get that the problem they are aiming to solve is a big pain point and whoever solves it -- they deserve money, but don't deserve to keep the whole community hostage to their whims indefinitely.

Then again, if people can pay 20 bucks a month for oracle lottery tickets selling infinite wisdom one token at time, why not pay actually helpful people doing great tools.

I think for a company the answer is yes, definitely. A monthly subscription is nothing next to a salary. Not that this will eliminate a whole engineer but... It might. It'll get close, depending on how big the project is.