Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LINUX -- Ignore unavailable to you. Want to Upgrade?

To: JC Jaros who wrote (1431)	4/13/1999 10:23:00 PM
From: Mitch Blevins	Read Replies (2) \| Respond to of 2615

(lay question) Why is it that we just can't throw X away and have a graphical browser that has an efficient dedicated (run time) GUI built in? If we're going to a browser desktop, what's the point of having all of that overhead? What am I missing? I think a decent browser/GUI that ran directly on the framebuffer and had a built-in Java Virtual Machine would be a real hit. But this would be very similar to the JavaOS that has completely flopped from a marketshare standpoint, so I could be all wet.

To: JC Jaros who wrote (1431)	4/14/1999 12:06:00 AM
From: E. Charters	Read Replies (1) \| Respond to of 2615

E.- <g> Are you saying that your GUI isn't going to be in the kernel, but on a separate layer? # jawohl. It will operate in the X address space but in a different mode. Programs no longer control their own window code. Also, are you advancing that XML will obviate 'productivity suites'? It kinda makes sense. Will an XML browser be able to *do that? # gotta write it. See Amaya. XML will do deep deep formatting and style sheets and database/spreadsheet and all graphics and user customizable formatting. If so, why is Corel jumping head long into XML? # avoid the rush, be obsolescent now. (lay question) Why is it that we just can't throw X away and have a graphical browser that has an efficient dedicated (run time) GUI built in? # I give up, why not? This GUI will be client server oriented with X pass-through of X commands but new code implemented for USER definable windows and much lower bandwidth and code. Also extensible code fragments. If we're going to a browser desktop, what's the point of having all of that overhead? # what overhead? What am I missing? # a good desktop with easy code and no conflicts and customizable look and feel.