kotlinlang #random

The Android app won't always refresh the names to be full name right away, seems to cache. So if someone changes one it could appear for some time without ...

onizuka89

09/30/2015, 12:38 PM

On the desktop app it seems like you can only have one or the either, not both.

grahamcox82

09/30/2015, 12:42 PM

Ah - so I assume the settings can't be changed on the android app but they carry across to it. Makes some kind of sense I guess

evanchooly

09/30/2015, 12:58 PM

a little terrifying… http://www.infoworld.com/article/2987529/java/insider-oracle-lost-interest-in-java.html#tk.twt_ifw

s.luhmirins

01/13/2017, 11:04 PM

I will allow myself to quote my colleagues opinion on `.btw()`: "next up

public inline fun <T> T.kkthxbai()

and `cache.iirc()`"

dwellman

01/13/2017, 11:20 PM

This quote from that Uncle Bob reply had me thinking:

dwellman

01/13/2017, 11:21 PM

Every step down that path increases the difficulty of using and maintaining the language. Every step down that path forces users of the language to get their type models “right” up front; because changing them later is too expensive. Every step down that path forces us back into the regime of Big Design Up Front.

dwellman

01/13/2017, 11:22 PM

Have folks felt that pain of causing changes to types be prohibitively expensive? More so than Java?

dwellman

01/13/2017, 11:22 PM

I'm still new to the language so I haven't written enough to notice anything.

dwellman

01/13/2017, 11:23 PM

I can imagine that going from a nullable to not nullable type might be a source of changes.

dwellman

01/13/2017, 11:24 PM

I wondered what specifically he thought caused this. Was it the nullable types or was it the idea of going farther down that dark path?

jdiaz

01/13/2017, 11:26 PM

@dwellman and what is the difference between nullable/non nullable change in kotlin and java? One forces you to do it correctly the other will just throw NPE all the way down

Ruckus

01/13/2017, 11:55 PM

@dwellman The slack off the language he attacking is probably not the best place to get an unbiased opinion 🙂

Ruckus

01/13/2017, 11:55 PM

But if you want a biased opinion, I'd say his last two articles are absolute bonkers.

dwellman

01/13/2017, 11:57 PM

@Ruckus: ha! Fair point. 😀

Ruckus

01/14/2017, 12:01 AM

Also, his claim that no language exists that a change on one line requires changing all other lines is false: https://en.wikipedia.org/wiki/Malbolge

😂 2

fellshard

01/14/2017, 12:51 AM

He does have a point, insofar as changing the nullability of a type requires a lot of widespread changes. But in some sense, I expect most Kotlin code to use nullable types A. at integration points with unmanaged Java code, or B. when a nullable type is a reasonable way to represent an optional value in the problem domain.

fellshard

01/14/2017, 12:52 AM

So it could be he's seeing it as this widespread use when in reality it should be contained, narrow, and not propagated everywhere.

fellshard

01/14/2017, 12:53 AM

Very little should be written to accept nullables, etc., unless - again - it makes sense as a proper representation. No different than Java, just more explicit where it needs to be

okkero

01/14/2017, 9:03 AM

Does the IntelliJ merge tool support three way merge?

irus

01/14/2017, 5:16 PM

Few extensions and sample of using Akka with Kotlin https://github.com/KotlinBy/kotlin-akka

👍 1

rocketraman

01/14/2017, 6:15 PM

@okkero Yes

okkero

01/14/2017, 6:15 PM

How can I enable this? I have looked

rocketraman

01/14/2017, 6:16 PM

If you have a merge conflict for example, and use IJ to resolve it, IJ will bring up a 3-way diff

rocketraman

01/14/2017, 6:17 PM

Not sure you can start it explicitly

gjesse

01/14/2017, 6:54 PM

I think it's under version control-> git -> resolve conflicts

okkero

01/14/2017, 7:30 PM

That always starts a two-way merge for me. It does not include a view of the base