Google Classroom
Gemini in Classroom drops its age gate and starts reading the assignment you are on.
A side-by-side editorial comparison of Processing and Blockly — release velocity, themes, recent moves, and the top alternatives to consider.
Processing is shipping again — and quietly moved its renderer onto wgpu.
Processing spent much of 2025 with a stalled release train; 4.5.4 in June explicitly marked the restart, and three releases have landed since. The work splits in two: build and release plumbing (the Ant-to-Gradle migration now sitting on Gradle 9.x, a release workflow that survives a failed macOS notarization) and an editor-shell refresh built on Jetpack Compose and Material 3. Contributor volume is the other signal — most release notes are lists of first-time PRs rather than maintainer work.
Blockly makes keyboard and screenreader access the default, not a plugin
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
Processing spent much of 2025 with a stalled release train; 4.5.4 in June explicitly marked the restart, and three releases have landed since. The work splits in two: build and release plumbing (the Ant-to-Gradle migration now sitting on Gradle 9.x, a release workflow that survives a failed macOS notarization) and an editor-shell refresh built on Jetpack Compose and Material 3. Contributor volume is the other signal — most release notes are lists of first-time PRs rather than maintainer work.
The plumbing work is close to finished, which frees attention for the graphics stack. `the-wgpu-moment`, a branch open for nearly a year, is now merged into main, pointing Processing away from Java plus OpenGL through JOGL. Expect the next stretch to be about making that path usable and testable rather than about the editor UI.
The likely next move is exposing the wgpu renderer behind an opt-in flag with an open call for testers, while the 4.5.x line continues as the stable Gradle and Compose track.
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
Accessibility has moved from an add-on to an architectural property of the editor, and the follow-on releases show what that costs: focus management, insertion markers, and field labeling all had to be reworked around it. The insertion marker rewrite is a good marker of the pattern, framed as a performance change but motivated by memory leaks in the focus-aware rendering path. Translation of field labels extends the same reasoning from assistive technology to language.
Expect continued hardening of the focus and navigation paths rather than new editor capability, since that is where every release since 13.0.0 has concentrated. The RTL and memory-leak fixes suggest the accessible rendering path is still settling.
Other EdTech products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Processing or Blockly.
Gemini in Classroom drops its age gate and starts reading the assignment you are on.
LifterLMS wired its REST surface into WordPress's new Abilities API.
Nearpod's feed is teacher marketing; one digest post carries all the product news.
Scribe's Optimize agent is turning a doc-capture tool into an org-grounded AI assistant.
Whatfix's feed has quietly moved from training users to governing workflows.
Tutor LMS spent four months getting 4.0 out the door; the interesting bet was buried in a beta.
See all Processing alternatives → · See all Blockly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Blockly is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Blockly is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top Processing alternatives in EdTech are ranked by recent ship velocity. Browse the "Processing alternatives" section above for the current picks, or visit /alternatives/processing for the full list with editorial commentary on each.
Top Blockly alternatives in EdTech are ranked by recent ship velocity. Browse the "Blockly alternatives" section above for the current picks, or visit /alternatives/blockly for the full list with editorial commentary on each.