|
As a software developer, I know what makes a good 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.
or
14 year old Web, Software, OS dev, author, music composer and CEO of OneNode ORG.
modified 25-Dec-12 19:45pm.
|
|
|
|
|
I don't see how that solves anything.
|
|
|
|
|
It's easy to design with Web Technologies so it will make software development easier. But.. it will not enable us to make background services or softwares like Rocket Dock or Rainmeter. A high school student can make his own application as many schools are teaching Simple web development (and of course how to use Visual Studio).
|
|
|
|
|
Ok, well good luck. Personally, I'm not convinced, though. Having to jump through all the html/css/js hoops just to make a desktop app (that's what this does, right?) seems counter productive to me.
|
|
|
|
|
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.
|
|
|
|
|
harold aptroot wrote: Having to jump through all the html/css/js hoops just to make a desktop Metro app (that's what this does, right?) seems counter productive to me.
FTFY
|
|
|
|
|
erikroyall wrote: It's easy to design with Web Technologies so it will make software development easier.
No it isn't.
Software development over time rises to meet the demand. The demand drives the innovation. the innovation doesn't drive the demand.
erikroyall wrote: A high school student can make his own application
I created my own applications before the Web and before the internet. The complexity has risen, significantly, since then. Complexity both in frameworks/apis/languages that exist to solve problems and complexity of applications that exist to meet need.
|
|
|
|
|
And if JavaScript is interpreted through an efficient one like Chrome's V8 engine, apps will run fastest than we can imagine.
|
|
|
|
|
erikroyall wrote: JavaScript
erikroyall wrote: efficient
erikroyall wrote: interpreted
erikroyall wrote: fastest
All those things in one sentence about slowpoky 'apps' which spend endless time shoveling megabytes over the web or waiting for a database.
|
|
|
|
|
one time i read in a blog that the V8 engine runs javascript faster than the desktop runs C, that made me take to conclusions:
1 - the test PC for C was a 386 and the one for javascript was a I7. (even then i think C is faster...)
2 - I must choose better the articles i read.
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
One trick they really like to pull is write crappy C code and run it through a crappy compiler, and then they say "oh hey, C is not so fast".
They would doubtless also find assembly to be slow.
|
|
|
|
|
men, theyr C code must be really, really, REALLY crappy to run slower than javascript
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
No.
"People who bite the hand that feeds them usually lick the boot that kicks them." Eric Hoffer
"The failure mode of 'clever' is 'a**hole'" John Scalzi
"Only buzzards feed on their friends" Patrick Dorinson
|
|
|
|
|
And how is this a web bases OS?
|
|
|
|
|
erikroyall wrote: As a software developer, I know what makes a good software.
While we might agree on "best practices", I doubt we'd all agree on what could be called "good software".
erikroyall wrote: 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.
..imagine writing a webcam-driver using HTML, CSS and JavaScript
erikroyall wrote: But now, I have a doubt. Is it necessary?
It's already available. You can download any Linux-distribution and boot the browser on startup.
|
|
|
|
|
You mean like Google Chrome OS?
I guess this is what you are talking about?
If I understand you, your reasons for doing this is so that developers can write applications more easily, because they're writing web applications in HTML/JavaScript rather than, say, c# or c++?
Thing is, there's nothing to stop you doing that now, the only difference is that the app will be hosted in a browser rather than directly in the OS (except in windows 8 if I understand Metro apps correctly)
S in answer to your question "is it necessary" I'd say that it's been done, and sales of google chrome OS would indicate its not exactly the Next Big Thing but certainly a viable concept.
|
|
|
|
|
When the only tool you have is a hammer, it does not automatically make all problems require a nail to solve.
Contrary to what some people think, not all applications are suitable for running on the web. Anything requiring a guarenteed response time, or typical response times under a second or so, can not run 'from the web'. Web apps can't manage local hardware effectively. Web applications are notoriously poor in terms of UI latency; users are accustomed to poor reaction times because the medium forces them to become so. Any application requiring significant data volumes (megabytes or even gigabytes per second) can't be delegated to a web server.
Secondly, there are significant computer systems with no Internet access. No web, no application.
While there may be a value is imposing structure on the chaos that is web development, calling that structure an 'operating system' seems overblown and unnecessary.
Software Zen: delete this;
|
|
|
|
|
You can already run web applications in a browser. Unless you mean giving external sources direct OS/hardware access, in which case you're talking about what is probably the worst-case security scenario imaginable. And, as mentioned above, you can already write apps that run locally in HTML/CSS/JavaScript in Windows 8 (or, in am ore limited fashion, any version of Windows running IE 5 or higher, take a look at HTML Applications[^])
So what do you gain by doing that?
|
|
|
|
|
Should note that although you are really unlike to solve anything, attempting to do so will teach you a great deal.
|
|
|
|
|
|
All Web apps suck. 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.
|
|
|
|