Women in Technology

Hear us Roar

  Rethinking the Linux Distribution
Subject:   requirements first (2)
Date:   2007-05-14 12:39:33
From:   Kuros
Response to: requirements first (2)

i agree that a kernel is needed, perhaps in modern day terms we would call it a micro-kernel... yes i think this is a deeper issue. I remember when I used to work on telecom applications (telephony) there was a specification called AIN0.2 (AIN=Advanced Intelligent Networking) which started with an abstract model of the digital telephone network, identifying all the major hardware components in the network (and communication protocols), then designing a set of primitives upon which one could in principle design and implement a wide range of telephony applications. Furthermore, a lot of of what you say reminds me of another specification, called X-Windows. At the time of its definition was pretty advanced and had the main elements of a networked application "system". It too modeled the entire network containing the application. I think such a model and a subsequent specification are a best starting point. Why do you feel that the browser is a good place for a kernel, i.e. why do we need a browser at all (I am not a browser specialist). As I mentioned in an earlier reply, sofar I am not too convinced that HTML (and HTTP) are the best way to go. Perhaps you are thinking of the browser, as not just a place for rendering HTML? Some language like Extended Javascript is naturally needed. I was thinking some kind of a homogeneous programming language that tied the client and server together would be best (Javascript has too much baggage attached perhaps). The final form of the language should at the very least, make networks transparent (or trivially easy to navigate) and make it easier to write interface using same syntax everywhere. I come from a J2EE background, and I have to laugh at the notion that I am doing object-oriented design/programming, because once I start working with Javascript, HTML or XML (which is quite a lot) or development tools, like ant etc. I realize that there is nothing OO about them, so the claim of OO with J2EE is not legitimate. One needs a language (perhaps OO) that would allow programming at all levels of a "WEB" application...
Main Topics Oldest First

Showing messages 1 through 1 of 1.

  • requirements first (2)
    2007-05-14 15:17:42  georgebelotsky [View]

    There is no intrinsic reason for the browser to be so central, but there is a definite historical reason. In the end it is simply how things turned out.

    At this point, Mozilla has invested a lot of effort into Firefox. Version 3.0 of the browser will have DOM storage and offline execution. This is a highly advanced FOSS project, with a lot of momentum. To match their significant technological achievement and market penetration would be a formidable task indeed.

    The above reasons is why I suggest adding X Window manager features to Firefox, making it the central mashup point for both SaaS and local applications.
    There is definitely a valid argument against putting too much in the browser, but what is the alternative? Maintain two separate desktop environments: the browser for SaaS, and a traditional X setup for local applications?

    Note that currently, the X-based desktop is the unifying construct, and the browser just another application that runs on top of it. Firefox, however is not just an application -- it is on the verge of becoming a platform. So, I am proposing to better integrate these two key systems, by making Firefox act like an X window manager.

    Of course, as you earlier pointed out, we do need to worry about many things, especially state management and the network protocol. HTML/HTTP is not the ideal solution. It should be possible, however, to solve these problems at higher protocol layers. This approach may not have the best architecture, but it avoids the monumental task of recreating Firefox's functionality elsewhere.

    Given your Java background, JavaScript will certainly seem strange to you. It does have an object model, and perhaps even its own peculiar elegance. Still, JavaScript OO development is very different from Java OO development.

    Since you prefer working in Java, maybe Google Web Kit (which automatically generates JavaScript from your Java code) is the right tool for you?