Dan Q
This checkin to GC86MHH Top of the Footpath reflects a geocaching.com log entry. See more of Dan's cache logs.
Turns out the glue I’d used had interacted badly with the material: wasn’t melting because of the heat (although that won’t have helped) but because of a chemical reaction on the plastic! Repaired and replaced, all good to go now!
This checkin to GC86MHH Top of the Footpath reflects a geocaching.com log entry. See more of Dan's cache logs.
Wow, this cache container really HAS been damaged by the hot weather. Removed for repair, back this weekend hopefully!
This article is a repost promoting content originally published elsewhere. See more things Dan's reposted.
This week on Twitter, Maxime Euzière asked why people choose large frameworks over vanilla JS. There are quite a few reasons. Some of them are really valid. Many of them aren’t. Here are the ones I see most often (with commentary). Vanilla JS is harder. No, it’s often not. Modern vanilla JS has taken many…
Like many people who were already developing for the Web when Javascript first reared its (ugly) head, I would later be delighted when libraries like Prototype and later jQuery would arrive and start doing the “heavy lifting” for me. Not having to do DOM parsing or (especially) Ajax the “long way” (which was particularly long given the workarounds that needed to be done for cross-compatibility) was a huge boon and made it possible for me to write applications that I wouldn’t otherwise have been able to.
But in recent years, I’ve really been enjoying “vanilla” JS. As a language, JavaScript has really grown-up lately, and with modern (and evergreen) browsers dominating the landscape, everybody benefits from these new features relatively soon after they become available. Of course, it’s still important to see any JavaScript as a progressive enhancement that not everybody will experience, but it’s still true, now, that the traditional barriers to writing excellent code in the language are rapidly evaporating.
I no longer add jQuery to a project as a matter of course (and in fact I think it’s been over a year since I deliberately added it to a new project), and that’s great.
This article is a repost promoting content originally published elsewhere. See more things Dan's reposted.
Regular readers will know already that I’ve been a huge fan of comic author Tailsteak, ever since Ruth, many years ago, introduced me to his work. I’m particularly enjoying Forward, his latest webcomic: so much so that in an effort to work around its lack of an RSS feed I accidentally stole unpublished work from him earlier this year (oops!).
He announced yesterday his new secondary Twitter account, @TailsteakAD (the “AD” is for “After Dark”) and was delighted from the very top tweet onwards:
Anyway: a short while later I found a 20-page comic he’d made called The Escape Room: read it on Twitter or via Threadreader. It might be exactly the comic you’ve always been looking for, assuming that the comic you’ve always been looking for combines B/D, gay sex, and escape room puzzle mechanics. NSFW, obviously.
Suddenly I feel like the escape rooms I go to aren’t quite as good as I thought.
