> If you wrote your website in some shitty language and you need lots of server power just to serve the home page you will end up saving a lot of money from blocking those countries.

At that point, might as well rethink the engineering happening at your company well before considering blocking countries' IP spaces, no?

how dare you besmirch react on hn

edit: i'll say it again too, test me.

You can do both.

As a cold business decision, just as it makes sense to fire customers who are more hassle than they are worth, it's also makes sense to block prospective customers who are more hassle than they are worth.

Of course, if you engineering is better, you can pick a different false-positive vs false negative trade-off.

It’s all a cost/benefit ratio. Even if the most efficient language is used, given a sufficient number of requests, it might make sense to block them no?

If you don't care about your paying customers ever traveling there and still wanting to use your service (or at least be able to unsubscribe from it without doing a chargeback), sure.

As a customer, I try to avoid any company that considers "blocking the bad countries" a reasonable security posture. If nothing else, it's usually indicative of other irrational and frustrating decisions that might hurt me later.