91–100 of 364 posts
Earlier quoted context omitted.
It confused me as well. "0.. is less than count"?
Personally, I find that just having "0..count" requires a bit of thinking on my part trying to decide if it's inclusive or not. "0..<count" instantly tells me that it's not including value, and follows the matematical interval notification [0..count] vs [0..count)
Here in Ukraine it would be very hard to get adoption of a programming language that is named after a Russian military base. This is the rare case where bad naming choice really hurts. No matter how good is the language, you will have to hear and pronounce that name many times a day, and even associate yourself with it (e.g. "a Kotlin developer" in your resume). Not something to be taken lightly.
Here in Ukraine it would be very hard to get adoption of a programming language that is named after a Russian military base. This is the rare case where bad naming choice really hurts. No matter how good is the language, you will have to hear and pronounce that name many times a day, and even associate yourself with it (e.g. "a Kotlin developer" in your resume). Not something to be taken lightly.
Earlier quoted context omitted.
If they open source it, maybe someone should fork it called Kiev.
Ironically, the name "Kiev" would be no less offensive becuase this spelling of the name implies that this is a Russian city, not a Ukrainian one. The official and correct spelling is "Kyiv", see http://kyiv.of-cour.se/ for explanations why.
Nitpick, the Hello World comparison is more like: Swift print("Hello, world!") Kotlin fun main(args: Array ) { println("Hello, world!") }
Kotlin has a REPL
Earlier quoted context omitted.
If they open source it, maybe someone should fork it called Kiev.
Ironically, the name "Kiev" would be no less offensive becuase this spelling of the name implies that this is a Russian city, not a Ukrainian one. The official and correct spelling is "Kyiv", see http://kyiv.of-cour.se/ for explanations why.
I like swift's conditionals without brackets, OTOH the syntax for string interpolation is ugly
Ugh, I know it's something that literally every programmer on earth can and often does bikeshed, but Swift just got string interpolation syntax wrong . Parentheses are something that are often part of the interpolated expression... they shouldn't be part of the interpolation syntax itself.
Earlier quoted context omitted.
What do you like about it? I was actually thinking the opposite... EDIT: Genuinely curious, this is not meant to troll or start a war. I like the more explicit feeling `count-1`. I'd use either...
How is the inclusive range operator implemented in Kotlin? Something like `for (i in 0..count)` needs to iterate count + 1 times, which may overflow the size of count's type - annoying to implement.