A generalized idea of application hybridization
Over the past few months I have been closely acquainted with the idea and implementation of the so-called Web 2.0. In fact, the same browser, the same technologies and principles, a slightly different implementation and appearance. Why then did this phenomenon get such a proud and promising sequence number? After all, if 3G, then with video, if MACH3, then with a triple blade :)
Then came across a very fresh article about hybrid applications . After a bit of thinking specifically on this topic, an idea came to my mind.
And what if to generalize structure of desktop applications and web platform?
')
The essence of the idea is as follows. Roughly speaking, the browser core (ex .: Gecko) is built into the OS. Separate applications, in turn, are essentially browser windows, but are already running in the OS interface. The contents of the window can be a combination of the system API and what the engine has drawn.
What are the advantages of such a scheme?
- the ability to work with system resources directly
- the ability to combine the best achievements of web and classical programming languages to achieve even better results
- unloading of system resources due to distributed work of the program
- almost the integration of operating systems and the Internet
- more user-friendly than web 2.0 in its current form for an ordinary user
About the rest of the advantages like absolute cross-platform and availability of the necessary data from the network I will not speak - this is a merit of the principle of the notorious web 2.0.
Probably a bit crumpled, but such thoughts are now flying around. I really wanted to share with people who are not alien to anything new.
Then came across a very fresh article about hybrid applications . After a bit of thinking specifically on this topic, an idea came to my mind.
And what if to generalize structure of desktop applications and web platform?
')
The essence of the idea is as follows. Roughly speaking, the browser core (ex .: Gecko) is built into the OS. Separate applications, in turn, are essentially browser windows, but are already running in the OS interface. The contents of the window can be a combination of the system API and what the engine has drawn.
What are the advantages of such a scheme?
- the ability to work with system resources directly
- the ability to combine the best achievements of web and classical programming languages to achieve even better results
- unloading of system resources due to distributed work of the program
- almost the integration of operating systems and the Internet
- more user-friendly than web 2.0 in its current form for an ordinary user
About the rest of the advantages like absolute cross-platform and availability of the necessary data from the network I will not speak - this is a merit of the principle of the notorious web 2.0.
Probably a bit crumpled, but such thoughts are now flying around. I really wanted to share with people who are not alien to anything new.
Source: https://habr.com/ru/post/7662/
All Articles