2) Are you sure about that? I get a terrible case of "white stripes" when reading white text on a dark background because of the memory effect of the eyes.
From what I know about LCD technology, the driver puts out variable power to each pixel in order to get it to a certain brightness level. Full power to make it completely opaque, zero power to make it completely transparent. So in theory, a completely white screen should use less power. However, I imagine that even a completely white screen is requiring the driver to put out some power to the pixels in order to maintain some kind of white balance. So the circuitry that varies the power level to the pixels must tend to be more inefficient when it is distributing the least power. Maybe it is a switching power supply that has to switch at a higher rate to "throttle" the power output.
Maybe they are designed that way on purpose to keep power draw more or less consistent? If this theory is right, then it goes basically like this: 1% power to pixels, 90% power to control circuitry, all the way up to 90% power to pixels, 10% power to control circuit, with the net varying between 91% and 100%. If they designed it the other way around, it would be 1% and 10%, all the way up to 90% and 10%, with a net power varying between 11% and 100%.
No, the hard drive is storage. It's pretty basic computing 101. If you need an analogy, consider an office desk. The surface of the desk is a computer's memory, the drawers are the storage.
I'm sure there is a communications law of some kind that says when you double the number of connections, you quadruple (or something) the network complexity.
If the UK were a US state, it would only be the 12th biggest state. It is smaller than Michigan. Yet there are 62 million people there, nearly double the # of people in the most populous state. That's a lot of people to spread the costs of installing a new network over. I'm sure the same applies in much of Europe.
I wonder if they have thought about using an asymmetric network- use the near-field wireless for device -> network transmit, and use a completely different system for network -> device "broadcasts".
The problem is, fast wireless for everyone is a dead end. It would be nearly as expensive as wired connections because they would need to have radio cells every couple hundred feet. And still suck worse than a wired connection.
There is enough capacity for the early adopters to do it. Just enough to make it seem like a good idea. Then people start doing it more commonly and capacity shits out.
So? If standing up for your principles isn't worth anything to you, then don't bother. But if it is, then make the stand. If they fire you, good for you. Unemployment insurance and probably a better job further down the road.
Probably. There are a lot of POS software vendors that will tell you that you can just run their website in fullscreen on a PC with a touchscreen and call it a POS.
Yeah, the real IBM printer spinoff was Lexmark. InfoPrint units were just rebadged Lexmarks. (And the larger ones were rebadged something else.)
I'm not a fan of Lexmarks either, but having a printer fixer guy for the last many years, I think they are better designed than HP units of the same era. Lexmarks are more cheaply made (I've had brand new ones jam right out of the box because plastic casting "hunks" were left in the paper path), but HP printers are just monstrosities. Over engineered and under specced. Whole lines of machines plagued with bad plastic bearings and control boards that go tits up after 1-2 years. Plastic gears that wear out. Little fiddly springs everywhere. One thing Lexmark did really well was their autocompensator pickup arm. Those things work great, no silly separation pads or separation rollers.
I can see where I might have the same reaction. You are dozing, you start to drift toward consciousness and begin hearing the radio patter about a C-17 being ahead. You open your eyes and see what appears to be headlights and react instinctively.
While driving at night, I've certainly been fooled by two motorcycles' headlights into believing it was a car that was nearer or farther than the actual motorcycles.
What I really don't like is the whole sleeping in the cockpit game. If it is legal, it shouldn't be.
Simple solution: your policy is that you don't work when you aren't getting paid. You want me to work overtime? Compensate me. Either with money or some other thing that's valuable to both of us.
I would imagine another outcome- efficiency would improve. If a company has after hour needs, then they should plan and staff for it. Otherwise, nobody should be working. If you don't have people feeling the need to burn the midnight oil, then you don't need to support them all the time. If a server goes down in the middle of the night, nobody needs to get woke up to fix it, because nobody needs it until the morning.
Where I work, there are two of us who do the same kind of job, with generally the same workload. I am definitely a "work from 9-5, leave me alone the rest of the time" guy. He is more of a chaotic kind of person. He is constantly bitching about his work stacking up and having to work late hours to catch up. I'll get a frantic call from him because he needs help with something, and then as I am working on that, I'll get cc's from my boss approving vacation requests. Jesus, man, if you'd just work instead of planning your vacation, we wouldn't be in this situation! I'll also get passive aggressive digs because I "have nothing to do" because by backlog queue is light or empty, while his is full. First, dude, quit wasting time looking at other people's problems and stick to your own. Secondly, how about looking at completed work instead of uncompleted work.
But you may see signs of problems leading up to fraud. When people start getting into a hole of some kind, they start getting sloppy. You might not catch the dispassionate embezzler, but you might catch the addict looking to feed the addiction.
If there ever was a war with China, it would probably be lost by the US's unwillingness to create mass casualties. We'd have to kill hundreds of millions, and the only way that would be acceptable was if it was an all-out invasion-and-enslave type of war.
Part of the point of ipv6 is that technicians won't have to remember addresses at all. It works basically like having a well configured DHCP and DNS server on ipv4. IPv6 just forces that on you. I think.
Slashdot Mirror
1) Common sense says no, but the data says yes.
2) Are you sure about that? I get a terrible case of "white stripes" when reading white text on a dark background because of the memory effect of the eyes.
From what I know about LCD technology, the driver puts out variable power to each pixel in order to get it to a certain brightness level. Full power to make it completely opaque, zero power to make it completely transparent. So in theory, a completely white screen should use less power. However, I imagine that even a completely white screen is requiring the driver to put out some power to the pixels in order to maintain some kind of white balance. So the circuitry that varies the power level to the pixels must tend to be more inefficient when it is distributing the least power. Maybe it is a switching power supply that has to switch at a higher rate to "throttle" the power output.
Maybe they are designed that way on purpose to keep power draw more or less consistent? If this theory is right, then it goes basically like this: 1% power to pixels, 90% power to control circuitry, all the way up to 90% power to pixels, 10% power to control circuit, with the net varying between 91% and 100%. If they designed it the other way around, it would be 1% and 10%, all the way up to 90% and 10%, with a net power varying between 11% and 100%.
No, the hard drive is storage. It's pretty basic computing 101. If you need an analogy, consider an office desk. The surface of the desk is a computer's memory, the drawers are the storage.
I would be surprised if they weren't running some kind of GPOS. I just assumed they were running some kind of Linux.
I'm sure there is a communications law of some kind that says when you double the number of connections, you quadruple (or something) the network complexity.
If the UK were a US state, it would only be the 12th biggest state. It is smaller than Michigan. Yet there are 62 million people there, nearly double the # of people in the most populous state. That's a lot of people to spread the costs of installing a new network over. I'm sure the same applies in much of Europe.
I wonder if they have thought about using an asymmetric network- use the near-field wireless for device -> network transmit, and use a completely different system for network -> device "broadcasts".
The problem is, fast wireless for everyone is a dead end. It would be nearly as expensive as wired connections because they would need to have radio cells every couple hundred feet. And still suck worse than a wired connection.
There is enough capacity for the early adopters to do it. Just enough to make it seem like a good idea. Then people start doing it more commonly and capacity shits out.
It's only random the first time you use it.
If it is a long haul where they need to sleep, then it should be done in separate crew quarters. Or have two crews scheduled.
Not unless you specifically tell them to use the full 15xx bytes. Otherwise, they default to 32 or 64 bytes.
So? If standing up for your principles isn't worth anything to you, then don't bother. But if it is, then make the stand. If they fire you, good for you. Unemployment insurance and probably a better job further down the road.
Probably. There are a lot of POS software vendors that will tell you that you can just run their website in fullscreen on a PC with a touchscreen and call it a POS.
I believe it was the same for Lenovo- they were the OEMs for IBM.
Yeah, the real IBM printer spinoff was Lexmark. InfoPrint units were just rebadged Lexmarks. (And the larger ones were rebadged something else.)
I'm not a fan of Lexmarks either, but having a printer fixer guy for the last many years, I think they are better designed than HP units of the same era. Lexmarks are more cheaply made (I've had brand new ones jam right out of the box because plastic casting "hunks" were left in the paper path), but HP printers are just monstrosities. Over engineered and under specced. Whole lines of machines plagued with bad plastic bearings and control boards that go tits up after 1-2 years. Plastic gears that wear out. Little fiddly springs everywhere. One thing Lexmark did really well was their autocompensator pickup arm. Those things work great, no silly separation pads or separation rollers.
That would definitely be a different kind of pitch excursion.
I can see where I might have the same reaction. You are dozing, you start to drift toward consciousness and begin hearing the radio patter about a C-17 being ahead. You open your eyes and see what appears to be headlights and react instinctively.
While driving at night, I've certainly been fooled by two motorcycles' headlights into believing it was a car that was nearer or farther than the actual motorcycles.
What I really don't like is the whole sleeping in the cockpit game. If it is legal, it shouldn't be.
The point isn't the formal language, but the change in language over time.
Simple solution: your policy is that you don't work when you aren't getting paid. You want me to work overtime? Compensate me. Either with money or some other thing that's valuable to both of us.
I would imagine another outcome- efficiency would improve. If a company has after hour needs, then they should plan and staff for it. Otherwise, nobody should be working. If you don't have people feeling the need to burn the midnight oil, then you don't need to support them all the time. If a server goes down in the middle of the night, nobody needs to get woke up to fix it, because nobody needs it until the morning.
Where I work, there are two of us who do the same kind of job, with generally the same workload. I am definitely a "work from 9-5, leave me alone the rest of the time" guy. He is more of a chaotic kind of person. He is constantly bitching about his work stacking up and having to work late hours to catch up. I'll get a frantic call from him because he needs help with something, and then as I am working on that, I'll get cc's from my boss approving vacation requests. Jesus, man, if you'd just work instead of planning your vacation, we wouldn't be in this situation! I'll also get passive aggressive digs because I "have nothing to do" because by backlog queue is light or empty, while his is full. First, dude, quit wasting time looking at other people's problems and stick to your own. Secondly, how about looking at completed work instead of uncompleted work.
Yes, this is it exactly. Sometimes people just go haywire for no reason.
But you may see signs of problems leading up to fraud. When people start getting into a hole of some kind, they start getting sloppy. You might not catch the dispassionate embezzler, but you might catch the addict looking to feed the addiction.
If there ever was a war with China, it would probably be lost by the US's unwillingness to create mass casualties. We'd have to kill hundreds of millions, and the only way that would be acceptable was if it was an all-out invasion-and-enslave type of war.
A good solution: http://www.youtube.com/watch?v=fbITzCI2AU0
Part of the point of ipv6 is that technicians won't have to remember addresses at all. It works basically like having a well configured DHCP and DNS server on ipv4. IPv6 just forces that on you. I think.