Swift is like Kotlin

Post by marcus_holmes » Thu, May 18, 2017, 11:52 AM UTC

Jach wrote: post #181

3chelon wrote: post #152

Earlier quoted context omitted.

Point taken, but the original point was being associated with the name, not throwing a fit. Having it on your CV/resume, for example. Potentially alienating clients because of words that stand out from the page in the wrong context. I can see a problem.

The point I responded to was maybe we should be above politics in names, to at least be capable of treating names with a professional indifference. To that end there's a simple test to see if someone you're considering working with believes that too. (Of course it's fully reversible, maybe the future will require passionate condemnation of names that might give offense in order to get hired.) For your point of unsavo…

Post by pmontra » Thu, May 18, 2017, 11:57 AM UTC

masklinn wrote: post #192

pmontra wrote: post #170

Some considerations on the syntax (Swift first, Kotlin last in each pair) bad: \(apples + oranges) # using \ is looking for troubles good: ${apples + oranges} good: label + String(width) # even Ruby requires a .to_s here bad: label + width # surprises will follow good: ["Anna", "Alex", "Brian", "Jack"] super bad: arrayOf("Anna", "Alex", "Brian", "Jack") # make the long form optional good: for index in 1...5 { bad: fo…

> # using \ is looking for troubles Are you referring to escaping and other special sequences (e.g. unicode codes)? Though it is odd-looking I actually find it rather smart that they decided to reuse an existing mechanism for that: aside from delimiters the only magical character in a string is \ rather than have e.g. both \ and $. > # the useless () My beef is more with 1..5 being inclusive and there apparently bein…

Post by lauritzsh » Thu, May 18, 2017, 11:59 AM UTC

menage wrote: post #85

desdiv wrote: post #36

Earlier quoted context omitted.

I prefer explicit words over symbols, like in Scala: scala> 1 to 3 scala.collection.immutable.Range.Inclusive = Range(1, 2, 3) scala> 1 until 3 scala.collection.immutable.Range = Range(1, 2)

As someone who's never programmed in Scala, it's not intuitive to me at all that "until" means exclusive, given that "to" (which is basically a synonym) means inclusive.

  > 1 through 3
  # [1, 2, 3]

  > 1 until 3 # or 1 to 3
  # [1, 2]

Post by billyjobob » Thu, May 18, 2017, 12:07 PM UTC

masklinn wrote: post #195

martijn_himself wrote: post #160

Does anyone else think the Kotlin syntax for array literals is super ugly: val shoppingList = arrayOf("catfish", "water", "tulips", "blue paint") What is wrong with square bracket syntax? (rant over). EDIT: I suppose it's consistent with other syntax e.g. listOf() etc.

> Does anyone else think the Kotlin syntax for array literals is super ugly: Well yeah, except it's really that Kotlin does not have array literals at all, arrayOf is just a variable-arity function.

Post by esrauch » Thu, May 18, 2017, 12:13 PM UTC

filomeno wrote: post #187

Cthulhu_ wrote: post #144

Earlier quoted context omitted.

Would you work in a programming language called Hitler? Any multinational company needs to do their research before deciding on a name.

What does the name of an individual have to do with that of an island? Wayland: I think it's the name of some America place. Should afghans, syrians, viets, [put whatever country the US invaded] stick to X11 because of this?