Post by bfraley on Oct 20, 2013 19:32:46 GMT -5
Hey, it's been a while since I previously replied, but I am getting back to looking at the Run Basic system for different uses.
I have been reluctant to spend time thoroughly learning and creating with Run Basic as a web solution because of insecurities I have about it. Although, I do not know enough and haven't tried enough to truly justify my lack of confidence in Run Basic.
So, here are some things that I'm concerned with(maybe deserves it's own topic), and below are more Web OS questions and comments.
Network security is a vast and ever-changing reality, especially for public facing servers running multiple web-server software and complex configurations. I know that the server aspect of RB is "hidden" / transparent for good reason, but how secure and reliable is it ?
My other concern is with web standards and modern html5 APIs, how browsers parse html/xml of a RB based application, as well as how search engine's view and read site's generated from RB code.
My last concern is about the generally small RB community, activity of users, and upcoming changes / updates to newer versions. I have lots of questions that I can't seem locate information for, as well.
Anyway, with that said, the simplicity of RB as a development and server environment for web applications and web-based solutions is very attractive. What it lacks, I think deserves some form of additional code library and tools for addressing many other Web APIs and standards. Then it could be more readily used for building and deploying various projects, and perhaps web-services.
I think that the concept of a Web OS in RB is the exact atmosphere required to grow into solutions for the things I addressed above. I'm not sure as to how this would be best designed, or implemented but it seems that a management system running in any browser or on it's own browser could serve as a back end to the "OS". It's as if a layer of some sort must be running beneath RB, which then would run RB web- programs and services, that would then finally produce end result web products and services.
I know that is all rather theoretical, but I am trying to understand the real potential power of such a system.
Lastly, such a system could actually serve as an embedded server based OS on dedicated machines that hosts other RB instances. This would provide extended service, value, and support for hosting applications, sites, and especially web-services integrated with other APIs, languages, databases, etc.
This is what I imagine when I think RB Web OS.
I guess I should start becoming more familiar with RB and produce some code instead of "talking" about it.
Mike, would you be interested in emailing me any of your thoughts and work ? You seem to be the most active and innovative person developing with Liberty / Run Basic. I commend you for that!
Thanks,
Brett
(brettfraley@hotmail.com)
I have been reluctant to spend time thoroughly learning and creating with Run Basic as a web solution because of insecurities I have about it. Although, I do not know enough and haven't tried enough to truly justify my lack of confidence in Run Basic.
So, here are some things that I'm concerned with(maybe deserves it's own topic), and below are more Web OS questions and comments.
Network security is a vast and ever-changing reality, especially for public facing servers running multiple web-server software and complex configurations. I know that the server aspect of RB is "hidden" / transparent for good reason, but how secure and reliable is it ?
My other concern is with web standards and modern html5 APIs, how browsers parse html/xml of a RB based application, as well as how search engine's view and read site's generated from RB code.
My last concern is about the generally small RB community, activity of users, and upcoming changes / updates to newer versions. I have lots of questions that I can't seem locate information for, as well.
Anyway, with that said, the simplicity of RB as a development and server environment for web applications and web-based solutions is very attractive. What it lacks, I think deserves some form of additional code library and tools for addressing many other Web APIs and standards. Then it could be more readily used for building and deploying various projects, and perhaps web-services.
I think that the concept of a Web OS in RB is the exact atmosphere required to grow into solutions for the things I addressed above. I'm not sure as to how this would be best designed, or implemented but it seems that a management system running in any browser or on it's own browser could serve as a back end to the "OS". It's as if a layer of some sort must be running beneath RB, which then would run RB web- programs and services, that would then finally produce end result web products and services.
I know that is all rather theoretical, but I am trying to understand the real potential power of such a system.
Lastly, such a system could actually serve as an embedded server based OS on dedicated machines that hosts other RB instances. This would provide extended service, value, and support for hosting applications, sites, and especially web-services integrated with other APIs, languages, databases, etc.
This is what I imagine when I think RB Web OS.
I guess I should start becoming more familiar with RB and produce some code instead of "talking" about it.
Mike, would you be interested in emailing me any of your thoughts and work ? You seem to be the most active and innovative person developing with Liberty / Run Basic. I commend you for that!
Thanks,
Brett
(brettfraley@hotmail.com)