Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
nodejs
Home
+ new post
About this group
Join this group
Message from discussion jOS - The next step?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rasmus Wikman  
View profile  
 More options Aug 14 2011, 6:00 pm
From: Rasmus Wikman <rasmus.wik...@gmail.com>
Date: Mon, 15 Aug 2011 01:00:23 +0300
Local: Sun, Aug 14 2011 6:00 pm
Subject: Re: [nodejs] Re: jOS - The next step?
Print | View thread | Show original | Report this message | Find messages by this author

On 15 aug 2011, at 00.33, Dean Landolt wrote:

> On 14 aug 2011, at 01.58, Sotonin wrote:

> I think the idea is a fantastic one. But not with jQuery. jQueryUI  
> is one of the weakest UI libraries i've come across. Maybe something  
> involving Ext would be a better choice.

> The licensing terms of Ext are a little too restrictive to allow for  
> non-destructive development and adoption.

> I'm not saying that jQuery might be the best technological solution,  
> but it has a large adoption rate which is key to success.

> Just as Node I think the other winners of the JS race will be those  
> that are truly community efforts and not the ones that limit certain  
> types of use.

> Dojo. The engineering quality of Ext with a liberal license and  
> clean IP.

Wow, had missed that one. Development is truly speed of light at the  
moment!

> FWIW I'm with Scott -- calling whatever you're trying to do an OS  
> would probably be a mistake. I'm guessing you're going to need an OS  
> to run node on! You don't plan on rewriting all the userland tools,  
> right? You're probably talking about a desktop environment, right?

Well I'm mostly theorising at the moment and asking questions to avoid  
unnecessary work.

If JavaScript turns out to be the long term solution that becomes a de  
facto standard, I think we'll see faster development of the language  
specification aswell.

What's to say everything currently written in C can't/won't be  
rewritten/reparsed in JS?

And I'm not the only one poking around asking questions:
http://code.google.com/chrome/nativeclient/

Every OS has to be written in some other language before it can be  
rewritten in itself. Chicken and egg. :)

> In any event, good luck -- it seems to me like a great time for it.

And to you too, exciting times we're living in! :)

Rasmus


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google