cretz

Kotlin Annoyances

These are things that I found annoying writing a complex library in Kotlin. While I am also a Scala developer, these should not necessarily be juxtaposed w/ Scala (even if I reference Scala) as some of my annoyances are with features that Scala doesn't even have. This is also not trying to be opinionated on whether Kotlin is good/bad (for the record, I think it's good). I have numbered them for easy reference. I can give examples for anything I am talking about below upon request. I'm sure there are good reasons for all of them.

1. Arrays in data classes break equals/hashCode and ask you to overload it. If you are going to need to overload it and arrays have no overridability, why not make the least-often use case (the identity-comparison equals) the exception?

dlew

<!-- You can change the parent around to whatever you normally use -->
<style name="DebugColors" parent="Theme.AppCompat">

    <!-- System colors -->
    <item name="android:windowBackground">@color/__debugWindowBackground</item>

    <item name="android:colorPressedHighlight">#FF4400</item>
    <item name="android:colorLongPressedHighlight">#FF0044</item>
    <item name="android:colorFocusedHighlight">#44FF00</item>
    <item name="android:colorActivatedHighlight">#00FF44</item>

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

natevogt

amazing
incredible
powerful
great
great
best
really great
great
fantastic
beautiful

0xabad1dea

Abadidea's Index of Weird Machines in Video Games

A "weird machine" is when user-supplied input is able to create an arbitrary new program running within an existing program due to Turing-completeness being exposed. Sometimes such functionality was deliberately included but it is often the result of exploitation of memory corruption. You can learn more at the langsec site. There is a good argument for weird machines being inherently dangerous, but this index is just for fun.

It is broken into two categories: intentional gameplay features which may be used as weird machines, and exploit-based machines which can be triggered by ordinary player input (tool-assisted for speed and precision is acceptable). Games with the sole purpose of programming (such as Core Wars) are not eligible and plugin APIs don't count. If you know of more, feel free to add a comment to this gist.

Intentional Gameplay Mechanics

kaw2k

// Import settings
var settings = require('./settings');

// Setup IRC
var irc = require('irc');
var bot = new irc.Client(settings.server, settings.botName, settings);

console.log(
  settings.botName + ' connecting to ' + settings.server + settings.channels
);

harthur

var http = require("http"),
    url = require("url"),
    fs = require("fs"),
    async = require("async"),
    Instagram = require('instagram-node-lib');

Instagram.set('client_id', /* client key */);
Instagram.set('client_secret', /* client secret */);

fetchTag('cat', 400);

katylava

Update 2022: git checkout -p <other-branch> is basically a shortcut for all this.

FYI This was written in 2010, though I guess people still find it useful at least as of 2021. I haven't had to do it ever again, so if it goes out of date I probably won't know.

Example: You have a branch refactor that is quite different from master. You can't merge all of the commits, or even every hunk in any single commit or master will break, but you have made a lot of improvements there that you would like to bring over to master.

Note: This will not preserve the original change authors. Only use if necessary, or if you don't mind losing that information, or if you are only merging your own work.