I'm German, and I would not want that. German grammar works differently in a way that makes programming a lot more awkward for some reason. Things like, ".forEach" would technically need three different spellings depending on the grammatical gender of the type of element that's in the collection it's called on. Of course you could just go with neuter and say it refers to the "items" in the collection, but that's just one of lots of small pieces of awkwardness that get stacked on top of each other when you try to translate languages and APIs. I really appreciate how much more straightforward that works with English.

Programs aren’t written by a single team of developers that speak the same language. You’d be calling a library by a Hungarian with additions from an Indian in a framework developed by Germans based on original work by Mexicans.

If no-one were forcing all of them to use English by only allowing English keywords, they’d name their variables and functions in their local language and cause mayhem to readability.

[Edit:] Even with all keywords being forced to English, there’s often half-localized code.

I can’t find the source right now, but I strongly believe that Steve McConnell has a section in one of his books where he quotes a function commented in French and asks, “Can you tell the pitfall the author is warning you about? It’s something about a NullPointerException”. McConnell then advises against local languages even in comments

Excel functions are translated. This leads to being pretty much locked out of any support beyond documentation if your system language isn't English.