I'm not native English speaker, but I wish people would just accept that English is Latin of computers.
I still have to come to servers installed in German or French and guess by memory where stuff are.
I still have to come to servers installed in German or French and guess by memory where stuff are.
Let me guess, you're french?
Online communities (including StackOverflow and Hacker News) do much the same thing by putting rules in place about how people talk with each other. When people break those rules, we get upset, because we see those breaking the rules as 'outsiders' and a threat to the community.
I believe that language can have much the same effect. When English comes in, it often results in people forgetting local mythology, songs, rituals, etc, as a result of forces like Hollywood and Simon Cowell. The community withers and is replaced by the great 'meh'.
People argue that newcomers need to learn 'two things at a time', English and programming. I think that's absurd. No programming language (cue the COBOL people complaining?) is remotely similar to English, the language. Keywords are limited and it's a very foreign way to talk to a machine. Not a language in which you're going to ask where the next loo is.
You might recognize some of the things you had to type to make your name show up in an endless stream on the screen as words when you learn English as a foreign language. Fun moment. But until then, this is really just painting buttons in green instead of red.
I think the idea of that project is neat, interesting. But I don't believe that this is a good way to do things and I cannot imagine that I'd use something similar when my kids are old enough to start exploring this field.
And let's face it, the vocabulary of programming languages is tiny.
if(something){loop = while} else {loop=if} loop{print("hi")}
and it's not immediately obvious why that isn't valid in text, while in scratch it is.
I don't think its the language though that makes things easier.
The only reason that wouldn't work is bad language design. In e.g. Smalltalk or TCL it's fine.
I don't think it means what you think it means.
I just memorized things. And they'll learn a little bit of English
They don't need to know what 'if' means, they just need to learn "you use if to do this"
(Now, to be fair the docs were in my native language, that helped a lot)
Similarly, some people don't know English. Maybe they're curious about programming. Should they have to learn a whole new language first? Or be distracted by the fact that the foreign programming language they have to write is also written in a foreign natural language?
I'm not sure I even agree with your premise. It's a bit premature to worry about having to interact with code written by people that are just learning programming, isn't it? Like anything, when you empower people to learn things like this you have to trust them to have the decency to write programs in English in settings where there might be other people who don't speak their language that have to deal with their programs. Or trust that they wouldn't be hired for such jobs in the first place.
> I'm not native English speaker,
And? Does that give your argument more weight?
If somebody isn't willing to put in the tiny bit of effort to learn the tiny bit of english required for programming, they're not willing to put in the huge amount of effort that is required to learn programming anyways.
We have enough horribly documented code that needs maintenance, there is no need to add horrible documentation in hundreds of languages.
No, because he already knows English.
The proclamation "We should tax the rich less" is a self-serving sentence whether it comes from someone who was born into wealth, or it comes from someone who became rich later in life.
> If somebody isn't willing to put in the tiny bit of effort to learn the tiny bit of english required for programming, they're not willing to put in the huge amount of effort that is required to learn programming anyways.
I think you're coming from the viewpoint of "what would I do to learn programming if I had started from scratch today". But like I've argued, this is not a good view of the process of learning to program! It's more like you are vaguely interested in some discipline or skill, or might need it for something, and so you want to dip your toes in it. You have no idea whether you will like it or not, or how far you will take it. To put up all these demands -- what they should learn and focus in order to in time become your ideal programming colleague -- is just too much to demand of someone who is just exploring a new world to them and don't know where it will take them, if anywhere. How about they learn to actually put things like for-loops, if-statements and such together, before you demand that they should embody all the skills to write great documentation, use best practices, and whatever else?
Just think of all the different things that are "bad practices" that even experienced developers can manage to do with a clear conscience. You can't pick one aspect and demand that a green programmer should have the personality and disposition to know beforehand that such things are "bad practices". People can learn and change.
But why even bother. These topics just devolve into downvote/upvote battles.
And he didn't have to learn it at some point?
My english was pretty much nonexistent until I picked up programming.
Like I said below, nobody is arguing against beginner languages/tools like scratch and logo that could essentially be programmed in emoji, for what it's worth.
But people are arguing against "real" programming languages being translated, because that's a waste of everyones time.
No. That's the difference between this and the guitar: you can't buy a few bits of guitar. But you can learn words like 'print', 'var' or 'for'.
I'd steer this more into the land of 'manhours spent localizing are manhours wasted' rahter than
> to worry about having to interact with code written by people that are just learning programming
"Real" programming languages aren't suited for beginners because error messages are usually to cryptic and should contain hints how to solve the problem.
I'm likely to have to live with results of this. I already do to some extent.