Not true for the latest generation of Plasma TVs. Take a look at the 42" models from Panasonic.
Typical values (from zdnet reviews): # Microdisplay rear projector: 0.11 to 0.15 watt per square inch # LCD: 0.16 to 0.41 watt per square inch # CRT: 0.25 to 0.40 watt per square inch # Plasma: 0.30 to 0.39 watt per square inch
Do you mean burn in? True enough if you let this happen.
60,000 hour run life is pretty long for a TV. By then you will want the latest and greatest anyway. At the rate that I watch TV that is like 30 years.
Have you ever priced out larger sets? Plasma becomes cheaper over 32". Also the picture quality can be much better with truer blacks and better contrast.
BTW, ISDN is not dead and is not a in-between solution, it is a good for what it was designed for - mid-haul, moderate speed, digital comms. We use 300 ISDN-BRIs for backup circuits, they are cheap and reliable.
I was on the fence but after seeing the displays first hand at a shop, it was clear that plasma was for me. Try watching anything in a lit room (daylight or overheads), it can be a real struggle with an LCD. No problem on my plasma.
Even with the reflective glass on the Plasma, I find it easier than an LCD.
Admittedly I do not play console games on it and have to be diligent not to pause for too long for fear of burn in but who cares.
I have also had an LCD TV (much smaller however) and was pretty happy with it. It did have some dead pixels and watching dark movies was distracting since black was not quite black enough for my taste.
Don't get me wrong, I think each one has it's applications. My brother has the Aquos in his bedroom and it's really nice, but then again usually it is dark out when they are watching so no problems with that.
The power and heat issues are bad arguments. The power consumption is close enough (300 max for my plasma vs. 250 sustained for the comparable LCD, which is almost twice the price) to be ignored in most cases, and hopefully you are not that close to your 42" plasma that the heat is a concern...
I understand the problem as I am in the same boat. OP is probably using some addresses from each class of 1918 addresses.
Using a text file or wiki is not an elegant solution when managing 3000+ hosts where 50% of them are static (for various reasons). I've been using an Access database but I am currently developing a PHP/Postgresql based solution. We have 20+ support staff signing out new addresses every day. The napkin approach sucks and conflicts and mistakes are aplenty...
Switch fabric forwarding capacity is usually measured in pps not bps. They are cut-through and the size of the packet in general shouldn't matter. This is true for copy-once type switches (i.e. Nortel 8600). where the packet destination is determined and copied to the output queue only once. Some switches don't do this and packet size comes into play much more. Our switches can do 7 billion pps on the backplane, which means they top out at 10 GBps (GigaBytes ps). Compare that to a legacy router than can do 250 Mbps on the backplane (not to mention the huge forwarding latency).
Also, the backplane does not need to scale linearly, a subscription ratio is used to determine the backplane requirements.
I had considered your approach to limit client speeds but found that 10-full did not play nice with most auto-neg cards. Instead we rely on higher end PCI busses and 1000Mbps Cu interfaces for the servers. Never had a problem with SF being a bottleneck.
SS# were not intended to be a secure ID number to be kept confidential. This is a complete fabrication of credit agencies and the like.
The intent is to provide a unique ID number for the social security system. In many state databases (NYS employees) this ID number is freely available (along with your salary).
To help keep yourself out of the "identity theft" arena, opt-out of instant credit. This is advisable for everyone, alas no more discounts at the GAP for opening a credit card...
IANAMR but my wife is a resident and on a light month works just under 80 hours a week. On the books she always comes in under the legally required (finally) 80 hours a week.
Keep in mind she must go in two hours early to pre-round on the patients so that when she present the patients to the attendings on rounds she knows what she is talking about. And that she must finish all cases that are in progress and do follow up phone calls as well as dictate notes that has her leaving four hours later than scheduled.
On a tough rotation she works 4 AM to 9 PM six days a week. That is more than 100 hours in a week!!
I think this is ridiculous and absurd and all that but the hospital obviously feels that this type of slave labor is justified because the costs of lost revenue due to malpractice, etc does not exceed the cost of adding more residents.
And you thought 80 hours of programming were bad: try standing in surgery for six cases in a row for a total of eight hours with no breaks for food or excrement!
I will admit that I have had a few problems with Firefox on my Thinkpad.
But all and all it is a fast, stable browser with great features. I am in the process of moving my main desktop PC at home to Linux and Firefox runs great. My biggest problem is finding a replacement for RealPlayer 10 (the Jukebox features), right now I am looking at Madman.
This is going to be the hardest part. Even decent commercial web apps (i.e. Novel WebAccess) are horribly coded, taking advantages of features that are either proprietary or bugs in IE.
If you run them through an HTML validator they almost always have ridiclous and basic errors. mail.optonline.net is horrible, most of the buttons do not work because of javascript errors.
Luckily Mozilla handles a lot of these errors gracefully and Firefox is getting better. But like you said, it comes down to the webmasters and web application (commercial) developers getting on board and writing proper HTML & javascript.
Yes. But now it is easier for me to go to my boss and recommend we move all browsers to Mozilla. He used to think Internet Explorer == Internet. I have shown him the way.
At my company, ticket agents were complaining that they were losing jobs to the automated ticket vending machines until they realized that the jobs that service the machines pay twice as much and they don't need to deal with customers. There are so many machines plus office machines (that require an agent) that there is a net loss of 0 jobs.
In a corporate environ no justification is needed. The company is protecting their resources and thus can do whatever they deem necessary.
When I went to college (grad in 97) it was a free-for-all. Something akin to the wild west. A half way intelligent person could gather clear text passwords (it is fun using other peoples accounts) and it was better than Kazaa for grabbing progs off of peoples file shares.
My university had a great collection of pr0n newgroups - in the interest of research of course!!
I agree that some applications are better off with Postgres but a half way decent abstraction layer and portable queries go a long way.
I've changed some of my concurrent update intensive applications to a postgres back-end very easily.
Slashdot Mirror
Where I live (NY), generally it is called "chopped meat" and specifically ground beef, ground pork, etc.
And it is made exactly as you describe it.
Not true for the latest generation of Plasma TVs. Take a look at the 42" models from Panasonic.
- th42pwd8uk.php
Typical values (from zdnet reviews):
# Microdisplay rear projector: 0.11 to 0.15 watt per square inch
# LCD: 0.16 to 0.41 watt per square inch
# CRT: 0.25 to 0.40 watt per square inch
# Plasma: 0.30 to 0.39 watt per square inch
The low end of the LCD is from tiny displays.
My 42" plasma has a max power consumpition of 275 watts. http://www.dtvcity.com/panasonic-plasma/panasonic
Do you mean burn in? True enough if you let this happen. 60,000 hour run life is pretty long for a TV. By then you will want the latest and greatest anyway. At the rate that I watch TV that is like 30 years.
Have you ever priced out larger sets? Plasma becomes cheaper over 32". Also the picture quality can be much better with truer blacks and better contrast. BTW, ISDN is not dead and is not a in-between solution, it is a good for what it was designed for - mid-haul, moderate speed, digital comms. We use 300 ISDN-BRIs for backup circuits, they are cheap and reliable.
But have you owned and used a Plasma TV as well?
I was on the fence but after seeing the displays first hand at a shop, it was clear that plasma was for me. Try watching anything in a lit room (daylight or overheads), it can be a real struggle with an LCD. No problem on my plasma.
Even with the reflective glass on the Plasma, I find it easier than an LCD.
Admittedly I do not play console games on it and have to be diligent not to pause for too long for fear of burn in but who cares.
I have also had an LCD TV (much smaller however) and was pretty happy with it. It did have some dead pixels and watching dark movies was distracting since black was not quite black enough for my taste.
Don't get me wrong, I think each one has it's applications. My brother has the Aquos in his bedroom and it's really nice, but then again usually it is dark out when they are watching so no problems with that.
The power and heat issues are bad arguments. The power consumption is close enough (300 max for my plasma vs. 250 sustained for the comparable LCD, which is almost twice the price) to be ignored in most cases, and hopefully you are not that close to your 42" plasma that the heat is a concern...
I understand the problem as I am in the same boat. OP is probably using some addresses from each class of 1918 addresses. Using a text file or wiki is not an elegant solution when managing 3000+ hosts where 50% of them are static (for various reasons). I've been using an Access database but I am currently developing a PHP/Postgresql based solution. We have 20+ support staff signing out new addresses every day. The napkin approach sucks and conflicts and mistakes are aplenty...
Switch fabric forwarding capacity is usually measured in pps not bps. They are cut-through and the size of the packet in general shouldn't matter. This is true for copy-once type switches (i.e. Nortel 8600). where the packet destination is determined and copied to the output queue only once. Some switches don't do this and packet size comes into play much more. Our switches can do 7 billion pps on the backplane, which means they top out at 10 GBps (GigaBytes ps). Compare that to a legacy router than can do 250 Mbps on the backplane (not to mention the huge forwarding latency).
Also, the backplane does not need to scale linearly, a subscription ratio is used to determine the backplane requirements.
I had considered your approach to limit client speeds but found that 10-full did not play nice with most auto-neg cards. Instead we rely on higher end PCI busses and 1000Mbps Cu interfaces for the servers. Never had a problem with SF being a bottleneck.
Who modded this Troll?? Should be funny, RTFA.
Not broken, no longer appropriate...
SS# were not intended to be a secure ID number to be kept confidential. This is a complete fabrication of credit agencies and the like.
The intent is to provide a unique ID number for the social security system. In many state databases (NYS employees) this ID number is freely available (along with your salary).
To help keep yourself out of the "identity theft" arena, opt-out of instant credit. This is advisable for everyone, alas no more discounts at the GAP for opening a credit card...
IANAMR but my wife is a resident and on a light month works just under 80 hours a week. On the books she always comes in under the legally required (finally) 80 hours a week.
Keep in mind she must go in two hours early to pre-round on the patients so that when she present the patients to the attendings on rounds she knows what she is talking about. And that she must finish all cases that are in progress and do follow up phone calls as well as dictate notes that has her leaving four hours later than scheduled.
On a tough rotation she works 4 AM to 9 PM six days a week. That is more than 100 hours in a week!!
I think this is ridiculous and absurd and all that but the hospital obviously feels that this type of slave labor is justified because the costs of lost revenue due to malpractice, etc does not exceed the cost of adding more residents.
And you thought 80 hours of programming were bad: try standing in surgery for six cases in a row for a total of eight hours with no breaks for food or excrement!
I will admit that I have had a few problems with Firefox on my Thinkpad. But all and all it is a fast, stable browser with great features. I am in the process of moving my main desktop PC at home to Linux and Firefox runs great. My biggest problem is finding a replacement for RealPlayer 10 (the Jukebox features), right now I am looking at Madman.
This is going to be the hardest part. Even decent commercial web apps (i.e. Novel WebAccess) are horribly coded, taking advantages of features that are either proprietary or bugs in IE.
If you run them through an HTML validator they almost always have ridiclous and basic errors. mail.optonline.net is horrible, most of the buttons do not work because of javascript errors.
Luckily Mozilla handles a lot of these errors gracefully and Firefox is getting better. But like you said, it comes down to the webmasters and web application (commercial) developers getting on board and writing proper HTML & javascript.
Yes. But now it is easier for me to go to my boss and recommend we move all browsers to Mozilla. He used to think Internet Explorer == Internet. I have shown him the way.
This is typical of technology isn't it?
At my company, ticket agents were complaining that they were losing jobs to the automated ticket vending machines until they realized that the jobs that service the machines pay twice as much and they don't need to deal with customers. There are so many machines plus office machines (that require an agent) that there is a net loss of 0 jobs.
In a corporate environ no justification is needed. The company is protecting their resources and thus can do whatever they deem necessary.
When I went to college (grad in 97) it was a free-for-all. Something akin to the wild west. A half way intelligent person could gather clear text passwords (it is fun using other peoples accounts) and it was better than Kazaa for grabbing progs off of peoples file shares.
My university had a great collection of pr0n newgroups - in the interest of research of course!!
My f**kin 'i' key is broken so...
I agree that some applications are better off with Postgres but a half way decent abstraction layer and portable queries go a long way. I've changed some of my concurrent update intensive applications to a postgres back-end very easily.