Agreed. I think it's a bad idea (for the stated purpose, not as a nice little project which is always good to see of course). There's already sort of a problem in spanish texts (articles, some books) where the author chooses to make up (often cringy) translations for terms that don't really have an accepted counterpart in spanish. So they just translate the thing literally, and without consistency. Each author decides what to translate and how. This is probably an issue too in other languages.

Example: "arreglo". Why would you call an array that way?

Learning a programming language is already hard enough (especially the first one) to add another axis to the process, and you'll get much less out of the experience if you are limited to a "vainilla" universe.

Yeah, that's a good one.

The terminology is well established and standardized in english, so if someone says things like bus, heap/stack allocation, driver, or even simple random things like timeout, tracker, to trim a string, to wrap an error, etc. everyone knows what you mean but when people write their docs in spanish and make up their own terms (let alone the mental effort required to translate every term), you can quite easily end up with a huge mess.

Por favor, programad en inglés y usando los términos conocidos y si tenéis un equipo a cargo forzad a hacerlo así, os lo agradecerán en el futuro!

I remember being completely mystified the first time I heard "arreglo" at my first job.

I have a theory that the frequency of the use of those translations (arreglo, aplicativo) in a workplace is directly proportional to the amount of bureaucracy in it.

It turns out that there may be a shared etymology from Old French "arraier" (I arrange, prepare, put in order; contrast En. disarray). So, as far as choices go it's not necessarily a bad one.

Until someone comes along and translates 'heap_alloc' as 'asignacion_al_monton' or 'DatabaseDriver' as 'PilotoBaseDeDatos' (I wish I had made up the latter).

Here's a really interesting talk (in Spanish) about programming in one's (natural) language: https://www.youtube.com/watch?v=cZ2ZGNUqWXg

Thanks, interesting project but I disagree with the proposal. Actually the project is more about using your own style for coding and then transpiling that, than the language itself. And both are terrible ideas IMHO.

In fact, what's popular now is to do just the opposite: linters and formatters which force the same coding style for everyone, which is way easier to implement for all the different languages and way more reliable.

And as far as the language itself is concerned, I'd say that it is a bad idea as well because of context switching, translating what you type into other languages (which is not a trivial task for both machines and humans) and because, as I said above, you still need a good english proficiency level if you want to be a good developer, so it makes sense to prepare your students for the real world by teaching programming in english and getting used to it.