This checkin to GCBMAGF #07 Northmoor Loop reflects a geocaching.com log entry. See more of Dan's cache logs.
Wasn’t I just here? Yup! This is the only one of the series I’d already found, missing the FTF by only about half an hour the other week. It’s still here and looking good!
This checkin to GCBMAG7 #06 Northmoor Loop reflects a geocaching.com log entry. See more of Dan's cache logs.
Very easy find while the geopup dawdled behind me, clearly having found something more-interesting for her to smell. TFTC!
This checkin to GCBMAAR #05 Northmoor Loop - Little Bridges # 3324 reflects a geocaching.com log entry. See more of Dan's cache logs.
Another excellent container, though it was a bit of a stretch to reach it! A herd of playful cattle ran around far behind us as we searched, watching from a distance. TFTC.
This checkin to GCBMAAD #04 Northmoor Loop - Little Bridges # 3326 reflects a geocaching.com log entry. See more of Dan's cache logs.
Briefly overshot this one in our excitement to get out of the field with the sheep (and so allow the geohound off her lead) and rushed to the little bridge. Doubled back to quickly find this great-sized cache. TFTC!
This is a repost promoting content originally published elsewhere. See more things Dan's reposted.
…
I still think web components are a great foundation for a design system. No other approach gives you true cross-framework portability built on what the web platform already provides. The problem isn’t necessarily the model itself, it’s how we’ve been building them.
This is how I ended up creating Elena, a library that I’m open sourcing today. Elena starts from HTML and CSS, and stays grounded in web standards and what the web platform natively provides.
…
I love the “HTML Web Components”/”Progressive Web Components”1 development pattern. The idea is, if you’re new to it:
The downside is that there’s often more scaffolding than you’d like: implementing event and property change listeners (and tidying them on disconnection), batching updates to avoid flicker, and all that jazz.
Now obviously you could go with one of the big heavyweight frameworks like React, but then you’re leaning into a whole locked-in architecture that makes it harder to write progressive components and burdens your users with a ton of unnecessary code. Boo!
That’s why I love it when clever people make useful, HTML-friendly, ultra-lightweight frameworks2 like ReefJS, which I’ve talked about using before, and – now – Elena!
Elena’s a modern, simple, MIT-licensed wrapper framework for your web components, and – having perused the documentation on-and-off for the last couple of days – it’s really exciting. Perhaps not because of what it does, but because of what it doesn’t do. It’s unopinionated, well-documented, SSR-friendly3 microframework that seems to bring the absolute best in what the Web offers via web components… and makes it easier for developers without making end-users pay the price for it.
Anyway: all of which is to say: check out Elena! I’m really excited to have a play with it the next time I have a suitable web components project.
1 I’m with Jeremy: “Progressive Web Components” is a better name. Also: it’s it funny how changing just one word of a name can make you re-think what a thing is. The moment I refactored the way I thought about HTML Web Components into calling them Progressive Web Components was the moment I said to myself “hey, I could put an SVG into one of those… use state-managed props to set CSS variables that are available to the image… and in doing so, produce an SVG that elegantly becomes animated where JS is available…”
2 I same “frameworks”: by the time they’re this lightweight, single-purpose, and focussed on adding functionality that perhaps vanilla JS and web components should already have we might as well call them utility libraries or polyfills!
3 SSR perhaps ought not to matter for Progressive Web Components, but I can imagine situations where Elena would still be useful even for web components without a HTML fallback, at which point I suppose SSR could be a performance shortcut for some projects.
This checkin to GCBMA9M #03 Northmoor Loop reflects a geocaching.com log entry. See more of Dan's cache logs.
QEF when the GPSr dropped me right on it.
The dog complained that I wouldn’t let her go play with the lambs while I retrieved the cache – the playful pup can’t understand why I wouldn’t let her try to make friends with them!
This checkin to GCBMA8X #02 Northmoor Loop - Little Bridges # 3323 reflects a geocaching.com log entry. See more of Dan's cache logs.
Two for two. The dog watched from below as I reached for this one. Amazing container; love it!
FP awarded for the container alone! TFTC.
This checkin to GCBMA4C #01 Northmoor Loop reflects a geocaching.com log entry. See more of Dan's cache logs.
In the second hiding place I tied, and the evidence suggests I’m not the first to make my mistake. I dipped into this series on release day from the other “side”; now I’ve returned (with my geopup pal) to do more of the loop! TFTC.
