Don't claim it's right, just that it happens. Sometimes it's so blatently stupid it's sad. Sometimes it makes me mad when I see it happen. But that doesn't change the reality that people do stupid things and try to blame others for it.
Damn. It's almost like you planned it... I'm certain S&W has been sued over use of their guns. Volvo... Look up European regulations requiring manufacturers to make their cars and trucks safer to pedestrians. Jack Daniels has been sued by the families of alcoholics. So, apparently, people do blame the vendor for irresponsible use of their products even if it is outside of the vendor's control or the intended use of the product.
I received the notification and I opted out. Why? Because this does not benefit the customers. It only benefits the lawyers who filed the class action suit. Ultimately it hurts the customer because it will cause TicketMaster et. al. to raise prices.
Right. It was just a "damn, it's been that long?" as I, for a moment, reflected back on my life... Anyway, Intel was first. It was a good idea and AMD customers were losing chips so they added it too. It showed up first in socket A K7 architecture chips. Not sure which generation... but a quick google search indicates it was the 3rd gen Athlon XP in late 2001 or early 2002 that first implemented the thermal diode and MB based protection circuit. I was always concerned about killing my maximally overclocked Duron. Ironically, it was the northbridge that eventually failed.
That problem only affected earlier chips with inadequate cooling. The stock cooler was inadequate as they made certain assumptions with regard to "typical" usage. They fixed this long ago (it's been a decade?) by adding temp sensors and automatic clock throttling.
All true; but, they're down to 9% ownership and according to the articles no longer have rights to appoint someone to the GloFlo board. Looks like the relationship is becoming increasingly sour.
On the desktop, it's more like 89%; but, yes most people run Windows on the desktop. AMD is making a radical change to their architecture moving forward. They had to know they were going to take a hit initially.
Toms Hardware and Tech Report have also discussed and tested this theory. They found the current Windows scheduler does not use the hardware correctly. AMD has whitepapers available explaining the issue and the changes requried for the scheduler(s). Microsoft is working to make the changes as is the Linux kernel team.
Tech Report demonstrated this to be the case by setting the thread affinity on their tests, so they were locked to specific cores, using only once core per module. They saw as much as a 30% improvement in the single threaded or lightly threaded benchmarks. Other sources, including AMD itself, have demonstrated as much as 10% improvement in performance by using a better thread scheduler. AMD has whitepapers discussing this issue.
As for changing the OS kernels... Windows 8 already has the changes. Windows 7 and Server 2008 may get them in a future update (Service Pack?). Linux kernel support is ready and is available in a kernel patch. Compiler support is now included in VS 2010. So, not necessarily a flop; but, might be a short while before the full capability of the architecture is realized.
Windows does not (yet) know how to properly schedule threads on that hardware. This has caused issues with all the benchmarks, not unlike what happened when Intel Hyperthreading was first released. Once the proper support is added to the OS kernels, the results should be much better.
Still running a cluster of HP PA-RISC here. And it's running business critical code. So, yes, some customers plan to continue to use old systems. They may not have planned it that way when the origin decision was made; but, with a decade or more of momentum, it can be very hard to change.
Because as soon as you do, as soon as you think you're fully secure, Grandma will bypass the security using the Administrator password to install some new program on her computer that she downloaded and thinks she needs... Then all Grandma's base belong to a hacker. You need a virus scanner in the background to babysit the system and stop this stuff, after the fact.
My phone gets replaced when it breaks -- current phone is less than a year old but had last one 3 1/2 years. My primary home computer is 5 years old. My laptop is 3 years old. I expect to get another year or two out of them. I am still using a SD TV, a CRT. I don't plan to replace it until it becomes necessary. Why scrap a functional piece of hardware?
I'll be happy if we have something that lets us mere Humans putter about in the inner solar system (Jupiter and sunward) within the next 100 years. Interstellar is just wishfull thinking...
Somewhere there's a plant that makes the internals for all the expensive printers too. I worked on a line that alternately spit out HP and some other brand(s) of laser printers, depending on the sales orders. Differences were in the outer housing and the pcb, mostly.
While I respect your contribution to the space program, you're wrong. Specifically, with respect to the Space Shuttle, it is too late. They've been pulled out of service, stripped of flight hardware, and decomissioned. Contracts have been cancelled. Staff has been layed off. Necessary support infrastructure and hardware has been mothballed. It's done.
In addition, required airframe inspections were postponed in order to complete the final missions by the deadline. So, even if we were to renew all the contracts, re-hire all the staff, and pull the ground support harddware out of mothballs, a recertification of all three airframes would be required. This takes time; and, for the duration of the recertification process we would have no launch vehicles. Given that we did not have facilities to do more than one full tear down and inspection at a time, (or have not had the capability for a considerable period of time), the recertification would be drawn out until at least two airframes were inspected, sequentially -- flight rules require a second shuttle be available on standby in the event of an on-orbit accident.
No, Mr. Cernan. As embarrassing as it is to have no capability, returning the Shuttle to flight, now, is not the option. Our best option for NASA designed hardware is a return to flight leveraging proven components and technology, in the form of the SLS (or whatever you choose to call it) If you want it sooner, get it funded faster. And although your past arguments make it clear you find commercial options distastefully, I feel you should review your decision. One option is the ULA Atlas V+ Boeing CST-100. Another option is to use the Lockheed Orion on either ULA vehicles (Atlas or Delta) As these contractors are the people who built and maintained the Shuttle, they're already intimately familiar with the manned space flight requirements. Frankly, they're likely to be ready before SLS.
Finally, You should not be so quick to dismiss alternatives such as SpaceX. Yes, it is rocket science. Yes, these are the "new kids on the block", upstarts some may call them. Consider that SpaceX is hiring many experienced people from both NASA contractors and NASA itself. Consider that the work being done by SpaceX is under contract to NASA and the Air Force, and is under constant review by NASA and Air Force personnel. Consider that their designs, while new, are based on existing works. They may be the "new kid on the block" but they are clearly leveraging the industries 5 decades of experience.
Netgear makes enterprise grade equipment -- we have Netgear equipment all through our manufacturing facility and IT center. having said that... We used Xirrus wifi hwardware and it works quite well.
Slashdot Mirror
Don't claim it's right, just that it happens. Sometimes it's so blatently stupid it's sad. Sometimes it makes me mad when I see it happen. But that doesn't change the reality that people do stupid things and try to blame others for it.
But won't Martian drywall cause corrosion of all the electrical and plumbing systems? Mars is rust red after all...
Damn. It's almost like you planned it... I'm certain S&W has been sued over use of their guns. Volvo... Look up European regulations requiring manufacturers to make their cars and trucks safer to pedestrians. Jack Daniels has been sued by the families of alcoholics. So, apparently, people do blame the vendor for irresponsible use of their products even if it is outside of the vendor's control or the intended use of the product.
I received the notification and I opted out. Why? Because this does not benefit the customers. It only benefits the lawyers who filed the class action suit. Ultimately it hurts the customer because it will cause TicketMaster et. al. to raise prices.
Right. It was just a "damn, it's been that long?" as I, for a moment, reflected back on my life... Anyway, Intel was first. It was a good idea and AMD customers were losing chips so they added it too. It showed up first in socket A K7 architecture chips. Not sure which generation... but a quick google search indicates it was the 3rd gen Athlon XP in late 2001 or early 2002 that first implemented the thermal diode and MB based protection circuit. I was always concerned about killing my maximally overclocked Duron. Ironically, it was the northbridge that eventually failed.
That problem only affected earlier chips with inadequate cooling. The stock cooler was inadequate as they made certain assumptions with regard to "typical" usage. They fixed this long ago (it's been a decade?) by adding temp sensors and automatic clock throttling.
I wonder if they held any bits back?
Of course they did...
All true; but, they're down to 9% ownership and according to the articles no longer have rights to appoint someone to the GloFlo board. Looks like the relationship is becoming increasingly sour.
On the desktop, it's more like 89%; but, yes most people run Windows on the desktop. AMD is making a radical change to their architecture moving forward. They had to know they were going to take a hit initially.
Toms Hardware and Tech Report have also discussed and tested this theory. They found the current Windows scheduler does not use the hardware correctly. AMD has whitepapers available explaining the issue and the changes requried for the scheduler(s). Microsoft is working to make the changes as is the Linux kernel team.
Tech Report demonstrated this to be the case by setting the thread affinity on their tests, so they were locked to specific cores, using only once core per module. They saw as much as a 30% improvement in the single threaded or lightly threaded benchmarks. Other sources, including AMD itself, have demonstrated as much as 10% improvement in performance by using a better thread scheduler. AMD has whitepapers discussing this issue.
As for changing the OS kernels... Windows 8 already has the changes. Windows 7 and Server 2008 may get them in a future update (Service Pack?). Linux kernel support is ready and is available in a kernel patch. Compiler support is now included in VS 2010. So, not necessarily a flop; but, might be a short while before the full capability of the architecture is realized.
Windows does not (yet) know how to properly schedule threads on that hardware. This has caused issues with all the benchmarks, not unlike what happened when Intel Hyperthreading was first released. Once the proper support is added to the OS kernels, the results should be much better.
That's how I read the other reviews as well. It seems like a fairly good chip for servers or workstations.
Still running a cluster of HP PA-RISC here. And it's running business critical code. So, yes, some customers plan to continue to use old systems. They may not have planned it that way when the origin decision was made; but, with a decade or more of momentum, it can be very hard to change.
Because as soon as you do, as soon as you think you're fully secure, Grandma will bypass the security using the Administrator password to install some new program on her computer that she downloaded and thinks she needs... Then all Grandma's base belong to a hacker. You need a virus scanner in the background to babysit the system and stop this stuff, after the fact.
We're not all conspicuous consumers.
My phone gets replaced when it breaks -- current phone is less than a year old but had last one 3 1/2 years.
My primary home computer is 5 years old. My laptop is 3 years old. I expect to get another year or two out of them.
I am still using a SD TV, a CRT. I don't plan to replace it until it becomes necessary. Why scrap a functional piece of hardware?
I'll be happy if we have something that lets us mere Humans putter about in the inner solar system (Jupiter and sunward) within the next 100 years. Interstellar is just wishfull thinking...
Somewhere there's a plant that makes the internals for all the expensive printers too. I worked on a line that alternately spit out HP and some other brand(s) of laser printers, depending on the sales orders. Differences were in the outer housing and the pcb, mostly.
Throw your sabot at the computer
Dear Mr. Cernan,
While I respect your contribution to the space program, you're wrong. Specifically, with respect to the Space Shuttle, it is too late. They've been pulled out of service, stripped of flight hardware, and decomissioned. Contracts have been cancelled. Staff has been layed off. Necessary support infrastructure and hardware has been mothballed. It's done.
In addition, required airframe inspections were postponed in order to complete the final missions by the deadline. So, even if we were to renew all the contracts, re-hire all the staff, and pull the ground support harddware out of mothballs, a recertification of all three airframes would be required. This takes time; and, for the duration of the recertification process we would have no launch vehicles. Given that we did not have facilities to do more than one full tear down and inspection at a time, (or have not had the capability for a considerable period of time), the recertification would be drawn out until at least two airframes were inspected, sequentially -- flight rules require a second shuttle be available on standby in the event of an on-orbit accident.
No, Mr. Cernan. As embarrassing as it is to have no capability, returning the Shuttle to flight, now, is not the option. Our best option for NASA designed hardware is a return to flight leveraging proven components and technology, in the form of the SLS (or whatever you choose to call it) If you want it sooner, get it funded faster. And although your past arguments make it clear you find commercial options distastefully, I feel you should review your decision. One option is the ULA Atlas V+ Boeing CST-100. Another option is to use the Lockheed Orion on either ULA vehicles (Atlas or Delta) As these contractors are the people who built and maintained the Shuttle, they're already intimately familiar with the manned space flight requirements. Frankly, they're likely to be ready before SLS.
Finally, You should not be so quick to dismiss alternatives such as SpaceX. Yes, it is rocket science. Yes, these are the "new kids on the block", upstarts some may call them. Consider that SpaceX is hiring many experienced people from both NASA contractors and NASA itself. Consider that the work being done by SpaceX is under contract to NASA and the Air Force, and is under constant review by NASA and Air Force personnel. Consider that their designs, while new, are based on existing works. They may be the "new kid on the block" but they are clearly leveraging the industries 5 decades of experience.
There is probably management software, educational apps, and e-books included in that price
You must not be familiar with the kindergartner animal and the damage they can do.
Netgear makes enterprise grade equipment -- we have Netgear equipment all through our manufacturing facility and IT center. having said that... We used Xirrus wifi hwardware and it works quite well.
Big scary chickens. I feel there should be an obligatory XKCD raptor reference here; but, I can't decide which one to post.
If you don't require net energy production, it works now.