Great, thanks. I was having a play with rolling back with Safari 26.2 and had a hard time getting the history entries to be "correct" from a user perspective. It looks like precommitHandler solves this, so 🤞for Safari support soon
Do these things become a bit more stable once they are baseline?
(and also, how might I determine support for precommitHandler? will `if (NavigationPrecommitController) work?`
So excited by this. Related, but kind of general question: how stable is the API? I've been going through the GitHub issues for how I might implement a "rollback" after an intercept, and it looks like there have been a few of solutions: commit: 'after-transition', event.commit(), & precommitHandler.
And footpath is typically used for a pedestrian path away from a road, eg in a park or countryside
As a Brit, I think sidewalk makes more sense. However, I’ve always considered the road surface to be tarmac, and the pavement/sidewalk surface, paving slabs.
I’d love my game boy modded … if I could find it 😫
But what I _have_ found is my game gear. Have you fixed game gear (screens)?
And the men arose and went away; and Joshua charged those who went to describe the land, saying, “Go, and walk through the land and describe it, and come again to me, that I may here publish a GeoJSON file for you before the Lord in Shiloh.”
I suppose it follows the Methodist (methodical) philosophy and its origins from Wesley’s travels around the country!
Or even jQuery.load() with a fragment: api.jquery.com/load/#loadin...
Yes! Also reminds me of Turbo Streams: turbo.hotwired.dev/reference/st...
In addition, many modern websites and web-based applications deploy a technique called “server-side rendering” whereby programs running on a web server generate HTML markup with the initial content for web browsers to consume, instead of fetching content over the network once scripts are loaded.
I think of this WebKit blog post often: webkit.org/blog/13851/d...
/ht ruby.social/@javan@masto...
We invented computers to do boring repetitive tasks so humans could focus on creative work. Now we're inventing AI to do creative work so humans can (crawl back into the swamp and die)
So the minority’s a problem? Or is it the leader, writing inflammatory articles in support of a violent white nationalist?
And how is the online discourse?
They contribute to the tone and direction of the community. That’s not to say that everyone in the community agrees with them, but it impacts the types of people that participate in or are drawn to that community.
That’s quite a leap you’ve made there! (And not what I said)
No, where did I say that?
Or “pound shop musk” for the “native Brits”
I am
bin/dev in particular
I do think it affects Rails though. Community leaders set the tone and direction. They have influence beyond just the codebase, so I don’t think it’s as easy as “don’t read it”.
Have you checked your bins?
Yeh, I think that'd be tricky. Doable but types will always be a distraction
Ruby is great for this. I've been doing a lot of Swift recently, and I enjoy it, but I can't imagine sketching with it
Thirty-two years ago today, Myst was released.
Happy Birthday, little guy!
🎂
Perhaps because every domain is different, it’s hard to see the similarities and to generalise them? However, I think for me, thinking in terms of CRUD actions has helped frame what I’m actually modelling.
Re. Domain modelling: I agree that this is something which isn’t discussed enough. So many tutorials just talk about the technical side of models and their associations, but not how to _think_ about what the models should be.
Really interesting chat. I love the idea of temporary/disposable code. (In some ways this is why I like tailwind—it feels much more editable than composing styles in a css file.)
That's an innovative solution! I'd have probably be looked to see if the widget had a JS API that could be called? But this is neat! Anyway, there have been some suggestions for iframes (and other elements?) to be persisted across documents, which might help in the future: github.com/whatwg/html/...
This is great. Even with a small codebase, my fixtures were getting a bit unwieldy. Now things are much easier to manage with Oaken's seed-based approach.
