An amazing thing I heard that Tucker automobile company was working with Ford to bring the Tuckers back to life. All 50 original owners are very excited to see the new car. It still uses the original engine, they just slapped a turbo on it and a catalytic converter for the emissions. I think they also added seatbelts and an airbag.
I work for a silicon wafer manufacturer, we supply Intel, AMD, etc with the wafers that they put the chips onto.
The wafers we supply have and 'Epi' layer on them, which is short for epitaxial. The layer is silicon that is grown on the wafer at a high tempurature (I think 950-1000 degrees C). This makes the wafers less rough, thus smaller lines widths. The wafers are inspected for defects, and the machines that inspect them can only see particles, pits, etc down to.13 micron. The human eye can only see down to.30 microns or so. (That's under ideal conditions, dark room, 200 watt halogen light focused on the wafer.) Needless to say there has been a transition to machine only inspection as the chip lines widths have gotten smaller.
Intel already annoucing the.13 micron line widths makes me wonder what the yields will be like. The machines that can see down to.13 micron run about 1/2 million or so. I haven't seen what the next generation of them will do, but I know that we don't have them installed in our plant yet. That is definately one reason why it takes so long for this stuff to reach consumers. The clean rooms that the wafers are cleaned and inspected in are filtered down to class 10, which translates to less than 10 particles in the air at.3 microns. We usually have 0-1 at.1 microns. Makes an operating room look positively filthy.
The wafer manufacturers are mostly breaking even at this point. Intel is making fat cash, but they are getting it from squeezing all the wafer suppliers. Some have dropped out of the business do to the lean conditions. Nobody really has enough money to buy equipment to make these wafers on a large scale, let only finding vendors that have equipment that meets those specs.
The funny part is that VB has pointers in it, they're just not documented. You can find how to get to them in Hardcore Visual Basic. You can also get the AddressOf a function for callbacks. You can pass pointers from API calls to other API calls and cause all kinds of problems, just like you can in C. Can't write unsafe code, HAH!
The main reason to use the proxy servers is for caching. Try downloading a big file, and then when it's done do it again. The second download should be much faster, for a while. I'm sure they also track where their customers are going, but you also get a speed up on commonly accessed web sites. Oh, and you get the enhanced 128K max upload speed. It's good for you, trust them.
Thanks much! I dove into the comments just to look for a reference to the book. The only books I typically see for OS design that have source try to do some crappy DOS compatible thing. I would like to understand the Linux (or BSD) source, but ddin't really know where to start.
People who haven't rebooted since they installed, could still be using RH 5.2. One of the funny things with NT, I tend to stay more on top of the fixes because I have to reboot the NT servers more often. (Might as well try a the latest SP while I'm at it) The Linux servers rarely even have a monitor plugged in. I do all the administration remotely, and they just run. So I'm sure there are a number of RH 5.2's that have been up for a year that nobody wants to reboot for the upgrade.
I use VB all the time, for a very specific purpose, connecting a Windows GUI to data. I can easily get to any ODBC DB out there. VB excels (Microsoft Excel?) at easy data access. The newest version can end up looking more like Foxpro, or Access, if you want. You can connect to a database and drag and drop to create forms that link to the data. The language pretty much sucks, it not OO, no matter what the documentation says. If you try to do anything OO in it, you just get confused by it's poor implementation. (It really only has encapsulation.) I works great as a glue between C/C++ components, DBs and a GUI. It is kind of like the way you would use Perl on Unix. A lot of Perl code is real ugly, but if it gets the job done quicker, it's cool.
Maybe a better comparison would be with the IBM PC? A fairly open design, that is still around today (I'm typing on a PC clone now). Which computer platforms survived? Just a few, and of course M$.
Besides I drive a VW, so everyone in the world should drive one. Let's eliminate choices, they're no good...
Slashdot Mirror
An amazing thing I heard that Tucker automobile company was working with Ford to bring the Tuckers back to life. All 50 original owners are very excited to see the new car. It still uses the original engine, they just slapped a turbo on it and a catalytic converter for the emissions. I think they also added seatbelts and an airbag.
Isn't that now ePotato? Since Gore invented the Internet.
Does this mean potato power is supported in the kernel finally?
I work for a silicon wafer manufacturer, we supply Intel, AMD, etc with the wafers that they put the chips onto.
.13 micron. The human eye can only see down to .30 microns or so. (That's under ideal conditions, dark room, 200 watt halogen light focused on the wafer.) Needless to say there has been a transition to machine only inspection as the chip lines widths have gotten smaller.
.13 micron line widths makes me wonder what the yields will be like. The machines that can see down to .13 micron run about 1/2 million or so. I haven't seen what the next generation of them will do, but I know that we don't have them installed in our plant yet. That is definately one reason why it takes so long for this stuff to reach consumers. The clean rooms that the wafers are cleaned and inspected in are filtered down to class 10, which translates to less than 10 particles in the air at .3 microns. We usually have 0-1 at .1 microns. Makes an operating room look positively filthy.
The wafers we supply have and 'Epi' layer on them, which is short for epitaxial. The layer is silicon that is grown on the wafer at a high tempurature (I think 950-1000 degrees C). This makes the wafers less rough, thus smaller lines widths. The wafers are inspected for defects, and the machines that inspect them can only see particles, pits, etc down to
Intel already annoucing the
The wafer manufacturers are mostly breaking even at this point. Intel is making fat cash, but they are getting it from squeezing all the wafer suppliers. Some have dropped out of the business do to the lean conditions. Nobody really has enough money to buy equipment to make these wafers on a large scale, let only finding vendors that have equipment that meets those specs.
.01 micron, holy crap!
The funny part is that VB has pointers in it, they're just not documented. You can find how to get to them in Hardcore Visual Basic. You can also get the AddressOf a function for callbacks. You can pass pointers from API calls to other API calls and cause all kinds of problems, just like you can in C. Can't write unsafe code, HAH!
The main reason to use the proxy servers is for caching. Try downloading a big file, and then when it's done do it again. The second download should be much faster, for a while. I'm sure they also track where their customers are going, but you also get a speed up on commonly accessed web sites. Oh, and you get the enhanced 128K max upload speed. It's good for you, trust them.
Maybe Jamcracker could replace GPFs. I kinda like the ring of it. Sorta like the Amigas Guru Mediatation error.
Thanks much! I dove into the comments just to look for a reference to the book. The only books I typically see for OS design that have source try to do some crappy DOS compatible thing. I would like to understand the Linux (or BSD) source, but ddin't really know where to start.
People who haven't rebooted since they installed, could still be using RH 5.2. One of the funny things with NT, I tend to stay more on top of the fixes because I have to reboot the NT servers more often. (Might as well try a the latest SP while I'm at it) The Linux servers rarely even have a monitor plugged in. I do all the administration remotely, and they just run. So I'm sure there are a number of RH 5.2's that have been up for a year that nobody wants to reboot for the upgrade.
I use VB all the time, for a very specific purpose, connecting a Windows GUI to data. I can easily get to any ODBC DB out there. VB excels (Microsoft Excel?) at easy data access. The newest version can end up looking more like Foxpro, or Access, if you want. You can connect to a database and drag and drop to create forms that link to the data. The language pretty much sucks, it not OO, no matter what the documentation says. If you try to do anything OO in it, you just get confused by it's poor implementation. (It really only has encapsulation.) I works great as a glue between C/C++ components, DBs and a GUI. It is kind of like the way you would use Perl on Unix. A lot of Perl code is real ugly, but if it gets the job done quicker, it's cool.
Maybe a better comparison would be with the IBM PC? A fairly open design, that is still around today (I'm typing on a PC clone now). Which computer platforms survived? Just a few, and of course M$.
Besides I drive a VW, so everyone in the world should drive one. Let's eliminate choices, they're no good...