clojure-europe 2021-12-01

And our kids will be like “Ugh, how did our parents live without holonet? They had to sit completely isolated in their homes and type text with a keyboard ”

😂 2

reefersleep08:12:28

(->> "good morning"
     seq
     shuffle
     (apply str))
=> "nrgomgd ioon"

Better than your average ioon.

😂 1

dnmriono ogg

morning

Good morning

Once again I am fed up with Vim and trying out VSCode. Then I use the neovim extension inside it because otherwise my fingers just type nonsense 🙂

slipset10:12:51

Morning! So, TypeScriptReport (TSR) of the day. I consider myself a Clojure programmer, and as such, one would expect that I was ok with wrangling parens. Turns out I’m not. When writing TS (in vscode) without paredit, I constantly mess up the various parens, and, man have they made it difficult for themselves. Where we generally just need, if you’ve messed up, to sprinkle a couple of ) to balance stuff out, in TS you need to interleave the )s with }s. It’s very frustrating I can tell you.

🙈 3

pez10:12:39

I feel ya. What I tend to do is use move-to-matching-bracket a lot (ctrl+alt+cmd+7 on my machine), and also to first create the structure and then move code in there. So the latter… Say I’m providing a function as a parameter, I then type

(foo) => {
  |
})

So that I don’t have to later figure out how to close it. The auto-formatter is pretty smart so if you move some code into there (using alt+up/down for instance, it will reindent it as long as the structure is healthy.

ray14:12:44

gong moorind

🌊 3

agigao19:12:47

Moooaarning

2021-12-01

Channels