As an example, the WINE project has great difficulties with X's poor font handling. It doesn't provide anywhere near the capabilities of the Win32 interface, and thus makes it very difficult to emulate those parts on Win32.
I have wondered if Display postscript could be the answer to X's font woes, but I don't know enough about what it provides, and in any case, the GNU version isn't at production level yet.
An interesting tangential point (well, not open source related) is how all the other neat stuff in the lab works, and how you would go about making things *really* unrecoverable... There is an interesting paper on the subject available form Auckland university. Worth a read.
How about making any one MM session get all it's posts from one slashdot article. ie: you gon into MM, and 10 posts get picked from *one* article and shown to you.
This would: o Give you some idea of the relative quality of the posts. o Mean you only had to check once to see what the article was about o Make it obvious when a post was off-topic o Make spotting flamebait and trolls much easier
Another idea would be to do the MM in the actual article-discussion itself.....
Based on RP5 the animations probably require Shockwave. As macromedia do not make a Linux player, RP can't play them.
As SW format is now "open" and there *is* a Linux player I wonder if the RP plug-in format is documented well enough to create the components necessary for playback??
Somthing that has always bothered me with this sort of case: What about RF interference. A conventional metal case sheilds quite well against both emission and absorbtion of RF interference. Most of the opaque plastic cases are metal or foil lined. Do these see-thru cases make the grade? Or are these cases going to make my TV go on the blink?
Maybe prople didn't know this, but Compaq have been having a lot of trouble with their supply/inventory/financials systems. This has resulted in huge delays in delivery, even on relatively common parts.
They always used to have supply troubles, esp. in the Asia-Pacific region (where I am) but everything was supposed to be fixed by the new SAP system being implemented.... Needless to say, it hasn't, in fact things have gotten *much* worse.
Rumor has it that the cutover to SAP was supposed to happen in one weekend! It dragged on for months.
This may have had an impact on the bottom line, but it would certainly have had an impact on customer satisfaction levels....
This is not a terrably good metaphor. When you refer to Power in the Porche, you are talking about engine size, road handling, etc.
Power as referred to here is about control over the system and it's environment, not CPU horsepower. The Porche is easy to use because it severly restricts the on the fly control you have over the car. (eg, AFAIK you can't adjust the fuel/air ratio easily, etc) The defaults may be extreemly good, and the automatic control excelent (you are paying for a Porche) but you have to be a mechanic to have "Power" (in this sense)
I disagree. This is not purely a Linux problem. Many people do not know where everything is in Windows, and that's smaller! If you don't know a program is there is that in any way worse than not having it? I don't see how, apart from disk space.
The main problem is how to track down the best tool for a job. This is a prennial problem, and is not yet solved to my satisfaction.
the GUI approach is to show choices on screen via "menus" and "toolbars" This once made things simpler, but now there are too many choices, and things end up being buried in sub menus, and are difficult to find. This approach also leads to large "multi-function" applications, as it tends to be difficult to use GUI tools in concert.
The unix/CLI approach is to provide lots of small tools that can be strung togeather, or programmed to provide any functionality. This makes ir harder initally, as lots of commands have to be *learnt* as well as how to string them togeather, but means that many obscure functions can be created on the fly by the user.
Neither soleve all the problems and even the CLI method still makes it hard to find the right tool for many functions. I often find myself doing a man -k and sometimes I'm lucky... Some sort of find tool by function might be nice, but perhaps there are too many possible descriptions of functions....
Some of the concepts I guess I'm trying to describe are things like LATEX where you request a heading, and the computer handles the details, but applied to the whole system...... I really don't know where to start, put perhaps this group do, and perhaps they will help to take Linux to a new level - I want *easier* to use than Windows!
I think their complaint against Linux was simply that after the card change, drivers for the new card were simply not available. Whereas presumably drivers for Micros~1 systems would have shipped with the system.
This is really the manufacturer's fault. They should (in an ideal world) make Linux (or XFree86) drivers available with hardware release.
I agree that they should have ensured hardware continuity accross the rollout. This is common practice on all rollouts. Sometimes you have no choice though.
Could someone explain to the more ignorant of us exactly *what* has been closed off? Just Zone transfers from the root servers? Or ability to send queries (and then, recursive, or not?)
If they did block non-recursive queries, surely the DNS system would stop....
Sorry, but I didn't find the article technically clear.
Many/most PC thefts these days involve opening the case and swiping the memory and CPU, both of which are difficult to identify, and easy to sell. Most companies could easily add the CPU IDs to their asset database and report them stolen. When the police catch up with someone with a dozen CPUs stashed under the bed, they could actually *prove* that they were the ones that went missing from xyz corp last week. It would also help you get your parts back if they were found, as you would be able to show they were actually yours.
As for the rest, you are right, and I think the writers should hang their heads in shame for writing such an ill thought out article. Adrian
Slashdot Mirror
X needs to be improved.
As an example, the WINE project has great difficulties with X's poor font handling. It doesn't provide anywhere near the capabilities of the Win32 interface, and thus makes it very difficult to emulate those parts on Win32.
I have wondered if Display postscript could be the answer to X's font woes, but I don't know enough about what it provides, and in any case, the GNU version isn't at production level yet.
An interesting tangential point (well, not open source related) is how all the other neat stuff in the lab works, and how you would go about making things *really* unrecoverable... There is an interesting paper on the subject available form Auckland university. Worth a read.
How about making any one MM session get all it's posts from one slashdot article. ie: you gon into MM, and 10 posts get picked from *one* article and shown to you.
This would:
o Give you some idea of the relative quality of the posts.
o Mean you only had to check once to see what the article was about
o Make it obvious when a post was off-topic
o Make spotting flamebait and trolls much easier
Another idea would be to do the MM in the actual article-discussion itself.....
Based on RP5 the animations probably require Shockwave. As macromedia do not make a Linux player, RP can't play them.
As SW format is now "open" and there *is* a Linux player I wonder if the RP plug-in format is documented well enough to create the components necessary for playback??
Somthing that has always bothered me with this sort of case: What about RF interference. A conventional metal case sheilds quite well against both emission and absorbtion of RF interference. Most of the opaque plastic cases are metal or foil lined. Do these see-thru cases make the grade? Or are these cases going to make my TV go on the blink?
Adrian
Maybe prople didn't know this, but Compaq have been having a lot of trouble with their supply/inventory/financials systems. This has resulted in huge delays in delivery, even on relatively common parts.
They always used to have supply troubles, esp. in the Asia-Pacific region (where I am) but everything was supposed to be fixed by the new SAP system being implemented.... Needless to say, it hasn't, in fact things have gotten *much* worse.
Rumor has it that the cutover to SAP was supposed to happen in one weekend! It dragged on for months.
This may have had an impact on the bottom line, but it would certainly have had an impact on customer satisfaction levels....
This is not a terrably good metaphor. When you refer to Power in the Porche, you are talking about engine size, road handling, etc.
Power as referred to here is about control over the system and it's environment, not CPU horsepower. The Porche is easy to use because it severly restricts the on the fly control you have over the car. (eg, AFAIK you can't adjust the fuel/air ratio easily, etc) The defaults may be extreemly good, and the automatic control excelent (you are paying for a Porche) but you have to be a mechanic to have "Power" (in this sense)
I disagree. This is not purely a Linux problem. Many people do not know where everything is in Windows, and that's smaller! If you don't know a program is there is that in any way worse than not having it? I don't see how, apart from disk space.
The main problem is how to track down the best tool for a job. This is a prennial problem, and is not yet solved to my satisfaction.
the GUI approach is to show choices on screen via "menus" and "toolbars" This once made things simpler, but now there are too many choices, and things end up being buried in sub menus, and are difficult to find. This approach also leads to large "multi-function" applications, as it tends to be difficult to use GUI tools in concert.
The unix/CLI approach is to provide lots of small tools that can be strung togeather, or programmed to provide any functionality. This makes ir harder initally, as lots of commands have to be *learnt* as well as how to string them togeather, but means that many obscure functions can be created on the fly by the user.
Neither soleve all the problems and even the CLI method still makes it hard to find the right tool for many functions. I often find myself doing a
man -k
and sometimes I'm lucky... Some sort of find tool by function might be nice, but perhaps there are too many possible descriptions of functions....
Some of the concepts I guess I'm trying to describe are things like LATEX where you request a heading, and the computer handles the details, but applied to the whole system...... I really don't know where to start, put perhaps this group do, and perhaps they will help to take Linux to a new level - I want *easier* to use than Windows!
I think their complaint against Linux was simply that after the card change, drivers for the new card were simply not available. Whereas presumably drivers for Micros~1 systems would have shipped with the system.
This is really the manufacturer's fault. They should (in an ideal world) make Linux (or XFree86) drivers available with hardware release.
I agree that they should have ensured hardware continuity accross the rollout. This is common practice on all rollouts. Sometimes you have no choice though.
Adrian
Could someone explain to the more ignorant of us exactly *what* has been closed off? Just Zone transfers from the root servers? Or ability to send queries (and then, recursive, or not?)
If they did block non-recursive queries, surely the DNS system would stop....
Sorry, but I didn't find the article technically clear.
Adrian
Actually, It will help with chip theft...
Many/most PC thefts these days involve opening the case and swiping the memory and CPU, both of which are difficult to identify, and easy to sell. Most companies could easily add the CPU IDs to their asset database and report them stolen. When the police catch up with someone with a dozen CPUs stashed under the bed, they could actually *prove* that they were the ones that went missing from xyz corp last week. It would also help you get your parts back if they were found, as you would be able to show they were actually yours.
As for the rest, you are right, and I think the writers should hang their heads in shame for writing such an ill thought out article.
Adrian