Processing
Processing is shipping again — and quietly moved its renderer onto wgpu.
A side-by-side editorial comparison of itslearning and Blockly — release velocity, themes, recent moves, and the top alternatives to consider.
Ten months of accessibility debt and legacy retirement, with SCORM now a line item
itslearning ships one dated digest a month, and the contents are consistent: interface conversions (frameless layouts, refreshed icons, font selection, a rebuilt permission system, a rebuilt personal Files area), a long fix table, and features funded by the German Development Project with four German states. Across ten months of updates nothing adds a new capability category — the work is making the existing platform accessible, faster and less iframe-bound. The one structural move is subtraction: legacy subsystems are being retired on published deadlines.
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.
itslearning ships one dated digest a month, and the contents are consistent: interface conversions (frameless layouts, refreshed icons, font selection, a rebuilt permission system, a rebuilt personal Files area), a long fix table, and features funded by the German Development Project with four German states. Across ten months of updates nothing adds a new capability category — the work is making the existing platform accessible, faster and less iframe-bound. The one structural move is subtraction: legacy subsystems are being retired on published deadlines.
The retirement schedule is the actual roadmap. Test 2.0 loses editing from summer 2026, the Icodeon SCORM player is stripped from inactive sites and swapped for Rustici on active ones in August, and small legacy surfaces like the project Links page are deleted as cleanup. Net-new features trace back to the GDP partnership rather than a general product thesis, which means the roadmap follows a funded customer bloc; expect frameless conversions and accessibility passes to keep filling most of each monthly digest.
The next digest should confirm the Rustici cutover landed for active sites, with further frameless conversions and GDP-funded features behind it. What the entries do not answer is what schools that decline the paid SCORM add-on at renewal are expected to use instead.
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 itslearning or Blockly.
Processing is shipping again — and quietly moved its renderer onto wgpu.
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.
See all itslearning alternatives → · See all Blockly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — accessibility — within EdTech. itslearning and Blockly are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. itslearning and Blockly are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top itslearning alternatives in EdTech are ranked by recent ship velocity. Browse the "itslearning alternatives" section above for the current picks, or visit /alternatives/itslearning 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.