I think you do miss one point on the particulate front:
- The only reason more efficient particulate filters are not on the US Edition TDI engines is that these filters work only in conjunction with advanced catalytic systems that require low sulphur diesel.
Sure, this is not important when Biodiesel is the conversation, no sulphur being present in the mix. But VW cannot sell a car for Biodiesel only can they ?
Will a TDI be ever as low-emission on particulates as a regular engine. Probably, but not without a large cost. Much like catalytic converters based on platinum plates, high quality particulate filters with good exhaust flow capability cost a lot of money.
Funny, I try my best to never sign a Non Disclure Agreement. It has meant that I fail to see neat stuff before others, it has meant that I cannot participate in neat projects and at least once it has held back my career by about 1 year.
But I could never fault the company for wanting such a protection to their secret. A NDA is binding and harsh. Tough.
Much like in Highschool, some jackass cannot keep a secret. Fine, I don't need a personal secret revealed and I undertand Apple doesn't either.
Real fan's wouldn't want to break the mystique of a "X-mas like" introduction... would they ?
I assume VA & HP are adding JetDirect "port" support into Linux, something that already exists (thank dog) in AIX.
Under AIX, dealing with the Byzantine print system is truly easier when using JetDirect "ports".
So, we can look forward to multiple logical queues to a single physical HP printer. Each queue could carry with it a series of paper, orientation and other defaults. Each queue could have bi-directional messages, like toner low, and it would propagate to client PCs (say Windows).
All neat and tidy, but simple LPR/LPD, using PostScript has worked rather well for all our HP printers. Trouble always stems from older Windows software that has some built-in assumption of the end-device, forcing us to try a PCL driver to compensate.
I look forward to dissecting the new printing mechanism. One less reason to have an NT print server.
I'm glad Tim wrote this, I certainly began thinking about items mentioned.
I started with Object Oriented programing by buying a NeXT and beating my head against the ideas of Objective-C. I learned the hard way that C=A+B is what I wanted, but then it wasn't possible...
Or was it. Unlike C++, Objective-C, a strange descendent of Smalltalk and C, did allow me to write a set of very clean abstarctions to do exactly C=A+B, where A,B&C are arrays.
Why? Objective-C is run-time bound, therefore programs can be extended after compilation.
Today, Apple plays down the impact of Objective-C in their Mac OS X documentation. It was the crown jewel at NeXT and the reason Carmack and Co built Doom on the platform. The programming tools were better (and most copied) then anywhere.
And yes, there was a penalty in speed for all this "late binding" and abstraction. On my 25Mhz NeXT, that was alright for the sheer simplicity of design.
With the proliferation of Mhz today, you would think that we could just adopt the same things and run with it? Naw, Tim also pointed out a strong failure of the programming community: Once a language is deemed "unpopular", no matter what it is giid for, it is discarded.
That's fine, maybe PR is all that a language really needed. Heck, if you can write UT or Quake3 with it... it must be good.
Wow, I can't believe this is an issue. Are Linux users really out to stifle other OSs?
Mac OS X is a grandson of NeXTstep, a BSD derivative OS. Under NeXTstep, we (users/developers) were actually pushing NeXT to stay on top of the changes being wrought by BSD 4.4 Lite, to allow the source code and libraries to be free of restrictions and to benefit of improvements.
So what is wrong with them continuing this trend of working closely with BSD?
Years ago, I bought a NeXT Colorstation to benefit from an improved Mac like GUI interface, a BSD based Unix with a GNU C compiler, an Object Development system that still impresses me, a Display Postscript environment "because it made sense". And the sum of all parts outweighed the individual pieces.
Now, those days are gone, but Mac OS X announces itself as a great "user Experience." I still own and use my NeXT and would pay $$$ to simply update the hardware under it to something current. Barring that, an iBook running OS X may just suite me fine.
My dual-Celeron Linux server, my Cobalt Qube and any other Linux boxes simply never matched the consistency of that old BSD Unix based NeXT. I think that is also the perception of the engineers at Apple (Nue NeXT).
I may have disliked the tone of the Mindcraft test, but they did provide the documents for the entire test configuration. For personal satisfaction, when can we see the equivalent documents from this PC Week test ? I don't think PC Week is hoilding this information back for any other reason than they forgot how intrested most of us are in the details". PC Week... publish the details. Please.:)
I booked May 19th as a Vacation day about two months ago and therefore I get to enjoy it. Being out of the office, our rules for "backup person" prevent others from taking that day. These loose restrictions are actually quite flexible for an old-fashioned company like ours.
Claiming sickness would not cut it either, just a little too obvious.
I'm also the "boss" in IS and will have to enforce the fact that others will need be at work. Wish I could take them all, but the rules are...
Slashdot Mirror
Here in cold-balls Montreal, EVERYONE has electric heating; most people haven't made use of central heating, as Hydro Quebec is the defacto logic.
That said, after the infamous Ice Storm, many have wood/gas/oil heaters as well.
I think you do miss one point on the particulate front:
- The only reason more efficient particulate filters are not on the US Edition TDI engines is that these filters work only in conjunction with advanced catalytic systems that require low sulphur diesel.
Sure, this is not important when Biodiesel is the conversation, no sulphur being present in the mix. But VW cannot sell a car for Biodiesel only can they ?
Will a TDI be ever as low-emission on particulates as a regular engine. Probably, but not without a large cost. Much like catalytic converters based on platinum plates, high quality particulate filters with good exhaust flow capability cost a lot of money.
You can learn from http://behardware.com/ I just recomend it to anyone, and *no*, I have no affiliation. Example of a great article is the "Mura effect "http://www.behardware.com/articles/589-1/panels-a -carte-mura-components-dead-pixels.html
You can learn from behardware.com/
p anels-a-carte-mura-components-dead-pixels.html
I just recomend it to anyone, and *no*, I have no affiliation.
Example of a great article is the "Mura effect":http://www.behardware.com/articles/589-1/
Funny, I try my best to never sign a Non Disclure Agreement. It has meant that I fail to see neat stuff before others, it has meant that I cannot participate in neat projects and at least once it has held back my career by about 1 year.
... would they ?
But I could never fault the company for wanting such a protection to their secret. A NDA is binding and harsh. Tough.
Much like in Highschool, some jackass cannot keep a secret. Fine, I don't need a personal secret revealed and I undertand Apple doesn't either.
Real fan's wouldn't want to break the mystique of a "X-mas like" introduction
I assume VA & HP are adding JetDirect "port" support into Linux, something that already exists (thank dog) in AIX.
Under AIX, dealing with the Byzantine print system is truly easier when using JetDirect "ports".
So, we can look forward to multiple logical queues to a single physical HP printer. Each queue could carry with it a series of paper, orientation and other defaults. Each queue could have bi-directional messages, like toner low, and it would propagate to client PCs (say Windows).
All neat and tidy, but simple LPR/LPD, using PostScript has worked rather well for all our HP printers. Trouble always stems from older Windows software that has some built-in assumption of the end-device, forcing us to try a PCL driver to compensate.
I look forward to dissecting the new printing mechanism. One less reason to have an NT print server.
I'm glad Tim wrote this, I certainly began thinking about items mentioned.
... it must be good.
I started with Object Oriented programing by buying a NeXT and beating my head against the ideas of Objective-C. I learned the hard way that C=A+B is what I wanted, but then it wasn't possible...
Or was it. Unlike C++, Objective-C, a strange descendent of Smalltalk and C, did allow me to write a set of very clean abstarctions to do exactly C=A+B, where A,B&C are arrays.
Why? Objective-C is run-time bound, therefore programs can be extended after compilation.
Today, Apple plays down the impact of Objective-C in their Mac OS X documentation. It was the crown jewel at NeXT and the reason Carmack and Co built Doom on the platform. The programming tools were better (and most copied) then anywhere.
And yes, there was a penalty in speed for all this "late binding" and abstraction. On my 25Mhz NeXT, that was alright for the sheer simplicity of design.
With the proliferation of Mhz today, you would think that we could just adopt the same things and run with it? Naw, Tim also pointed out a strong failure of the programming community: Once a language is deemed "unpopular", no matter what it is giid for, it is discarded.
That's fine, maybe PR is all that a language really needed. Heck, if you can write UT or Quake3 with it
Wow, I can't believe this is an issue. Are Linux users really out to stifle other OSs?
Mac OS X is a grandson of NeXTstep, a BSD derivative OS. Under NeXTstep, we (users/developers) were actually pushing NeXT to stay on top of the changes being wrought by BSD 4.4 Lite, to allow the source code and libraries to be free of restrictions and to benefit of improvements.
So what is wrong with them continuing this trend of working closely with BSD?
Years ago, I bought a NeXT Colorstation to benefit from an improved Mac like GUI interface, a BSD based Unix with a GNU C compiler, an Object Development system that still impresses me, a Display Postscript environment "because it made sense". And the sum of all parts outweighed the individual pieces.
Now, those days are gone, but Mac OS X announces itself as a great "user Experience." I still own and use my NeXT and would pay $$$ to simply update the hardware under it to something current. Barring that, an iBook running OS X may just suite me fine.
My dual-Celeron Linux server, my Cobalt Qube and any other Linux boxes simply never matched the consistency of that old BSD Unix based NeXT. I think that is also the perception of the engineers at Apple (Nue NeXT).
I may have disliked the tone of the Mindcraft test, but they did provide the documents for the entire test configuration. For personal satisfaction, when can we see the equivalent documents from this PC Week test ? I don't think PC Week is hoilding this information back for any other reason than they forgot how intrested most of us are in the details". PC Week... publish the details. Please. :)
I booked May 19th as a Vacation day about two months ago and therefore I get to enjoy it. Being out of the office, our rules for "backup person" prevent others from taking that day. These loose restrictions are actually quite flexible for an old-fashioned company like ours.
...
...
Claiming sickness would not cut it either, just a little too obvious.
I'm also the "boss" in IS and will have to enforce the fact that others will need be at work. Wish I could take them all, but the rules are
If you book it