midgetjones

What a lovely article! I happened to walk past his house in Cork last year, not having known he'd lived there. My partner couldn't work out why I was so excited, but then there's only 10 types of people in this world etc

I'm not sure which is best for you, or how established you are as an artist. But if the website is early days then changing the url/product name would be least harmful. Or just submit your own tunes under a pseudonym if it's royalty-free. I think my concern as an artist is that you might make it big and take back the domain name.

Hi Wlad! This is great, and I'd consider contributing, but I'm not sure that making the domain name the same as your artist name encourages that.

I think I started using it for much the same reason; I was having trouble with the official node installer. But once I uninstalled rvm as well, I was sold. Now I can have a project with a specific elixir/erlang/node version written into my `.tool-versions` file, and I don't have to worry about anything.

I'm sorry, I could have sworn the README used to have a snappy description.

Think of it like a Swiss Army knife of version managers that can handle all the languages you use, per-project. And it's all just bash scripts, and installs everything into a visible place on your drive.

Great work, but you'd have to pry asdf out of my cold, dead hands.

https://github.com/asdf-vm/asdf

I actually wrote 'game changer' in my original comment, and got rid of it for the same reason! Now that I've added it to my vimrc, I'm now upping it to 'life-changing'

I can't believe I didn't know about this! Thanks so much :)

> Contrary to false reports, his cat hasn't even been at embassy since well before the inunction was filed

But not all of the numbers are multiples of 9

Picked a "gif" at random:

  Format                                   : MPEG-4
  Format profile                           : Base Media / Version 2
  Codec ID                                 : mp42
  File size                                : 1.61 MiB
  Duration                                 : 4s 890ms
  Overall bit rate                         : 2 766 Kbps
  Encoded date                             : UTC 2018-06-07 09:34:57
  Tagged date                              : UTC 2018-06-07 09:34:57

  Video
  ID                                       : 1
  Format                                   : AVC
  Format/Info                              : Advanced Video Codec
  Format profile                           : Baseline@L3.0
  Format settings, CABAC                   : No
  Format settings, ReFrames                : 1 frame
  Codec ID                                 : avc1
  Codec ID/Info                            : Advanced Video Coding
  Duration                                 : 4s 890ms
  Bit rate                                 : 2 764 Kbps
  Width                                    : 720 pixels
  Height                                   : 414 pixels
  Display aspect ratio                     : 1.739
  Frame rate mode                          : Variable
  Frame rate                               : 33.538 fps
  Original frame rate                      : 1 000.000 fps
  Minimum frame rate                       : 33.333 fps
  Maximum frame rate                       : 1 000.000 fps
  Color space                              : YUV
  Chroma subsampling                       : 4:2:0
  Bit depth                                : 8 bits
  Scan type                                : Progressive
  Bits/(Pixel*Frame)                       : 0.276
  Stream size                              : 1.61 MiB (100%)
  Title                                    : Twitter v1.0-757770b7c8e9d79a526cdff77e74666386274fdf
  Writing library                          : x264 core 148
  Encoding settings                        : cabac=0 / ref=1 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=2 / psy=0 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=1 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc=crf / mbtree=0 / crf=20.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=2:1.00
  Encoded date                             : UTC 2018-06-07 09:34:57
  Tagged date                              : UTC 2018-06-07 09:34:57

The funniest and most depressing part of all this is that twitter 'gifs' are mp4s

Maciej's writing was always fantastic, but this story in particular was so well-written that I'm very excited for the next one.

Also, if you're reading this Maciej, there's a typo: indedidble.

Why would they do that when we'll happily pay them to keep pumping out poison and selling us water filters?

Wasn't there a recent story in the news where a major producer of legal opioids, started also producing the methadone to wean addicts off them? Wish I could find a reference

I follow a few teletext artists on twitter. This guy particularly springs to mind: https://twitter.com/Horsenburger

I'd be interested to see how Elixir does with an OTP-optimised redo. Probably still not great, but I feel like the example isn't playing to its strengths.

The key for me is making the query _slightly_ more descriptive. It's a good thing that it's not tracking me, so it's fair enough that I should type a bit more so that it knows I mean Ruby the language and not the gemstone.

It's risk/reward to the people who want to decide how their money is spent, isn't it?

In your example, the worst-case scenario is that someone could die, and that tends to spur on investors to discover the probity within themselves to spend some money avoiding an expensive lawsuit.

But when the devs are complaining about the old code being terrible and making their lives hard, it never seems to hinder them that much to management. They keep banging out new features and fixing bugs, and nothing bad seems to happen. But the drip-drip-drip of bugs keeps increasing, and the new features take a little longer each time, and nobody dies at least, but the thing becomes a haunted moneypit that nobody wants to touch, and you're stuck with it now unless you rewrite it all at huge expense, etc., etc.

Maybe everyone should just treat a piece of software as they would a life. I bet we've all seen some codebases where if it were a friend, you probably would have staged an intervention by now. Your software baby needs absolute care from the get-go until the very end, or it will get sick and probably die, and most likely in a very prolonged and painful way.

Great examples (after I realised they weren't all going to be McDonald's ads)

(I'm not looking, but) I would work for you in a flash if that's how you do things. I'm the only Org user in my team, and I wish they'd see the light!

The literal translation (from German delikat essen) is 'delicious food'

Have you tried just putting one leg out? Never fails for me.

And do those professionals need access to YouTube tutorials to see how to use the plunger?

Well, I'm glad I use Firefox now

These problems can also be avoided by not owning guns.

It doesn't surprise me that much; I personally found it _way_ harder than Vim to get to grips with. Although I would have thought Spacemacs adoption might have pushed it up a little bit, as that was my entry point as a Vimmer.

I think it's more likely to be amazon/google than apple

Yep, good old `<meta name="Generator" content="Microsoft Word 9">`

Same in the UK, it's always "going up to London". Maybe it's a subconscious status thing?