docs(blog): PocketJS on the BlackBerry Classic - #304
Closed
HalfSweet wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on
feat/blackberry-classic— the BlackBerry Classic host code. Base is the feature branch, so this reviews as just the blog diff on top of the hosts; retarget tomainafter the host branch lands.Adds the engineering blog post for the BlackBerry Classic port — the same PocketJS guest run through two native stacks (QNX-native BAR on a rooted device + Android Runtime API-18 APK on a stock one), diverging only below the QuickJS bridge.
Covers:
Contents:
site/content/blog/blackberry-classic.md— new post (author HalfSweet, 2026-08-19), 5 inline SVG diagrams, 9 code snippetssite/nav.ts— registered inBLOG_POSTSsite/assets/blog/blackberry-classic-hero-720.png— hero photo (Hero demo on real hardware)Draft — verified the post renders through the site's marked + shiki pipeline (SVGs pass through,
tsx/c/textblocks highlight, tables render). The commit is unsigned (--no-gpg-sign, no TTY in the automation shell).