A complementary Haiku web application persona
|Reported by:||jonas.kirilla||Owned by:||nobody|
If Haiku was remade to be consumable as a website, both locally and remotely, if redesigned as a kind of middleware for running Haiku web applications (called haikus?) this could:
- free it from the present consensus against theming
- free it from the constraints of its C++ API
- free it from limitations of the app_server (drawing primitives?)
- free it from the conventions of its desktop environment (Tracker, Deskbar, Twitcher, etc)
- mitigate the lack of drivers, if consumed from another computer
- allow accessing one's Haiku environment from one's phone
- eventually free Haiku from dependencies on its own kernel and filesystem
- make multiuser more interesting (to experiment with)
- sidestep C++ API integration for script langauges, offering web-based GUI
- allow apps to mix different programming languages
- allow apps to offer services, data to each other
All in all, this would help break Haiku out of its current pigeon hole. It might not be Haiku anymore, but it would be more interesting, to me at least. BeOS fans learned to love the post-BeBox BeOS. "It's dark in the box." Perhaps Haiku fans can learn to love a post-Haiku Haiku, if its spirit, core values, sensibilities, and ease of use remain.
To be clear, for a transitional period of time (years, most likely), the present Haiku would be the premier host platform for its web personality. Haiku weblets would be shown as regular windows when run locally. Remote web consumers would only see the haiku weblets, and weblet windows would be managed by a pluggable window manager, similar to X in concept, tailored to a web user experience when used remotely.