The Web was initially conceived as a platform for content rather than applications. Qworum is proof that the Web still isn't a full-featured application platform, and that, despite JavaScript. Qworum aims to change that.
Note that Qworum is not a Web framework but an upgrade to the Web platform itself.
💡 What's missing from the Web platform?
There are several big gaps between what applications need and what the current (non-Qworum) Web provides:
- Hyperlinks alone are not suitable for linking between applications, but they are great for linking between content. When application A1 calls application A2, how will A1 continue its execution once the call to A2 has returned? For this reason, in the Qworum world linking between applications is done through scripts rather than plain hyperlinks.
- Applications are fundamentally stateful, and content is fundamentally stateless. And that's why using the tab history is problematic for applications, but not for content. When was the last time you navigated to a website, signed in, and then went back one page, only to be asked to sign in once again? Last time this happened to me was on Eventbrite. In the Qworum world, the tab history is disabled so that the UI cannot go out of sync with the application's internal state.
- Object-oriented programming adopted to the Web platform is a winner. By structuring web applications and APIs as OOP classes, Qworum is able to support distributed applications, UI-level integrations, modular application frontends, and composable and distributed user dialogs.
⚙️ How is Qworum implemented?
Qworum provides a new browser runtime that is implemented as a browser extension. The Qworum runtime is attached to browser tabs instead of individual web pages as the JavaScript runtime is.
🧑💻 Show me the code
Here is a video presentation I've posted today. If you are short on time the first 6 minutes are conveying the gist of it.
🚀 Time for action
Qworum subscriptions are available to businesses worldwide at very affordable prices.
∎
Top comments (0)