Also IMH developer perspective HTML+JS+CSS is surprisingly a not so bad UI toolkit, and React makes the development experience even better.
I will always bet on standards and, at least for now, modern web is the standard that I can trust.
We can do better.
I just don't get this at all. The fact that chromium books and in the past netbooks do so well is for this reason. I can't understand why you wouldn't want browser applications at this point. Outside of write once run anywhere, security and accessibility is another benefit of the browser. We still have a huge issue with the walled garden in the app space. I'm assuming you mean primarily in the mobile space ? I think this is largely due to a failure on Apple and Google's lack of wanting to innovate because they control the app stores.
Is this possible? If so, is there any guidance on how to achieve this?
Thanks
On the frontend side, when you install a module, it loads the .js file (using a regular <script> tag) which contains a single function. The Odoo core passes its main JS object (the base of the core API) to that function, which then initializes the whole module and uses the Odoo API to configure stuff, setup hooks, etc.
There's no security, though: by design, a module is trusted and can do anything on the platform. I'm not sure if and how one could contain them.
(Disclaimer: I'm a developer working for an Odoo partner, we write modules and host it as a SaaS.)
When you say "language" here, are you referring to the web languages (HTML, JS)?
These concepts may hurt or cripple early developers since html/css is obvious and easy while the concept that globals, scope and the database is in an entirely seperate location seems odd. What makes it worse is that xmlhttp requests arent very kind.
The concept of the single page app and "serverless" architecture seems to be a fools errand to build (or influence big names to build) complex html applications without the need to spend money or wrappers to bridge the gap. Meteor, northwest.js and electron are celebrated for attempting to accomplish these goals.
It depends. A desktop application may have a backend, like a central web service to connect to. Even if it doesn't, there is still likely to be a logical separation of layers which may or may not be in different languages (think c++ backend with a c#/xaml front end).
As the potential capabilities in front-end web development increase, the differences between web development and "desktop" software development are reduced, because web developers find themselves facing more and more of the same questions software developers have always faced when dealing with distributed software architectures at scale.
because that's where people's attention is.
where people's attention is, is where apps are going to be built, with whatever is there to build them.
if you think javascript is bad, get ready for SnapchatScript (that's not an actual project, but it all too easily could be, and something like it will be an actual project, some day)
I'm currently working in the peer to peer application/protocol space and the biggest thing that stands out to me is the impact these technologies could have in developing countries. The challenge is making things light enough to run well on the weak hardware most people have to work with. Browser apps don't make the cut.