Ah, please don't misunderstand. I think the proposed change is very excellent. It is that most non-developer uses of Linux do not require multiple kernels on the same host.
As a developer, I do edit, build and run more than one kernel, but the vast majority of desktop users never do such a thing.
I don't want to start an argument, but what would be the point of having grub (or lilo, if you like:-) offer desktop users the chance to load a server-tuned kernel? That would just make support issues for desktop help where none existed prior.
For the server, I'd also be doubtful of the utility of offering a desktop-tuned kernel to boot--especially with server blades--, but at least their assume an administrator would not get lost at a bootup screen. Contrariwise, it would make automatic reboots less attractive as either they would require manual intervention to pick a kernel to book, or there'd be an extra delay in the reboot for a timeout on kernel selection.
For that matter, why are you trying to do two completely different work loads and environments with the same kernel? You compile the kernel tuned to batch workloads for the server, and recompile the kernel tuned to interactive workloads for the desktop. You have the source.
More to the point, Kroupware sounds much too close to Crapware, and that's a bad joke I'd just as soon not hear. I hope they have a contest to rename the project; it is certainly insteresting work.
Well, yes, but this is precisely what Invisiblity means. The light wavefront is unchanged by the intervening object. This is the same sense in which glass is invisible, easily demonstrated by birds which accidently fly into large plates of glass they didn't see.
I wrote a BEEP implementation for Perl when I was working at Enron Broadband Services, but my group was never able to get the lawyers to let give it GPL licensing and release it publically.
At the time, it seemed like our choices for letting partners have some say in network routing through our backbone were SOAP or BEEP, and we favored BEEP because of partner pressure from Sun against all things favored by Microsoft (go figure). Eventually, we used simple XML messages rather than an entire application layer.
Early on, BEEP wasn't a difficult protocol to implement; however as time passed, it grew more and more complex, until it maintaining BEEP in a closed-source environment outweighed any benefits. At that point we switched to simple XML messages.
BEEP isn't a bad protocol at all. It is a little over-designed: as a fan of eXtreme Programming, I'd have preferred that smaller versions of the protocol get wider use and more feedback before being expanded.
This is a nice sentiment, but overlooks some points.
One doesn't only use spreadsheets to provide tabular data. For purely tabular data, you are quite right, and could just use tab-delimited files or something similar.
But often sophisticated spreadsheets include many presentation elements, such as graphs and formatted tables.
Even further, some include interesting extension such as database connectivity and the like.
I can't say if Excel uses a good or bad file format (I have no idea what it uses, actually), but it is probably and excellent candidate for XML or other structured representation. This is, after all, what the open-source competitors use.:-)
I could even say X11R6.4, but I don't want to. You may be correct, but I've never been anywhere that X wasn't informally referred to as X Windows or just plain X.
Personally, we use it at work the same way you'd use any of the other commercial X server providers. We run remote X applications on Unix boxes and display them on our Windows PC desktops.
One of my favorite tricks for newcomers at work is to run my entire KDE desktop from home, displaying to my PC desktop. Remote control was never easier.
The main drawback is speed. I don't think it's using the Broadway extensions, and X is very chatty. However, I've seen the same problem with other remote control software (e.g., Windows terminal thingy and VNC), so it might be a more generic problem than just with X Windows.
You are confusing X Windows with Linux. When you run X Windows under BSD, you are not running Linux on top of BSD. The same is true for X Windows under Microsoft Windows (not simply Windows XP, mind you, but also Windows 9x/NT/2k).
There's a drawback to your example comment as presented: reflowing the block loses the leading @'s at the start of each line. Instead, you might consider a blank line between significant elements, thus:
/**
* Get the Bug description for the given Id
*
* @pre id must be > 0 and less than BugList.lastId(), the highest bug number
*
* @post The return must not be null
*
* @invariant does not change the number of bugs
*/
Why is this marked "funny"? The author is perfectly serious, if perhaps using an amusing tone.
One of Unix's greatest strengths is the widespread use of human-readable files.
+ Do man pages use bizarre binary formats for markup? No, some inscruitable codes are there, but the text of the man page remains.
+ Are configuration files kept in a common, fragile binary repository? No, they are stored as human-readable, editable and searchable files.
Why does Microsoft want to change their filesystem? Well, they are now getting bitten in the butt for having binary file formats, and want to fix the problem by making yet more proprietary layers, locking out other search solutions.
This "modularizing the problem" point it a very nice one. Nuclear power is a wonderful solution to a problem of this sort, being much cleaner and safer than fossil fuel plants. And nuclear is practically old technology these days, at least compared to some of the interesting ideas for energy sources one sees in the press.
I totally believe it. You could suggest to that guy to find the russian
community in his town - I'm pretty sure Louisville has one, and they
usually have some private package shipping service going on, for nominal
fee. It originated when things were bad with food in Russia, and lots
of Russian stores in the states started offering food packages to
Russia. I've certainly seen ads here in the Houston store about sending
anything over.
book burning far too commonplace
on
Fahrenheit 451
·
· Score: 1
Book burning has been a hallmark of our century, although we certainly did not invent it.
I'm not sure this expresses the whole horror of book-burning. It may have been oft done in our present, nearly extinguished century, but it was also a hallmark of earlier periods. It's difficult to even speculate how many times the Torah was burned, for example. And how many famous libraries of the past burned after their navies or cities were sacked?
How does all of this (new techonology, existing stuff from Lucent, et al) compare to terabit optical routing? (I have Sycamore Networks in mind, but would be interested in hearing about others as well.)
The announced technology talks about 100Mbs, which is still too slow compared to an all-optical network, if I understand everything correctly.
Although I agree in general with your comments, your 4th point is incorrect. Just as with C++, the Java compiler is often able to detect when a method call does not need to be virtualized, and does not need to go through indirection.
This is especially so for two important cases: inlining function calls, and finalized classes (where the programmer instructs the compiler that there will be no subclassing).
One approach might be to treat DTDs similarly to interface definitions (as in IDL) and keep them in repositories by ORB-like intermediaries. XML documents are, after all, just instances of a particular DTD.
This has the advantage of reusing existing (ORB) technology for new purposes, and fits into an existing ideology that many already understand.
You would put a client of one of these XML ORBs into Apache or your browser client, and be able to exchange documents and DTDs freely just as with code objects and traditional ORBs.
What do you think the evolution of the Universe really is?
I've read recent news that there is evidence of an accelerating rate of expansion for the Universe, but my reading prior indicated that our Universe was poised at an point of neither expansion nor collapse.
How does the amatuer physicist evaluate competing claims like this?
Slashdot Mirror
Ah, please don't misunderstand. I think the proposed change is very excellent. It is that most non-developer uses of Linux do not require multiple kernels on the same host.
As a developer, I do edit, build and run more than one kernel, but the vast majority of desktop users never do such a thing.
I don't want to start an argument, but what would be the point of having grub (or lilo, if you like :-) offer desktop users the chance to load a server-tuned kernel? That would just make support issues for desktop help where none existed prior.
For the server, I'd also be doubtful of the utility of offering a desktop-tuned kernel to boot--especially with server blades--, but at least their assume an administrator would not get lost at a bootup screen. Contrariwise, it would make automatic reboots less attractive as either they would require manual intervention to pick a kernel to book, or there'd be an extra delay in the reboot for a timeout on kernel selection.
For that matter, why are you trying to do two completely different work loads and environments with the same kernel? You compile the kernel tuned to batch workloads for the server, and recompile the kernel tuned to interactive workloads for the desktop. You have the source.
More to the point, Kroupware sounds much too close to Crapware, and that's a bad joke I'd just as soon not hear. I hope they have a contest to rename the project; it is certainly insteresting work.
Well, yes, but this is precisely what Invisiblity means. The light wavefront is unchanged by the intervening object. This is the same sense in which glass is invisible, easily demonstrated by birds which accidently fly into large plates of glass they didn't see.
Quite.
Microsoft's "donation" is really a bribe; alternatively, Peru is extorting the money from them.
I wrote a BEEP implementation for Perl when I was working at Enron Broadband Services, but my group was never able to get the lawyers to let give it GPL licensing and release it publically.
At the time, it seemed like our choices for letting partners have some say in network routing through our backbone were SOAP or BEEP, and we favored BEEP because of partner pressure from Sun against all things favored by Microsoft (go figure). Eventually, we used simple XML messages rather than an entire application layer.
Early on, BEEP wasn't a difficult protocol to implement; however as time passed, it grew more and more complex, until it maintaining BEEP in a closed-source environment outweighed any benefits. At that point we switched to simple XML messages.
BEEP isn't a bad protocol at all. It is a little over-designed: as a fan of eXtreme Programming, I'd have preferred that smaller versions of the protocol get wider use and more feedback before being expanded.
This is a nice sentiment, but overlooks some points.
:-)
One doesn't only use spreadsheets to provide tabular data. For purely tabular data, you are quite right, and could just use tab-delimited files or something similar.
But often sophisticated spreadsheets include many presentation elements, such as graphs and formatted tables.
Even further, some include interesting extension such as database connectivity and the like.
I can't say if Excel uses a good or bad file format (I have no idea what it uses, actually), but it is probably and excellent candidate for XML or other structured representation. This is, after all, what the open-source competitors use.
I could even say X11R6.4, but I don't want to. You may be correct, but I've never been anywhere that X wasn't informally referred to as X Windows or just plain X.
I turn my head a little... that's it. It's a copyright symbol which fell down. The "C" is facing the baseline.
That depends on what you use it for. :-)
Personally, we use it at work the same way you'd use any of the other commercial X server providers. We run remote X applications on Unix boxes and display them on our Windows PC desktops.
One of my favorite tricks for newcomers at work is to run my entire KDE desktop from home, displaying to my PC desktop. Remote control was never easier.
The main drawback is speed. I don't think it's using the Broadway extensions, and X is very chatty. However, I've seen the same problem with other remote control software (e.g., Windows terminal thingy and VNC), so it might be a more generic problem than just with X Windows.
You are confusing X Windows with Linux. When you run X Windows under BSD, you are not running Linux on top of BSD. The same is true for X Windows under Microsoft Windows (not simply Windows XP, mind you, but also Windows 9x/NT/2k).
There's a drawback to your example comment as presented: reflowing the block loses the leading @'s at the start of each line. Instead, you might consider a blank line between significant elements, thus:
/**
* Get the Bug description for the given Id
*
* @pre id must be > 0 and less than BugList.lastId(), the highest bug number
*
* @post The return must not be null
*
* @invariant does not change the number of bugs
*/
Why is this marked "funny"? The author is perfectly serious, if perhaps using an amusing tone.
One of Unix's greatest strengths is the widespread use of human-readable files.
+ Do man pages use bizarre binary formats for markup? No, some inscruitable codes are there, but the text of the man page remains.
+ Are configuration files kept in a common, fragile binary repository? No, they are stored as human-readable, editable and searchable files.
Why does Microsoft want to change their filesystem? Well, they are now getting bitten in the butt for having binary file formats, and want to fix the problem by making yet more proprietary layers, locking out other search solutions.
This "modularizing the problem" point it a very nice one. Nuclear power is a wonderful solution to a problem of this sort, being much cleaner and safer than fossil fuel plants. And nuclear is practically old technology these days, at least compared to some of the interesting ideas for energy sources one sees in the press.
My recently Americanized Russian wife says:
I totally believe it. You could suggest to that guy to find the russian
community in his town - I'm pretty sure Louisville has one, and they
usually have some private package shipping service going on, for nominal
fee. It originated when things were bad with food in Russia, and lots
of Russian stores in the states started offering food packages to
Russia. I've certainly seen ads here in the Houston store about sending
anything over.
Sic scribit timothy:
I'm not sure this expresses the whole horror of book-burning. It may have been oft done in our present, nearly extinguished century, but it was also a hallmark of earlier periods. It's difficult to even speculate how many times the Torah was burned, for example. And how many famous libraries of the past burned after their navies or cities were sacked?How does all of this (new techonology, existing stuff from Lucent, et al) compare to terabit optical routing? (I have Sycamore Networks in mind, but would be interested in hearing about others as well.)
The announced technology talks about 100Mbs, which is still too slow compared to an all-optical network, if I understand everything correctly.
Although I agree in general with your comments, your 4th point is incorrect. Just as with C++, the Java compiler is often able to detect when a method call does not need to be virtualized, and does not need to go through indirection.
This is especially so for two important cases: inlining function calls, and finalized classes (where the programmer instructs the compiler that there will be no subclassing).
--binkley
One approach might be to treat DTDs similarly to interface definitions (as in IDL) and keep them in repositories by ORB-like intermediaries. XML documents are, after all, just instances of a particular DTD.
:-)
This has the advantage of reusing existing (ORB) technology for new purposes, and fits into an existing ideology that many already understand.
You would put a client of one of these XML ORBs into Apache or your browser client, and be able to exchange documents and DTDs freely just as with code objects and traditional ORBs.
Or so I would hope.
You young'uns have it good! Why in my day, we had to carry our TCP/IP packets in BUCKETS. UPHILL. BOTH WAYS! In the melting Texas heat, no less.
I would have killed any number of gnomies to have had that in my dorm room. This is the ugly face of envy.
What do you think the evolution of the Universe really is?
I've read recent news that there is evidence of an accelerating rate of expansion for the Universe, but my reading prior indicated that our Universe was poised at an point of neither expansion nor collapse.
How does the amatuer physicist evaluate competing claims like this?