61–70 of 72 posts
> designed to allow every man to write code in his mother tongue. Hopefully, by doing so, Citrine will make coding accessible to a wider audience. One day that audience might extend to women.
Ah, but can it speak Emoji? Because, bless them. Not the first time I’ve seen a “let’s make coding more accessible” project make this mistake, alas.
Earlier quoted context omitted.
Love it. I phrased it this way just to trigger you. There is no structural sexism except maybe in some Islamic countries - but I don't hear anyone about that. Women are free to do whatever they want. If they feel offended by words they probably don't belong outside the house.
Well congrats on being a Grade-A douche. I strongly recommend you go find a new hobby—one you can play by yourself—because with salesmanship like that your project is already dead. https://jaxenter.com/wp-content/uploads/2017/04/women-in-com...
Hi, I am the creator of the language, my name is Gabor. You can ask questions if you like. To answer some: - Yes, we use machine translations, they serve as an example, they are far from perfect. Some language files are translated by native speakers. I think the website needs to be more clear about this. - I use gendered language because coding is a men's job, women belong in the kitchen! ;-). No, just joking. Women…
“I use gendered language because coding is a men's job, women belong in the kitchen! ;-). No, just joking. Women are also welcome to become Citrine users. I just think the opening sentence is beautiful, it combines the concepts of male and female in a lovely, natural way ignoring today's PC-bullshit.” Dude, really. If you gave a crap about effective communication you would not just have said that. Hell, you would not…
Weird how a language that exists to be more welcoming and accessible uses needlessly gendered language on its website. "Designed to allow every man to write code in his mother tongue" could easily be written as "designed to allow every person write code in the language they are most comfortable with."
It did say that, before they ran the site through Citrine.
Earlier quoted context omitted.
>I just think the opening sentence is beautiful, it combines the concepts of male and female in a lovely, natural way ignoring today's PC-bullshit. Honestly, I am astonished that you can be so conscious of the effect of language on thinking in the context of programming, and yet so tone-deaf when writing your copy. This is not "today's PC bullshit", it is an effort to eradicate structural sexism going back at least h…
Love it. I phrased it this way just to trigger you. There is no structural sexism except maybe in some Islamic countries - but I don't hear anyone about that. Women are free to do whatever they want. If they feel offended by words they probably don't belong outside the house.
This is unfriendly.
>If they feel offended by words they probably don't belong outside the house.
I'm afraid that with this you move from "tone-deaf" to "overtly sexist".
Is anyone aware of tooling or languages in existence that allow for maintaining codebases with multiple supported languages? I'm imagining something similar to a git hook that performs translation at an AST level, where library can provide a "strings database" that maps it's public members into arbitrarily many languages. I could imagine for multinational companies, it might even be worth hiring dedicated translators…
Ouch. Naming things is, famously, one of the two Hard Problems of computer science. How much harder if you have to name everything, down to the last loop iterator, thousands of times - once for each language that humans speak?
Earlier quoted context omitted.
“I use gendered language because coding is a men's job, women belong in the kitchen! ;-). No, just joking. Women are also welcome to become Citrine users. I just think the opening sentence is beautiful, it combines the concepts of male and female in a lovely, natural way ignoring today's PC-bullshit.” Dude, really. If you gave a crap about effective communication you would not just have said that. Hell, you would not…
If you have technical criticisms please share.
Programmers like you are the reason I finally taught myself how to code, so I would never have to depend on your sort for anything. You’re a smug, condescending martinet with a grossly inflated sense of your own specialness, and the sooner you grow up/the world kicks you to the curb, the better.
So here’s me expressing my freedom of thought and expression by having nothing more to do with you.
I've written once an internationalized parser for another (more established) language. As long as you can output an AST, this works. User feedback was interesting. Some non-native speakers of English objected to this, on the basis that it was a lot easier for them to distinguish language keywords (in English) from user symbols (typically in the user's language); language acted as a kind of syntax highlighter for them…
“they felt it disorienting to express in their own native language programming constructs that they'd learned in English” Trust me, going from natural-language English to programming-language English is just as discombobulating. (Been there, done that; made a deliberate point of remembering that experience.) If you’re only testing it with existing programmers, you’re bound to skew your results because anything new an…
In a way, we already have this test today. Most of the world's programmers are non-native speakers and, by and large, they learn programming languages where keywords are based on English. I've heard people thinking that language localization would be a cool thing, but I haven't heard anyone complain about it not being available.
> Out of interest, is there any more public information of your work here?
No, my comment is all the public info there is about it. My $.02, localizability wouldn't be what I would worry about for a proof-of-concept language.