|
That's great. (Currently on the hate side of my love/hate Java relationship)
|
# ? Nov 16, 2012 02:47 |
|
|
# ? May 28, 2024 21:28 |
|
Using λ instead of halfLife or some other semantically meaningful variable name makes about as much sense as saying foo ࢠ Z/256Z rather than unsigned byte foo.
|
# ? Nov 16, 2012 02:58 |
|
1337JiveTurkey posted:Using λ instead of halfLife or some other semantically meaningful variable name makes about as much sense as saying foo ࢠ Z/256Z rather than unsigned byte foo.
|
# ? Nov 16, 2012 03:10 |
|
Thermopyle posted:That's great.
|
# ? Nov 16, 2012 03:10 |
|
Doctor w-rw-rw- posted:If you're doing Android, I'd say it's more Android, less Java, actually. What kind of stuff are you getting frustrated from? Well, I guess it's actually static typing rather than Java in particular, but since 95% of the time I'm using a statically-typed language its Java (and most of that time it's frustrating Android dev), Java gets the brunt of my hate. I don't have any particular problem with it other than the fact that I'd rather just use Python or Ruby or whatever. If only they were the appropriate tool all of the time... Hmm, I was about to submit this post, and then thought about it some more and I can't really put a finger on why I'd rather write in something like Python than something like Java. It may be just something as simple as that, years ago, I learned on Python. I'm certainly not under any illusions such that I think Python and the like are in any general way objectively superior to Java.
|
# ? Nov 16, 2012 03:57 |
|
PrBacterio posted:vvv Again, just write lambda or something, I don't see the problem. It's longer and less legible? It's like here I am telling you about for loops and you're wondering what's so good about them that you can't do with a while loop and a few extra statements.
|
# ? Nov 16, 2012 04:01 |
|
Thermopyle posted:Well, I guess it's actually static typing rather than Java in particular, but since 95% of the time I'm using a statically-typed language its Java (and most of that time it's frustrating Android dev), Java gets the brunt of my hate. Python is also like 50x quicker to write and takes about 50% less code to do similar stuff. Honestly that's one of the reasons I really like Scala, but it has a pretty big learning curve. It's also a lot pickier about types, but in practice you don't have to write out types 80% of the time. Plus functional programming can make algorithms look a lot more elegant, and it's easier to reason with immutable variables than having to worry about mashups of different states (to me at least).
|
# ? Nov 16, 2012 04:15 |
|
Jabor posted:It's longer and less legible? EDIT: Jabor posted:You started off saying that ASCII should be enough for everyone; can I assume you've changed your mind on that? EDIT again: And I'll just say that from this quoted comment of yours I take it that it seems you still didn't really 'get' what I was trying to say, which is probably my fault, not yours. Hopefully I've now managed to make my position somewhat clearer, though PrBacterio fucked around with this message at 05:06 on Nov 16, 2012 |
# ? Nov 16, 2012 04:24 |
|
ultramiraculous posted:Edit: Those are some pretty simple examples that just happen to be more clear if you're used to thinking in deltas and whatnot. Scala can also become a real, real horror with this poo poo. When adding ★ as an operator starts to feel sane, it's time to step back. You're just creating a horror at that point. I honestly don't think that making operators named <<= and =>= is that bad. But maybe that's just because I write a lot of Haskell. The real horror in that first link is calling something a 'pimp'.
|
# ? Nov 16, 2012 04:31 |
|
PrBacterio posted:You'll notice that what I said wasn't in opposition to the use of any particular symbol but rather to the idea that the set of allowable symbols should be completely open-ended. You started off saying that ASCII should be enough for everyone; can I assume you've changed your mind on that?
|
# ? Nov 16, 2012 04:52 |
|
Also goddamn man it's not like you're charged 10¢ every post, make a new one if you're responding to someone who posted after you and you actually want them to see it.
|
# ? Nov 16, 2012 05:30 |
|
Jabor posted:Also goddamn man it's not like you're charged 10¢ every post, make a new one if you're responding to someone who posted after you and you actually want them to see it.
|
# ? Nov 16, 2012 05:38 |
|
Thermopyle posted:I don't have any particular problem with it other than the fact that I'd rather just use Python or Ruby or whatever. If only they were the appropriate tool all of the time... I hear very, very good things about JRuby. PrBacterio posted:But taking your argument to its logical conclusion, we'd have to demand for all languages to be written in ideographic writing systems like Chinese, which clearly we don't. Unless such a system is part of the language we'd want to use to build the model of our domain, which happens with math stuff, and when we ourselves write and think with such a writing system. It's fine if English is the language of your development team, as it is for tons of others, and all the ones I've been a part of, but I still don't understand what you think is lost in the utf8 upgrade. e: I could have sworn there was a jquery wrapper that made '$' available as 'ಠ_ಠ' or something ridiculous like that, but I can't find it now. Doc Hawkins fucked around with this message at 06:00 on Nov 16, 2012 |
# ? Nov 16, 2012 05:55 |
|
yaoi prophet posted:Are you saying you have non-latin characters in your source code?
|
# ? Nov 16, 2012 06:13 |
|
Aleksei Vasiliev posted:In strings or comments, yeah sometimes. But I don't see any reason for source code not to use UTF-8. Because there are multiple characters that look the same? Seriously, though, use UTF-8, but you probably shouldn't be straying far from the ascii zone with any code other than output strings or comments (by which I mean, don't use non-ascii characters for variable or function names).
|
# ? Nov 16, 2012 06:59 |
|
I will call an operator ∪ if that's what it does. Of course I'll also set up a binding in my editor so that typing `union` automatically gets converted to ∪, because being able to input your stuff easily is really the important thing.
|
# ? Nov 16, 2012 07:16 |
|
Jabor posted:I will call an operator ∪ if that's what it does. Please no one listen to this guy. Custom binding just to write code isn't okay.
|
# ? Nov 16, 2012 07:22 |
|
Titan Coeus posted:Please no one listen to this guy. Custom binding just to write code isn't okay. Which is why I manually comment out blocks of code by hand.
|
# ? Nov 16, 2012 07:41 |
|
yaoi prophet posted:Which is why I manually comment out blocks of code by hand. Titan Coeus posted:Custom Uh, if that isn't built into your IDE I'm not sure what to tell you.
|
# ? Nov 16, 2012 08:23 |
|
I think at this point this is really nothing more than another one of those "code formatting styles/braces on the same line vs. braces on the next line/tabs vs. spaces/which IDE/language/version control system to use" topics that come down to personal preference and style and we should really leave it alone and let the thread to go back to its original purpose, which is for posting (and making fun of) examples of fantastically bad code.
|
# ? Nov 16, 2012 08:38 |
|
PrBacterio posted:I think at this point this is really nothing more than another one of those "code formatting styles/braces on the same line vs. braces on the next line/tabs vs. spaces/which IDE/language/version control system to use" topics that come down to personal preference and style and we should really leave it alone and let the thread to go back to its original purpose, which is for posting (and making fun of) examples of fantastically bad code. Yeah, it's like whinging about a language you don't use because it doesn't work the way your preferred language works. Tools are meant to be used in certain ways, and are not meant to be used in others. In programming we just happen to have heaps of different tools to solve similar problems. It seems like the focus should be on languages that have terribly inconsistent designs, or when the tools get used in absolutely ridiculous ways.
|
# ? Nov 16, 2012 09:07 |
|
PrBacterio posted:About the anglocentricism I'll just note that as long as we're using languages with English-language keywords there's no way around that anyway, which you'll note is also not a problem. Programming languages are formal languages defined on their own terms "their own terms" just happens to be "on white English-speakers' terms" the vast majority of the time. Non-English speakers having to learn a foreign language before they can even start learning to program is a big problem.
|
# ? Nov 16, 2012 10:12 |
|
ninjeff posted:"their own terms" just happens to be "on white English-speakers' terms" the vast majority of the time. Non-English speakers having to learn a foreign language before they can even start learning to program is a big problem. I've always been interested in that. It's strange how English became "the" language to use when programming. It's always interesting seeing non-English speaking people code and having their comments in Chinese or whatnot.
|
# ? Nov 16, 2012 10:18 |
|
Well then do I have the solution for you http://www.babylscript.com/
|
# ? Nov 16, 2012 10:42 |
|
Suspicious Dish posted:Well then do I have the solution for you Tell me they include a tool which standardises all the names to a given language so that it's actually readable.
|
# ? Nov 16, 2012 14:32 |
|
The question of using non-ASCII characters in source files is germane to this thread in the sense that the real argument against them is that there are so few systems that sanely handle Unicode end-to-end. I don't have the link handy but Raymond Chen has posted a couple times about non-ASCII characters in Windows headers breaking builds in non-Western locales.
|
# ? Nov 16, 2012 17:41 |
|
ninjeff posted:"their own terms" just happens to be "on white English-speakers' terms" the vast majority of the time. Non-English speakers having to learn a foreign language before they can even start learning to program is a big problem. It's not exactly that bad. They really 'only' have to learn to map the words they use for a language's keywords to the English equivalent. Well, as long as they aren't using someone's framework with English-only docs, but nothing is stopping a Russian from writing a great framework with Russian-only variable, method, and class names (for any language that supports Cyrillic) and then telling the world to go pound sand if they want it in English. Comparatively few people would use it, but nothing is explicitly preventing someone from doing it. The main reason I wouldn't want a bunch of Unicode operators in a language is that they'd be a pain in the rear end to type. Otherwise, it'd be pretty sweet to use λ instead of lambda in Python
|
# ? Nov 16, 2012 18:30 |
|
Doc Hawkins posted:I hear very, very good things about JRuby. I hope it's in a better state that Jython.
|
# ? Nov 17, 2012 02:59 |
|
Munkeymon posted:It's not exactly that bad. They really 'only' have to learn to map the words they use for a language's keywords to the English equivalent. You can't assume every English-based programming language's keywords have a direct mapping to words in every other natural language. It's generally the case for other languages from around Europe, sure. But there's no Japanese (for example) word that maps to "while" or "if" alone. Here's another hard-to-spot source of privilege in programming languages: being written left-to-right, top-to-bottom. Imagine growing up reading right-to-left and then being told you have to read the opposite way to read programs, and "that's just the way it is". Don't even get me started on printf!
|
# ? Nov 17, 2012 03:35 |
|
Thermopyle posted:Well, I guess it's actually static typing rather than Java in particular, but since 95% of the time I'm using a statically-typed language its Java (and most of that time it's frustrating Android dev), Java gets the brunt of my hate. Having just returned to iOS from Android, it's a breath of fresh air. I think the biggest switch in my style is that I write code, then I write the methods and types I need for it, whereas in Java, types and methods come first, then their usage (to a degree - it obviously involves switching between one and the other). Java's just so enterprisey, and while I like that when I'm doing stuff that's more pure like web-based stuff, where the only I/O you really need to think about is a text (or similar) request/response, it just feels bad when doing mobile.
|
# ? Nov 17, 2012 04:44 |
|
ninjeff posted:You can't assume every English-based programming language's keywords have a direct mapping to words in every other natural language. It's generally the case for other languages from around Europe, sure. But there's no Japanese (for example) word that maps to "while" or "if" alone. I grew up reading right-to-left, and it wasn't a big deal at all. You really only need to know the same 30-40 english words to understand any computer language. Basic level english is also very easy to learn, and if you spend any amount of time on the internet then you probably know it already. It also means that if you go abroad, you can work as a programmer wherever you go ,that multi-national teams can work on the same project easily and when Tokyo university invents a new language, you don't have to bust out the Japanese dictionary just to understand the hello world example. I'm a Hebrew speaker, and php's T_PAAMAYIM_NEKUDOTAYIM still fills me with rage every time.
|
# ? Nov 17, 2012 11:03 |
|
Hell I thought it was enough of a pain dealing with Sony sample code where it would be something like:code:
|
# ? Nov 17, 2012 15:37 |
|
Clearly we need to do all of our coding in Lojban.
|
# ? Nov 17, 2012 19:47 |
|
∪λ∑ != ëçæ I'm fine with math symbols being available, any science symbol is ok in my book, but typing out accented characters is a pain in the loving rear end.
|
# ? Nov 18, 2012 01:15 |
|
KARMA! posted:∪λ∑ != ëçæ Those benefits are true of other similar languages, though, I guess English was just lucky to get it's foot in the door first.
|
# ? Nov 18, 2012 08:27 |
|
The Gripper posted:easily distinguished from eachother That's pretty facilIlIlIlIlIlIlIlIlIe
|
# ? Nov 18, 2012 08:48 |
|
Carthag posted:That's pretty facilIlIlIlIlIlIlIlIlIe
|
# ? Nov 18, 2012 09:12 |
|
The Gripper posted:Not only that, characters represented in ASCII are very easily distinguished from eachother - even by non-english-speaking people Dyslexia is a Myth. Wake up sheeple! (Also, english needs more than ascii to write). quote:and have the benefit of being very flexible as far as correctness goes (as a written and spoken language). The spelling and pronunciation have nothing in common though? I thought you ought to know about this being tough and thoroughly challenging for newcomers to plough through, a linguistic hiccough or cough perhaps. quote:Poor grammar and bad spelling and even poor pronounciation can make something difficult to understand, yet still not stray obscenely far from it's intention. This might be more to do with humans and not the language spoken. quote:Those benefits are true of other similar languages, though, I guess English was just lucky to get it's foot in the door first. Social and cultural factors are the major influence on the spread of English.
|
# ? Nov 18, 2012 13:10 |
|
tef posted:The spelling and pronunciation have nothing in common though? e; none of the pronunciation crap is applicable to programming though. The Gripper fucked around with this message at 13:30 on Nov 18, 2012 |
# ? Nov 18, 2012 13:21 |
|
|
# ? May 28, 2024 21:28 |
|
The Gripper posted:Oh I know, I was just generalizing that neither (bad) pronunciation or (bad) spelling on their own make the language impossible to understand (which doesn't help in learning english, but does aid in english speakers understanding improper use of english). A lot of other languages aren't as forgiving in that aspect, namely ones where a single character or transposing of characters can heavily affect entire phrases like Mandarin and Japanese, and basically all languages where the written word doesn't directly map to pronunciation at all (I know there are cases in english where this can also happen, too.) I was just wondering if you had any pubic sources on the deanliness on the forgivingness of english.
|
# ? Nov 18, 2012 13:30 |