mirror of
https://github.com/alexandrev/xslt-lab.git
synced 2026-09-13 08:43:16 +00:00
40b81728d6
From the August competitive analysis, the items that close real gaps: - Saxon HE 12.5 -> 12.9 (the closest competitor already ships 12.9). The trace/hotspot instrumentation is reflection-based, so it was verified against the new jar: variables and execution counts come back intact. - Tracing now works for XSLT 2.0. The trace infrastructure needs Saxon 10+ APIs and cannot load inside the Saxon 9 daemon, so traced 2.0 requests run on Saxon 12 in backwards-compatible mode instead of silently returning an empty trace — a real trace with a small, labeled semantic difference. Untraced 2.0 runs still use Saxon 9. XSLT 1.0 now says outright that XSLTC has no tracing hook rather than pretending. - Saved fiddles: POST /fiddle stores the workspace under a 7-char id with an append-only revision history; ?f=ID loads it (optionally &r=N). Available whenever DATABASE_URL is configured — unlike /history this is unauthenticated, because a fiddle is a thing you share with someone who has no account. An unreachable database degrades to "fiddles off" instead of crashlooping: the chart has shipped a placeholder databaseUrl for a long time, and opening it eagerly would have taken production down. - The home page now tells the truth about engines: 1.0 on XSLTC, 2.0 on Saxon 9, 3.0 on Saxon 12.9 — three real processors was already the architecture, it just was never marketed. - Four posts aimed at where the demand data points: the FreeFormatter shutdown audience, Chrome's XSLT removal (v158, Nov 2026), Peppol/EN-16931 Schematron validation and ISO 20022 camt transformations. Every example was executed against the real backend and the published output matches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KZntQUfw463NW4ftgSjWw5