Yes, those banners are useless for people who don't know what cookies are and how they work and they're a nuisance for people who do, so it would be so much better to invest in eduction than into enforcing this policy which has net-zero effect.

If you're using opera browser you can use "I don't care about cookies" extension https://addons.opera.com/pl/extensions/details/i-dont-care-about-cookies/?display=en Pretty sure there's similar one for chrome or other browsers

there is also http://prebake.eu/ for adblock plus

https://kotlinlang.slack.com/archives/random/p1449834831000669

Yes! The only good part of that law is that of course you need the cookie to track that the user already clicked on "let's close that annoying message". So like in Inception, those dozens of millions of websites that have to respect that arbitrary law should also add a paragraph to explain that they use cookies to implement the law. which is funny like every absurdity

I've got tired of waiting for slack-redir.net to forward links in slack chats, so I ported slack-direct extension available for Chrome to GreaseMonkey. https://github.com/AlexCzar/grease-slack-direct

I wounder haw harmful it is that we resolve our kotlin-related problem here, on slack, and not on StackOverflow Of course it is faster, but that way the answers are not searchable, and the questions are asked over again

Also the SO-question-count is down, but that is only important for marketing

Maybe there could be a Stack Bot that would publish question-answer to SO from here?

Not only speed, but on Slack you don’t have to worry about karma levels, etc. etc. that makes SO such a PITA.

Well, some of them are probably bad publicity/marketing (like the scary issue that happened with apks build on beta-1038 on android 4.1 and earlier)-- Highly relevant to people using that version, but not great as part of the long term memory of the language.

why would anyone worry about SO 'karma'? From my experience, not being a douche and using SO like it is supposed to be used takes care of everything by itself. I agree with Daniil, I've already seen many repeat questions here and also, Kotlin slack community although large does not encompass all Kotlin developers and will never be able to. I'm for 1. Ask on SO 2. Post link here style of asking questions. If the question gets answered here, the author of the question can copy it to SO himself with due credit remark of course.

@Czar: good idea! Actually I saw many people doing this

all newly created IT laws show that

In case anyone interested I imported most of the Kotlin code from here http://rosettacode.org/wiki/Category:Kotlin into github project https://github.com/dkandalov/rosettacode-kotlin

@pkazm has left the channel

If somebody doesn't know about that, guess it's an interesting read https://www.ibm.com/developerworks/library/j-nativememory-linux/ 🙂

@Dmitry Kandalov - that looks great, still a lot of unimplemented solutions for Kotlin if anyone has got any free time over Xmas. http://rosettacode.org/wiki/Reports:Tasks_not_implemented_in_Kotlin

@andyb I have an hello triangle (https://github.com/elect86/kt/blob/master/src/hello.kt) that I may modify for the opengl sample

@kage has left the channel

so, i just ran into the dozenth or-so instance of my collegues copy-pasting code in our codebase.

tomorrow my plan is to go to work, disassemble their keyboards and remove the the

C

key

(for those who are interested

alt

0090

and

alt

0067

are the windows combinations for

c

and

C

respectively)

thoughts?

Software solution, opposite to your hardware approach: code analysis tool that punishes for copy-paste and fails CI build.

On a Mac, I would just bind “Cmd+V” globally to

say "Copy pasting again? Refactor instead”

@groostav you should try http://gitprime.com

I remember a PM who was copying same text through specs. Each time I was trying to read carefully and understand is there any difference or this text or it is just copy-pasted. The company where we both were working does not exist for now. 😐

@orangy: I've tried to make the distinction with these guys that cut paste isn't an issue, so I'm ok with a couple uses of paste -- mind you intelliJ's refactor commands subsume 95% of the cut-paste use cases.

Do any of you guys have a favourite blog post about the horrors of code clones?

@curioustechizen has left the channel