Oh my goodness... I've had a full text search endpoint (powered by ripgrep of course) available in the API for ever and only a slug based search in the UI...
No longer
Hit highlighting, floating widget to scroll hits
The search page filters on viewed / updated / created dates, plus passing through all the useful bits to shape the response.
ripgrep is đ when ADHD is life ;)
[I wonder if it can find my keys]
Ghirija Jayarraj's 'Wanderland' Weaves Dance, Displacement, and Multi-media Narratives
Ghirija Jayarraj's 'Wanderland' performance uses dance, theatre, and film to explore identity, displacement, and family history across Sri Lanka, India, and Australia.
#Wanderland, #GhirijaJayarraj, #DanceTheatre, #DiasporaStories, #MulticulturalArts
https://newsletter.tf/ghirija-jayarraj-wanderland-dance-film-identity/
Ghirija Jayarraj's 'Wanderland' performance combines dance, film, and theatre. It explores themes of displacement and identity across Sri Lanka, India, and Australia.
#Wanderland, #GhirijaJayarraj, #DanceTheatre, #DiasporaStories, #MulticulturalArts
https://newsletter.tf/ghirija-jayarraj-wanderland-dance-film-identity/
SmolChalk :: if SmallTalk and Erlang had a baby and it was web components for kids and it composed itself out of markdown and YAML
Just a bunch of little things that mostly don't suck all doing their best to give your children a place to learn whatever you can think of, and letting them explore and learn from the environment they're learning in while they do so.
#humantools #computingforlittles #smoldata #smolchalk #wanderland
Anyone following along probably has questions about just how the heck we're using a single YAML fence in a Markdown file as shared storage for multiple users?
Well we're not.
The <oculus-fence> Web Component assigns as session id the first time one is called. The rest of them share the same id while until the session expires. The `write_path` method intercepts calls containing X-Wanderland-Client-Id and cuts them their own slice of the universe - an overlay driver tracking an append-only list of updates made by that session.
Replay on read. Multi-player ready. Collision proof updating.
Game on Wayne. Game on Goose
It's Monday night, your daughter is at dance and you're stuck in town at the library waiting for her...
[As you do]
You're bored
[As you do]
What do you do?
Goose Pong Mobile
[As you do]
PEEK / POKE / EXECUTE
state = peek('goose-pong:game-state.yaml')
poke('goose-pong:game-state.yaml', state)
execute('goose-pong:board', action='poke_cell', params={'row': ball_row, 'col': ball_col, 'value': 'đȘ©'})
[As you were]
"""
Hello World!
"""
--- wanderland, as to you, inviting you to try executable markdown
"""
Shut-up and take my money!
"""
--- you, after seeing goose-pong played in a Markdown file in a browser
===
Wanderland is built on executable Markdown - think Jupyter, but you know... not those bits...
Markdown has ```code-fences, they're normally used for presentation. But semantics are semantics and MDAST is perfectly happy to pop them out of the tree so we'll take advantage of that to turn them into lovely little addressable distributed functions.
And then we'll wrap them in Web Components to bring them to life (or Emacs, or Neovim, or you know... whatever can talk to a simple HTTP API)
<oculus-fence> exposes a function
<oculus-node> exposes some text (in this case a Markdown table standing in as our beer pong table)
new-game resets the game
take-turn ... takes a turn ;)
Here we go
#emacs #orgmode #jupyter #smoldata #wanderland #devops #devops_you_say_as_a_question_but_of_course_i_say_as_an_answer_distributed_functions_build_platforms
"""
How does that make money for business?
"""
--- my mom, a harsh critic
+++
Executable Markdown means executable markdown - fences are functions, the file is the I/O surface
"""
Ooh...
"""
--- he, after having a go at this
===
Wanderland runs on executable Markdown. Code fences become distributed functions. Patterns in the structure of the text become API surfaces (to-do lists, tables, changelogs...).
Lantern is the rendering engine in front of the graph built on custom Web Components with a two phase rendering pipeline: server side they expand with static content and a hydration marker for non-js enabled friends, client side detects the marker and explodes them into lovely rich, interactive control surfaces
Like this one, for running those embedded fences.
Take a Markdown document, write some code in it. Now you have a tool.
Write some prose around it. Now you have a documented tool.
Write a YAML block in it. Now you have a data store.
Run it and push it to git. Now you have an audit trail
Neat
graeme fawcett
NewsletterTF