An OS for the web. Is it a good idea?
-
It's easy. Believe me. And there is Codecademy www.codecademy.com, a website that teaches web development an easy style.
WebDevelopment != SoftwareDevelopment
There are countless problems that cannot be solved by mere web development. If your experience revolves only around web based applications, then I see where you are coming from, but I respectfully disagree. What you are suggesting is that every computer needs to be nothing more than a web hosting device which is not practical in any way, shape, or form.I wasn't, now I am, then I won't be anymore.
-
As a software developer, I know what makes a good :thumbsup:software. But when it comes to programming them, gosh! I had a lot of night-outs, especially when making a browser engine. Then came this thought: why couldn't making software be any easier and faster? Then came the idea of making an OS. The main concept was creating and INTERPRETING applications using a database to store information, JavaScript for logics, HTML, CSS and JS for design. I already have a boot loader, Linux kernel. But now, I have a doubt. Is it necessary? Update: Everything is not coded in HTML or JS. It does supports the normal compiled ones. But it is not yet confirmed that which executable type to use. It is not interpreted in a web browser but in a browser engine. You really do not require an internet connection as they work offline. Everything works offline until or unless you want to update the application or download a new one from appStore. :thumbsup: or :thumbsdown:
14 year old Web, Software, OS dev, author, music composer and CEO of OneNode ORG.
:thumbsdown: :thumbsdown: :thumbsdown: All Web apps suck. X| Including this one.
erikroyall wrote:
why couldn't making software be any easier and faster?
For the most part, that tends to make things worse. The best I can say is that, although there tend to be more bugs, they tend to be easier to find and fix. In my opinion, the best balance is in using C.
erikroyall wrote:
INTERPRETING applications using a database to store information
That sounds like a rule-based system. I have had to work within one of those (for batch processing, not interactive), it did what it was supposed to do and worked fairly well, but it was slooooww and ungainly. Additionally, a whole set of tools was required to maintain the apps and there was no way to validate the logic of the apps. And in the end each rule had to be implemented in a regular programming language anyway so there was little to be gained. The goal was to have a small group of senior developers writing the rules and junior (or off-shore) developers assembling them into apps. I left after a year of that. Which brings to mind -- could you write your OS within the OS? You can write a C compiler in C; you can write a whole OS in C. One can write a Universal Turing Machine. Could you write your interpreter in your new interpreted language? I fear not. Not to say that's a show-stopper, but something to consider. But go ahead and do it, it sounds interesting, and as has been said, you'll probably learn quite a bit.