If you consider yourself a "web developer" and don't know how to manipulate the URI fragment to make the back button work with AJAX, then you should just quit right now and become a politician or a lawyer or something. The back button is fundamental and all AJAX applications should work with it.
Once I spotted a beautiful yellow 3rd-generation Mazda RX-7 in a parking lot, back when such cars were new and shiny. I said to my friends "Check out my new car" to which they all replied with the obligatory "cha, right" knowing that I drove a lowly 1985 Mazda 626. Undeterred, I sauntered up to the RX-7, inserted the key to my 626, and it worked! I couldn't believe it, but then I made a habit of trying it on various cars and found that it worked about one time in ten.
I still use Windows 2000 wherever I need Windows. It runs all the games I have, and it can still be installed on recent PCs as long as they don't use native AHCI and don't have enormous LBA disks. There's nothing in Windows 2000 that is worse than what was in Windows NT Workstation 4.0, so it was a logical upgrade from that. But there's tons of stuff in XP that regresses with respect to Windows 2000, so I never upgraded. Also, by sticking with one version I become immune to Microsoft's perpetual crusade to make my Windows admin knowledge obsolete.
The downsides are that Win2k sucks on a laptop, has bad/no wireless networking, and has many usb and firewire quirks. But if your computer is more along the lines of keyboard+cpu+display, and it sits on the floor, it should work fine.
It's both. The kernel is responsible for setting up the execution environment, and in the past it used a fixed 32 pages for the arguments. 32 pages on an ordinary PC is 128KiB, which is the old limit. The new limit is that any one argument can be up to 32 pages, and all the arguments taken together can be 0x7FFFFFFF bytes, which is ~2GiB.
After that, it was up to libc people to fix the globbing routines. Ulrich Drepper, taking some time off from his full-time job of being an asshole on mailing lists, managed to work this into glibc 2.8:
Sure, I agree with everything you wrote. I was only trying to answer the question of whether a camera has enough resolving power to justify this number of pixels. The answer seems to me to be "yes, under certain ideal conditions." If you are taking your photo at f/11 for aesthetic reasons or because your lens is sharper at that stop, then clearly having more than 50MP on this size sensor would be totally pointless.
The rule of thumb is that the Airy disk for visible light has roughly the same diameter, in microns, as the f number. Therefore it is impractical to decrease the pixel size much below 2 microns. The only thing you can do to get more resolution is make the sensors physically bigger.
Actually, a patch was recently added to Linux to dynamically allocate the command line, so your argument length is now bounded only by available memory.
Well I'm sorry to break it to you, but the size of the Airy disk at f/5.6 is 7.5 microns, therefore any sensor with smaller pixels can be said to be diffraction-limited. If you want to discard the issue of color, and consider just the luminance, then the 2x2 pattern gives you a 12 micron area diameter in which case the system is diffraction-limited at f/11 and smaller. But if you do that you must be willing to admit that the system has only 3 megapixels instead of 12.
You appear to be operating under some definition of diffraction-limited other than "limited by diffraction". Also I would like to point out that 12MP on a 16x24mm sensor is 6 microns, not "less than 6 microns".
If the lens is perfect (which it isn't, but let's assume that) the camera will be diffraction-limited. At a certain aperture, the Airy disk will be larger than the pixels in the sensor. This camera has 6-micron pixels, which is very small indeed. Cameras with this sensor will probably be diffraction-limited at f/5.6 and smaller apertures.
It is important to remember three things: Colin Powell is a lying cocksucker who covered up a war crime in Vietnam. Seymour Hersh is a brilliant journalist who broke the story of that war crime.
Third thing: For almost a year, Seymour Hersh has been writing in the New Yorker about Dick Cheney's preparations for a war, possibly even a nuclear first strike, against Iran.
Not just that, but it filters out RST packets that may in fact have been sent by the peer. So this trick can leave you with sockets hanging open in a bad state.
You don't have to do it for the user accounts if you put it in/etc. And you can't call yourself a sysadmin if you don't have already have a way to distribute a file to all your hosts.
Only if you're an idiot who can't read the manual. See/etc/ssh/ssh_known_hosts. You put the new key into known hosts ahead of time, then you change the keys, then you remove the old key from known_hosts. No automated logins will have been broken.
The point is that with OSP you have bare copper pads. You don't need to put any kind of metal finish on the board at all, certainly not the traditional tin/lead finish. In fact the tin/lead HASL finish is practically useless with fine-pitch QFN parts that are no so popular, because HASL has bad planarity. OSP has the best planarity of any board finish.
The Thunderbird does 0-60 in about 9 or 10 seconds, depending, and a factory stock 2008 Toyota Sienna reaches 60 in 6.6 seconds according to Car and Driver. You're letting some rosy vision of musclecar glory cloud your judgment.
The problem of tin whiskers is real but the consequences ascribed to them by Cringley are not. A printed circuit board like the one in your computer or TV is made of fiberglass and copper layered in a sandwich. In the early days of electronics the copper was plated with tin to prevent corrosion, but scientists discovered that pure tin tends to form hairlike growths, causing the circuits to fail. Adding lead to the tin prevented the growths, and had other desirable properties, so the tin/lead alloy became a universal standard.
More recently we got something called "the restriction of the use of certain hazardous substances in electrical and electronic equipment" or RoHS. RoHS prohibits the sale of materials containing more than 1% lead in the EU. (Old-style electronic assemblies use 37% lead solder.) RoHS came into force in 2006 but research into lead-free electronics began decades ago. Initially researchers tried pure tin plating, which lead to tin whiskers. Some products marketed in the late 90's even failed from this problem. But researchers did not throw up their hands in despair. RoHS has led to innovations in metallurgy to the extent that a circuit board designer can now choose from half a dozen different alloys. Today only 2% of printed circuit boards use tin plating.
Some of these new alloys use gold or silver finishes over copper. These are completely immune to tin whiskers. The most popular new system eliminated the plating step, attaching components directly to the bare copper using chemicals called Organic Solderability Preservatives. OSP leads to stronger and more durable assemblies than even the old tin/lead process.
The whining we see today on the subject of RoHS mirrors almost perfectly the doomsaying seen when California began regulating automobile emissions. There was at that time a tremendous amount of yelling about how the catalytic converter spelled the end of civilization as we know it, and only a moron would take the lead out of gasoline. But soon afterwards we saw the introduction of clean, efficient, powerful cars by Honda. Honda was even able to meet California emissions standards without using catalytic converters or even fuel injection. Their brand of engineering eventually trickled down to even the most benighted American car maker, and California emissions standards are now in force in every industrialized nation.
I would expect to see the same thing with RoHS. We have only just entered the initial stage of complaining. The tin/lead dinosaurs with backwards-looking engineering departments face an existential crisis. In other design houses the challenge of lead-free assembly is being embraced as a competitive advantage. Those who can adapt to RoHS will thrive and those who cannot will clearly suffer.
Cringley brags about a 1966 Thunderbird with a 428 cu. in. motor, a car so heavy, so polluting, and so slow by modern standards that it would be impounded by CARB and laughed off a drag strip by a base model minivan. As time goes on I think Cringley's views on the metallurgy of printed circuit boards will seem as antique at that T-Bird.
This was _always_ a feature in Netscape. It got dropped in the transition from Netscape to Mozilla. It's one of those problems with open source development: there's no guarantee that useful, widely-used features are carried forward into new versions.
Shouldn't the title of this post be "Shitty router programming causing router crashes"? It should matter what type of garbage come off the wire, the router must be able to handle it all without error.
That's ridiculous. OpenSecrets counts industries by the employers stated by individual contributors. That's a very different thing from contributions from actual corporations (which are mainly made to PACs, not to campaigns).
Slashdot Mirror
If you consider yourself a "web developer" and don't know how to manipulate the URI fragment to make the back button work with AJAX, then you should just quit right now and become a politician or a lawyer or something. The back button is fundamental and all AJAX applications should work with it.
Once I spotted a beautiful yellow 3rd-generation Mazda RX-7 in a parking lot, back when such cars were new and shiny. I said to my friends "Check out my new car" to which they all replied with the obligatory "cha, right" knowing that I drove a lowly 1985 Mazda 626. Undeterred, I sauntered up to the RX-7, inserted the key to my 626, and it worked! I couldn't believe it, but then I made a habit of trying it on various cars and found that it worked about one time in ten.
I still use Windows 2000 wherever I need Windows. It runs all the games I have, and it can still be installed on recent PCs as long as they don't use native AHCI and don't have enormous LBA disks. There's nothing in Windows 2000 that is worse than what was in Windows NT Workstation 4.0, so it was a logical upgrade from that. But there's tons of stuff in XP that regresses with respect to Windows 2000, so I never upgraded. Also, by sticking with one version I become immune to Microsoft's perpetual crusade to make my Windows admin knowledge obsolete. The downsides are that Win2k sucks on a laptop, has bad/no wireless networking, and has many usb and firewire quirks. But if your computer is more along the lines of keyboard+cpu+display, and it sits on the floor, it should work fine.
It's both. The kernel is responsible for setting up the execution environment, and in the past it used a fixed 32 pages for the arguments. 32 pages on an ordinary PC is 128KiB, which is the old limit. The new limit is that any one argument can be up to 32 pages, and all the arguments taken together can be 0x7FFFFFFF bytes, which is ~2GiB.
Here's the diff: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b6a2fea39318e43fee84fa7b0b90d68bed92d2ba;hp=bdf4c48af20a3b0f01671799ace345e3d49576da
After that, it was up to libc people to fix the globbing routines. Ulrich Drepper, taking some time off from his full-time job of being an asshole on mailing lists, managed to work this into glibc 2.8:
http://sourceware.org/ml/libc-alpha/2008-04/msg00050.html
Sure, I agree with everything you wrote. I was only trying to answer the question of whether a camera has enough resolving power to justify this number of pixels. The answer seems to me to be "yes, under certain ideal conditions." If you are taking your photo at f/11 for aesthetic reasons or because your lens is sharper at that stop, then clearly having more than 50MP on this size sensor would be totally pointless.
The rule of thumb is that the Airy disk for visible light has roughly the same diameter, in microns, as the f number. Therefore it is impractical to decrease the pixel size much below 2 microns. The only thing you can do to get more resolution is make the sensors physically bigger.
Actually, a patch was recently added to Linux to dynamically allocate the command line, so your argument length is now bounded only by available memory.
Well I'm sorry to break it to you, but the size of the Airy disk at f/5.6 is 7.5 microns, therefore any sensor with smaller pixels can be said to be diffraction-limited. If you want to discard the issue of color, and consider just the luminance, then the 2x2 pattern gives you a 12 micron area diameter in which case the system is diffraction-limited at f/11 and smaller. But if you do that you must be willing to admit that the system has only 3 megapixels instead of 12.
You appear to be operating under some definition of diffraction-limited other than "limited by diffraction". Also I would like to point out that 12MP on a 16x24mm sensor is 6 microns, not "less than 6 microns".
If the lens is perfect (which it isn't, but let's assume that) the camera will be diffraction-limited. At a certain aperture, the Airy disk will be larger than the pixels in the sensor. This camera has 6-micron pixels, which is very small indeed. Cameras with this sensor will probably be diffraction-limited at f/5.6 and smaller apertures.
The article doesn't seem to mention whether the new Kodak sensor uses the new-and-perhaps-improved pixel pattern that Kodak announced in 2007. See http://johncompton.pluggedin.kodak.com/default.asp?item=624876
It is important to remember three things: Colin Powell is a lying cocksucker who covered up a war crime in Vietnam. Seymour Hersh is a brilliant journalist who broke the story of that war crime.
Third thing: For almost a year, Seymour Hersh has been writing in the New Yorker about Dick Cheney's preparations for a war, possibly even a nuclear first strike, against Iran.
Fear.
Even Firefox 2 supported this.
Your comment seems to imply that no bittorrent peer will ever need to RST the connection, which is not generally true.
Not just that, but it filters out RST packets that may in fact have been sent by the peer. So this trick can leave you with sockets hanging open in a bad state.
You don't have to do it for the user accounts if you put it in /etc. And you can't call yourself a sysadmin if you don't have already have a way to distribute a file to all your hosts.
Only if you're an idiot who can't read the manual. See /etc/ssh/ssh_known_hosts. You put the new key into known hosts ahead of time, then you change the keys, then you remove the old key from known_hosts. No automated logins will have been broken.
Gmail has the same problem: can't open an email in a new tab. Or, you can, but it also navigates the current tab to the same email.
Note to developers: javascript and ajax are cute, but don't break the browser's native UI.
The point is that with OSP you have bare copper pads. You don't need to put any kind of metal finish on the board at all, certainly not the traditional tin/lead finish. In fact the tin/lead HASL finish is practically useless with fine-pitch QFN parts that are no so popular, because HASL has bad planarity. OSP has the best planarity of any board finish.
The Thunderbird does 0-60 in about 9 or 10 seconds, depending, and a factory stock 2008 Toyota Sienna reaches 60 in 6.6 seconds according to Car and Driver. You're letting some rosy vision of musclecar glory cloud your judgment.
The problem of tin whiskers is real but the consequences ascribed to them by Cringley are not. A printed circuit board like the one in your computer or TV is made of fiberglass and copper layered in a sandwich. In the early days of electronics the copper was plated with tin to prevent corrosion, but scientists discovered that pure tin tends to form hairlike growths, causing the circuits to fail. Adding lead to the tin prevented the growths, and had other desirable properties, so the tin/lead alloy became a universal standard.
More recently we got something called "the restriction of the use of certain hazardous substances in electrical and electronic equipment" or RoHS. RoHS prohibits the sale of materials containing more than 1% lead in the EU. (Old-style electronic assemblies use 37% lead solder.) RoHS came into force in 2006 but research into lead-free electronics began decades ago. Initially researchers tried pure tin plating, which lead to tin whiskers. Some products marketed in the late 90's even failed from this problem. But researchers did not throw up their hands in despair. RoHS has led to innovations in metallurgy to the extent that a circuit board designer can now choose from half a dozen different alloys. Today only 2% of printed circuit boards use tin plating.
Some of these new alloys use gold or silver finishes over copper. These are completely immune to tin whiskers. The most popular new system eliminated the plating step, attaching components directly to the bare copper using chemicals called Organic Solderability Preservatives. OSP leads to stronger and more durable assemblies than even the old tin/lead process.
The whining we see today on the subject of RoHS mirrors almost perfectly the doomsaying seen when California began regulating automobile emissions. There was at that time a tremendous amount of yelling about how the catalytic converter spelled the end of civilization as we know it, and only a moron would take the lead out of gasoline. But soon afterwards we saw the introduction of clean, efficient, powerful cars by Honda. Honda was even able to meet California emissions standards without using catalytic converters or even fuel injection. Their brand of engineering eventually trickled down to even the most benighted American car maker, and California emissions standards are now in force in every industrialized nation.
I would expect to see the same thing with RoHS. We have only just entered the initial stage of complaining. The tin/lead dinosaurs with backwards-looking engineering departments face an existential crisis. In other design houses the challenge of lead-free assembly is being embraced as a competitive advantage. Those who can adapt to RoHS will thrive and those who cannot will clearly suffer.
Cringley brags about a 1966 Thunderbird with a 428 cu. in. motor, a car so heavy, so polluting, and so slow by modern standards that it would be impounded by CARB and laughed off a drag strip by a base model minivan. As time goes on I think Cringley's views on the metallurgy of printed circuit boards will seem as antique at that T-Bird.
This was _always_ a feature in Netscape. It got dropped in the transition from Netscape to Mozilla. It's one of those problems with open source development: there's no guarantee that useful, widely-used features are carried forward into new versions.
Shouldn't the title of this post be "Shitty router programming causing router crashes"? It should matter what type of garbage come off the wire, the router must be able to handle it all without error.
Better brush up on your history. The 1976 Republican primary, between Ford and Reagan, was closer than the current Democratic contest.
Standard operating procedure throughout the cold war. http://en.wikipedia.org/wiki/Farallon_Islands#Nuclear_waste
That's ridiculous. OpenSecrets counts industries by the employers stated by individual contributors. That's a very different thing from contributions from actual corporations (which are mainly made to PACs, not to campaigns).
Yes, but any moron can catch bugs like that one with a simple "rgrep scanf ." and fire the programmers in question. Static analysis not required.