Linked by Eugenia Loli on Tue 30th Sep 2003 05:20 UTC
General Development In the dawn of the renovation of's web site, David Zeuthen announced the release of HAL 0.1. HAL is an implementation of a hardware abstraction layer, as defined by Havoc Pennington's paper. It encompasses a shared library for use in applications, a daemon, a hotplug tool, command line tools and a set of stock device info files. Carlos Perelló Marín also announced the design of a similar concept, but it is expected the two projects to merge. More people are encouraged to join this innovative project. Elsewhere, Gnome's Seth Nickell is giving us a first taste of his effort to replace the Init system.
Permalink for comment
To read all comments associated with this story, please click here.
by oGALAXYo on Tue 30th Sep 2003 12:05 UTC

> However, the people live in the real world,
> not in some sort of academic dreamland. They actually get
> something done, and that's obviously a Good Thing.

Is it ? The sentence 'someone who provides the code leads the development' can be a serious WRONG sentence. If we let everyone proceed that way and excuse all things happening with such sentences then we end in the biggest mess ever. We sould first sit down, talk and weight the real life benefits with theoretical hackish solutions. I doubt that these people at do everything right. They are humans like we all and they trap themself into shit quite often enough.

A real life solution shouldn't be LAME HACKS, if we add more LAME HACKS around and inside GNOME or any other Desktop solution then we gain nothing. There is no need to add another layer ontop of an already existing layer and I bet even you can understand these simple explainations that I provided with my earlier replies. Where will it all end, when we simply sit down and assume that the people at do everything right ? Who judges that the stuff they decide IS right if not from people outside with real life (e.g. 20 years and more) of experience in these areas ? If we sit down looking the shit they sometimes put in a Desktop then where will we end in a few years ? We add one technology after another into GNOME or KDE without any real life benefits. We hack stuff ontop of other existing solutions only to get the stuff done that we like because we can't do it differently because the OS where this Desktop belongs to permits these capabilities from Desktop level. We are sitting here somehow paralyzed and let them proceed with all the bloat in the Desktop which we can't do anything. They excuse the needs of it today and we let the proceed, tommorow they come up with yet another idea which we criticise as well and we do let them proceed again.

What do you user want ? A working Desktop that works smoothly fast, loads up quickly, where the apps look consistent and where you see a good cost/value for what you get or do you want a technological experiemnt where ALL technolgical ideas went into, where with every increasing itterative number of Desktop release more and more techological ideas went in ? Where the dependency of: Application <-> Library dependency AND Library <-> Library dependency increases more and more ?

Systems like MorphOS, QNX, BeOS (to name some) show us in best bells and whistles how you can do a nice Desktop System the right way. As soneone else already stated, we will hit the limitation really soon, GCC is nearly complete for intel architectures, Linux the Kernel will grow permanently, other apps around the GNU System increase as well GNOME will increase and we need at least 1,6 Ghz to have a normal responsive operation and soon we require 2,6 Ghz only to achieve the same speed feel that we have today. While still other systems as named above requires less resources and less CPU speed but still respond faster than GNOME for example. Double click on an Icon in MorphOS for example on a G3/600MHZ and it bombs up before you ended the double click. Do the same on GNOME and you wait some seconds.

Maybe worth to think about ? What'ya say ? But getting deeper into this requires a lot more understanding.