Repository navigation
Conversation
Windows F: lab validation checkpoint (2026-10-24)Created an isolated test workspace at Verified locally:
Important limits: The QA PC has i5-4590, ~12 GB RAM, mechanical HDD. Tauri startup/RAM improvement remains unmeasured. Visual Studio/Windows SDK may still write system components outside F:. Do not merge or release on this evidence. #44 remains a separate unresolved investigation. |
Native build blocker, correction to earlier checkpoint (2026-10-24)The Visual Studio 2022 Build Tools bootstrapper progressed into Microsoft's setup.exe, but after extended observation there was still no Verified additional result: Native Tauri build, first-window smoke test, RAM measurements, and Electron/Tauri A/B therefore remain NOT DONE. Frontend Vite build is the only successful runtime-facing build evidence. Local handoff is documented at |
Windows native validation & Tauri Lab startup evidence — 2026-10-24Build prerequisites are now resolved. Verified MSVC x64 compiler Actual native build passed: First native smoke: Visible window after 336.7 ms, exit 0, isolated WebView2 QA folder populated. This is timing to window visibility, NOT verified completed first-paint or feature readiness. 10 repeated-profile starts: 10/10 visible-window successes; min 46 ms, median 62.35 ms, max 97.5 ms. Raw CSV: 10 independent fresh WebView2-profile starts: 10/10 successes; min 90.4 ms, median 98.65 ms, max 112.8 ms. Each profile verified to contain an Important: Tauri Lab deliberately disables real ADB/Gnirehtet and other production backend features; the numbers are not a feature-equivalent comparison to Wirebound Electron. Do not merge this draft PR or claim Tauri resolves #44 before the matching Electron QA comparison, ready-to-paint instrumentation, full resource accounting, and feature parity validation. Earlier user-facing streaming connection interruptions did not affect completion of the fresh-profile benchmark process. |
CRITICAL QA correction — 2026-10-24 (supersedes earlier Tauri startup claims)Re-auditing the local benchmark exposed false positives in all previously published Tauri visible-window timings (46–113 ms, 20/20) because PowerShell Win32 Cause: local Retract the earlier Tauri startup and RAM claims. Preserve raw files as methodological evidence; do NOT use them for Electron comparisons. A corrected Tauri CLI build is in progress locally. The 10-run isolated Electron QA baseline meanwhile observed 9/10 visible-window successes, one >35s timeout, one 25.3s latency, median 1167.4 ms among 9 visible; 9/10 renderer isolation checks passed. Electron CSV: Keep PR DRAFT and issue #44 OPEN. Any future timing harness MUST enumerate top-level windows, verify owner PID, |
Corrected and visually verified Windows benchmark (2026-10-24)This checkpoint supersedes the false-positive Tauri 46–113ms results documented earlier. Two QA defects corrected:
Evidence of real UI: Win32 audit confirmed a 1016×729 Corrected Tauri data (10 distinct newly created WebView2 QA profiles, no tracing):
Electron issue #44 QA baseline on same machine, 10 fresh isolated profiles, tracing off:
Interpretation: In this non-feature-equivalent experiment, the functional Tauri UI-only demo had a higher typical visible-window time than warmed Electron QA starts, but no >35s outlier in 10 samples. Working-set figures are not an apples-to-apples physical-RAM measure (shared pages/descendant coverage); and tests were sequential on an HDD PC after heavy build/install activity. This does not prove framework superiority nor explain issue #44. Renderer paint completion is not independently timed. Keep PR #52 DRAFT, no merge or release, no dependency upgrade; a full parity implementation/controlled crossover test would be required before migration. |
QA note: aborted crossover experiment (2026-10-24)The new interleaved E/T attempt is not a benchmark result: 1-Hz performance-counter sampling and preflight process inspection stalled severely on the HDD QA machine before the first valid measured launch. A separate npm installation in another project was active concurrently, adding uncontrolled load. No crossover CSV of valid launch times exists. The first harness was stopped and source files marked as Keep the previous corrected result as the most recent usable data: 10/10 Tauri real |
|
Archived per maintainer's 2026-10-28 PR-backlog cleanup decision. This is a UI-only Tauri 2 research spike, not feature-parity implementation, a valid Electron-vs-Tauri resource benchmark, or a replacement for the production Electron app. Closing this Draft PR without merging keeps |
Purpose
Explore whether a Tauri 2 shell could improve Wirebound's startup/resource footprint on older Windows PCs (i5-4590, ~12 GB RAM, HDD observed on one QA machine), without changing the production Electron app or reclassifying issue #44.
Implemented
Not done / blockers
Scope guardrails
References: #44, #38.