Skip to content

Add mori 0.1.0 announcement post#204

Merged
shikokuchuo merged 8 commits intomainfrom
blog/mori-0-1-0
Apr 23, 2026
Merged

Add mori 0.1.0 announcement post#204
shikokuchuo merged 8 commits intomainfrom
blog/mori-0-1-0

Conversation

@shikokuchuo
Copy link
Copy Markdown
Member

@shikokuchuo shikokuchuo commented Apr 22, 2026

Summary

  • Registers shikokuchuo/mori under content/software/ with frontmatter, a placeholder hex sticker, and a readme copy. Adds the repo to data/github-repos.toml.
  • Adds the mori 0.1.0 announcement blog post at content/blog/mori-0-1-0/. Covers the ALTREP-based share() API, a mirai-based bootstrap benchmark (~160× wall-clock in the rendered run), access/lifetime semantics, and positioning relative to bigmemory, SharedObject, Arrow memory-mapped Parquet, and fork-based parallelism.

mori was just released to CRAN as v0.1.0.

Test plan

  • Post renders correctly on the Netlify preview (hero image, diagram, code chunks, benchmark output)
  • Post appears at the top of /blog/ with the right title, thumbnail, and description
  • /software/mori/ page renders with the hex sticker and readme content
  • The software: mori tag in the post frontmatter resolves to the software page
  • validate-blog-posts.py CI check passes

Adds shikokuchuo/mori to data/github-repos.toml and a software page at
content/software/mori/ with a forest-green placeholder hex sticker and a
readme copy of the package README. Registers mori ahead of the 0.1.0
announcement post so the blog post's software: mori frontmatter tag
resolves.
Announces the first CRAN release of mori, a new R package for sharing R
objects across processes via OS-level shared memory. The post covers the
ALTREP-based share() API, a mirai-based bootstrap benchmark (~160x
wall-clock on this render), access/lifetime semantics, and how mori
positions relative to bigmemory, SharedObject, Arrow memory-mapped
Parquet, and fork-based parallelism.
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 22, 2026

Deploy Preview for posit-open-source canceled.

Name Link
🔨 Latest commit 2f9f4f8
🔍 Latest deploy log https://app.netlify.com/projects/posit-open-source/deploys/69ea097a90360d0008d8fd6c

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 22, 2026

Publishing checklist

  • Get a review — request at least one reviewer on this PR
  • Check your post — once the deploy preview is ready, a comment will appear with direct links to your post
  • Check the blog listing — confirm your post appears with the correct title, image, and description
  • Merge — once everything looks good and you have an approving review, merge to main

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 22, 2026

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 22, 2026

@shikokuchuo shikokuchuo requested a review from hadley April 22, 2026 13:46
@ivelasq
Copy link
Copy Markdown
Collaborator

ivelasq commented Apr 22, 2026

Thanks, @shikokuchuo!

I see mori's software page, but it doesn't show up on the software page itself or in the search. Just wanted to flag that for you.

The initial software registration used stars: 0 / forks: 0 as
placeholders, which caused mori to be filtered out of the /software/
listing and the Pagefind search index (layouts/software/terms.html and
taxonomy.itemindex.json both gate inclusion on a truthy stars value).
Brings the counts into line with the live GitHub repo so mori surfaces
correctly.
@shikokuchuo
Copy link
Copy Markdown
Member Author

I see mori's software page, but it doesn't show up on the software page itself or in the search. Just wanted to flag that for you.

Thanks and fixed. Just had to add the actual GitHub stars to the entry, otherwise it seems zero-star repos aren't included.

Copy link
Copy Markdown
Contributor

@hadley hadley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally feels LLM written to me. I don't think that's necessary bad but you might want to try https://mikecaulfield.substack.com/p/introducing-jamesian-a-claude-skill or similar.

Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd Outdated
Comment thread content/blog/mori-0-1-0/index.qmd
@shikokuchuo
Copy link
Copy Markdown
Member Author

Generally feels LLM written to me. I don't think that's necessary bad but you might want to try https://mikecaulfield.substack.com/p/introducing-jamesian-a-claude-skill or similar.

Would you be able to elaborate? I actually think the skill did a good job and the tone was generally 'conversational' to begin with. I then got Claude to de-claudify itself and removed what I regarded as "tells" that bothered me. Maybe I've become desensitised...

@hadley
Copy link
Copy Markdown
Contributor

hadley commented Apr 22, 2026

Hmmmm, it's hard to pinpoint exactly why I feel that way. A couple of bits that sound particularly claude-y to me are

  • The algorithm hasn't changed; the savings come from not copying data that's already in RAM.
  • The headline number is what you see when data transfer dominates, which it often does in bootstrap, cross-validation, and parameter sweeps.

But in isolation they seem fine.

@shikokuchuo
Copy link
Copy Markdown
Member Author

Ah the semi-colon, fair point! Those do happen to both be late amendments, after any style passes.
Thanks, I guess I do have to be vigilant on the language - I was more concerned if you thought that the structure (story arc) was now a give-away.

@github-actions
Copy link
Copy Markdown

Blog YAML Checks

✅ All 1 posts passed.

@shikokuchuo shikokuchuo merged commit b63996e into main Apr 23, 2026
13 checks passed
@shikokuchuo shikokuchuo deleted the blog/mori-0-1-0 branch April 23, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants