Also, for the macOS users, there's a great emoji picker interface: cmd+ctrl+space brings up a very similar-sounding menu where you can search by typing, or scroll through and click the one you want.
That's actually the one I was thinking of as being awkward to activate :) I love the picker itself but the activation method is pretty clunky in my opinion.
I wish I could just hit one key instead of having to simultaneously press three. I've been using Rocket for awhile now (https://matthewpalmer.net/rocket/) which kind of takes the Slack style ":emoji_name" format to the whole computer, but it's still kind of awkward to activate and has a lot of false positive triggers. (It really makes you realize how often you type colons in everyday computer usage.)
I'm mildly comfortable with clojure, but haven't used it in a number of years. The code linked here looked pretty typical to me; could you possibly elaborate on the differences between this and some more modern clojure, or maybe a reputable link to a blog post outlining the ways the language has changed?
Here's an example of why it's useful for me to see articles like this on HN. I'm an engineering manager, and someone on my team recently joined who wasn't very familiar with these more functional styles. I offered to explain to him benefits of declarative styles like this vs imperative, but he said he learned better by reading. He asked if I had any articles that I'd recommend about the topic, and since I've seen this, I'll send it his way.
And, when you compile it to JavaScript, you can choose the target language level. So, you could write Typescript and have it compile such that in essence, all it does is strip out the type annotations.
Same. I evangelize TypeScript whenever I can. I don't think I'll ever be as efficient in JavaScript as I am in TypeScript, now that I've tried it. Granted, it has its quirks, but (especially when writing React) it's invaluable to me.
How does typescript compare to flow? I'd love to see a comparison with pros n cons. I haven't tried either yet and I'm curious if you have any recommendations re resources to read.
+1 for typestyle. My team and I have been using it for the past few weeks in trying to clean up a rather monolithic css project, and it's been really cool to work with.
My experience with kotlin so far has been great. I've used it in personal projects, and am in the process of converting some microservices at work to it from java (the interop is seamless, so I'm able to do it incrementally as opposed to a full rewrite). People ask me what the difference is between kotlin and java, and I typically reply with "it's java, minus all the bad stuff". Variable types are inferred, map/reduce/filter are builtins and don't require going through a Stream, there's no need for Guava anymore since listOf() and mapOf() are builtin, boilerplate-reducers like data classes continue to speak to the whole "it's pretty much java, but how you _want_ to write it" mantra. It nails all of the little things that java has just missed, like in an if-block after checking a variables instanceof, you don't need to explicitly cast it to that type. There are tons of simple things like this that just come for free, and when you go back to java it's amazing how much extra, pointless boilerplate you need to write. I personally don't see any reason for me to ever write java again.
The alternative refers to an alternative type checking system - Flowtype. Not that the seconds has the async/await and modules. Both repositories are trying to deliver quite similar tools - type checking, es6 + async/awat + import syntax and linter.
