This feature entails the Orion browser shipping a new release candidate (RC) every four weeks (similar to the release cycle of Chromium & Firefox) that integrates the latest stable version of the WebKit browser engine. By adopting a frequent update cadence for WebKit, similar to how Safari Technology Preview delivers the latest updates, Orion users will benefit from cutting-edge improvements in rendering, performance, security, and web standards compliance without sacrificing stability.
This approach aligns Orion with modern practices demonstrated by browsers like Brave, Zen, and Ungoogled Chromium, which consistently (not so much UGC) ship the latest stable versions of their respective engines. The feature will:
- Keep Orion competitive by ensuring it supports the newest web technologies and APIs introduced in WebKit.
- Enhance security by promptly addressing WebKit vulnerabilities through frequent updates.
- Improve performance and stability with incremental engine optimizations.
- Incentivize a modular architecture for Orion’s codebase, streamlining the WebKit upgrade process and reducing technical debt over time.
For existing workflows, this feature is designed to be seamless. Users will experience incremental improvements in browser functionality and security. Orion developers and testers will benefit from a predictable release cycle, enhancing their ability to plan and execute "quality assurance processes" (or just testing) effectively.
What are the exact ways that you see a user using your proposed feature?
End Users:
- End users will indirectly benefit from this feature through improved page rendering, faster load times, and better compliance with modern web standards.
- Users will gain peace of mind knowing that their browser incorporates the latest security patches from WebKit, reducing exposure to known vulnerabilities.
Developers:
- Developers using Orion can rely on it as a WebKit reference browser, similar to Safari Technology Preview, to test the latest stable implementations of web technologies.
Orion Development Team:
- With a modular codebase designed for rapid WebKit integration, the Orion team can reduce the overhead of managing engine upgrades, dedicating more resources to enhancing browser-specific features.
- A four-week update cycle provides clarity and structure for testing and release management.
Examples and Comparisons:
- Brave Browser: Brave ships frequent updates to its Chromium-based engine to ensure it stays in sync with Google Chrome. This strategy allows Brave to maintain stability while offering users the latest features and security enhancements.
- Zen Browser: Zen has adopted similar practices to keep its Chromium engine current, ensuring its users benefit from the latest browsing capabilities and performance optimizations.
- Safari Technology Preview: While Safari TP focuses on experimental WebKit builds, Orion’s proposed feature would prioritize stable WebKit updates, offering users a production-ready alternative that balances innovation with reliability.
- Any other browser that has a consistent release cycle (of around 4 weeks) that depends on an external engine
Extension to Existing Features:
This feature complements Orion’s existing user-centric philosophy by emphasizing cutting-edge performance and security. A modular codebase that facilitates regular WebKit updates would also enhance the browser’s extensibility and reduce the likelihood of regressions.
