The last two issues in that article have a point, but the other things mentioned just show a poor understanding of the available language constructs.

Hmm... blasphemy. Excommunicate this individual from the Kult of Kotlin.

What does he even mean with that

for

problem ? Running the code I see similar results

Yeah, that puzzled me, too. After reading it I still have no idea what his problem with

for

in kotlin is, or why he went to implement that weird

For

function.

Don't want to digress, but how many folks actually use Loops often?

Not that often, really, especially with the extensive extensions functions for the collections. But I still wouldn't want to go full haskell and do all iteration via recursion 😉

Lack of array and map literals is something that bothers me too. And of course, every time I read anything more than the simplest code using generics, I am left bewildered and confused. But the rest - I don’t understand the problems.

I think that’s good that in everything, there’s contradiction i didn’t read the article in full but in all cases, contradiction brings improvements

some languages has much powerful

for

that’s what he means

I think that the for statement could be improved, and that he found some interesting edge cases with generics (by ignoring a compiler warning…). Otherwise much of the article looks to me like what I worry about when writing certain technical things: that someone who knows more than the writer will see the author as hopelessly ignorant. The lack of collection literals don’t bother me though, unlike some of the other people in this thread.

@rwachol From what I gathered he compared it to the normal for-loop in Java, though... Any example on one of those more powerful

for

in other languages?

I know about Scala for sure. Rust’s for works also on interator, and probably haskell 🙂

Python can use

for

loops that

yield

, but why would you want to do that when you have Sequences, Streams, Rx Observables, etc...

yield

isn't tied to

for

though, and we'll be able to do

yield

as well with coroutines 🙂

@thomasnield flat mapping monads!

I think he is asking for C/C++ syntax. Has been pounded enough on HN