@denis.st: https://youtrack.jetbrains.com/issue/KT-11295

eh, whats wrong with try.kotlinlang.org? I'm seeing the "Loading. Please wait." pop-up for like 5 minutes now :O

@Andreas Sinz: all works for me

@Andreas Sinz, @voddan: both try.kotlinlang.org and try.kotl.in are looks unreachable for me

I cannot access try.kotl.in as well. Chrome suggests showing only saved copy

Would be awesome if we could say if(someObject) {} like in JavaScript

I tried try.kotl.in and I see Welcome to nginx! not Welcome to Kotlin

@gregman: try some nginx then 🙃

It's never late to try!

probably updating software

@kevin_leigh: Kotlin has

someObject?.doStuff()

Seems like try.kotlinlang.org is working now.

try.kotl.in not yet, though

@arkadiy: its fine for me, maybe browser's cache

< HTTP/1.1 301 Moved Permanently
< Server: nginx
< Date: Fri, 04 Mar 2016 10:35:36 GMT
< Content-Type: text/html
< Content-Length: 178
< Connection: keep-alive
< Location: <http://try.kotlinlang.org/>

yeah, cache was it

@kirillmakarov: reason is that I would like to check that someObject is null only once, and its a JavaScript syntax style that I would prefer to see in the language then the standard

!= null

syntax seen in many c based languages

@kirillrakhman:

that's fine and dandy when you're working as a lone developer, but most of us work with other people who aren't going to want to invest their time in that. The gains just are not worth it to most people

Scala presents a new set of barriers. You can choose to cross them, or you can say, "I'm not willing to cross that barrier; I'd rather preserve the notions I currently have." And that is okay. It's choosing to enrich what you have over taking on something new.

As always, it's a team / environment based decision.

As a group, you have to be willing to forge into that territory together. And you may find along the way that doing so as a team helps you learn even better, especially if you're focused on helping one another learn.

That happens regardless of the language. Kotlin is a simple choice for most Java devs, because it's a natural progression from one to the next, requiring little in the way of alteration of thought. It's a continuation of the OOP principles you're familiar with.

The foundation of, say, Scala or Clojure is very different. That doesn't mean their benefits don't exist, but rather that you have to cross that barrier to start seeing what that new foundation gives you.

It's choosing a different set of baseline assumptions that has a multitude of downstream effects.

The more languages and paradigms you learn, the faster those barriers dissolve, and the better you'll see the bigger picture across all languages.

it's usually not as simple as you're making it out to be, though. If you have a team of developers, most of whom are not familiar with Scala, and you force it upon them all, most of them are going to sit there struggling, writing non-idiomatic code, and it's frustrating for everyone involved. The code becomes unmaintainable. Realistically, most teams don't have the time to spend on this, and there are very few tangible advantages to such a drastic migration

You don't force it on your team. Your team is responsible to select its own tools together.

Kotlin is OOP, but it has a lot of functional influences as well. It's more comfortable to work in. People can continue to be productive

It's as functional as Java is - which is to say it's at most continuation-passing. 😉

#funktionale notwithstanding