Can't transfer a file from my phone to Mac using bluetooth

TL;DR: Check that 'Bluetooth Sharing' is enabled under 'System Preferences' -> 'Sharing'.

I took a picture and wanted to deal with it using a Mac. I thought: 'It is just too easy. I'll use bluetooth to transfer it'. Not so fast.

I couldn't see the Mac from the phone and I didn't see any hint about it not being visible from 'Bluetooth Preferences'. 'Interesting glitch', I thought, deciding to try rendering the phone visible and pairing it from the Mac.

That being successful, I then selected the picture, chose 'Share', 'Bluetooth', the Mac, and... 'Transfer failed'.

'Joy', I thought, 'another Apple-not-playing-ball issue'. So I decided to try to browse the files in the phone from the Mac, to which the Mac replied, 'The device does not have the necessary services'.

Solution came from: Google 'galaxy s5 cannot pair with mac', then https://discussions.apple.com/thread/6098837?tstart=0

Total time spent: about 30 minutes.

Thank you again, Apple. <sarcasm />

Javascript 'wat' moments

The new 'let' (ES2015) brings some interesting questions.

Since it makes the variable limited to the scope where it was declared, as opposed to the 'var' which puts the variable in the function scope, what happens when we refer to it from within a lambda function reference?

Check out this JsFiddle for an illustration of the question.

What do you think you're going to see?

The first function block doesn't surprise me. The variable is not evaluated until the lambda function is executed.

For the second function block, I, for one, was expecting some 'Undefined reference' errors on line 18.

Then I executed it. wat? I concluded that the Javascript gods decided to add one more black magic and detect that the variable would not exist when the lambda function would execute.

A friend tried to convince me that I was wrong and that actually a copy was being made for the 'let', so we wrote the third function block. WAT? I certainly wasn't expecting that.

wat?