Not all predators.
Listened to an interview with a "wildlife management officer" in India. He talked about how once a big cat gets a taste of human, nothing else will suffice. The salt content in the blood is what causes the problems. This leads to big cats that prey on humans exclusively - a problem for some. The tell-tale sign is when you have a small village where every month or so, someone goes missing.
While Linux being free helped Linux displace Sun, SGI, Digital Unix, HPUX, IBM
Being free had nothing to do with displacing the other big UNIX vendors. When you invest so much money in hardware the cost of a well supported OS is nothing. Linux has displaced these operating systems for a few reasons. First, Linux is now good enough and has most of the features users require. Second, it detaches the user from any one vendor thereby greatly reducing the cost of new hardware. Third, the increased popularity of Linux on standard desktop hardware has produced many users that are more comfortable / productive with the OS.
There are probably other reasons as well, but nobody running a system that costs 6 figures gives a damn about the OS cost.
Brown is not what you want. They are similar to the "blue" keys but with less noise - I actually own both. There is still a significant distance the key must travel (up then down) to register sequential keystrokes. What you really want are the "red" keys. These keys require only a minimal amount of travel and do not have a noticeable "click" when activated. A pain for typists but it allows gamers to press keys at a very high frequency. The "black" keys are similar but require ~50% more force so they're a bit slower.
But all mechanical keyboards are great at minimizing latency - it is because of the differences between switches and capacitors. The chiclet keyboards work my altering observed capacitance - this requires a controller to continuously scan for key changes and then send the appropriate signals to the host. This takes time and results in the latency the original poster was talking about. Mechanical keyboards are simple switches and are faster to scan. I imagine some mechanical keyboards are even interrupt driven resulting in latency measured in microseconds -- but changes in capacitance can't trigger interrupts.
It seems like hybrids would benefit from a gps and software, so it can know my routine, and whether or not a low battery should be charged by running the engine (I'm at the start of a long trip), or not (I'm about to pull into my driveway and plug in).
Along those sames lines, I always thought using GPS to track the location and power requirements along any given road could help with automatic transmissions. One really notices the problem when driving up inclines. Espically with lower powered cars, the automatic transmission should know to not change gear all the time. For this to happen the transmission needs to know future power requirements - something that could be obtained via GPS and past driving history.
Contrary to what you might think, your car should ALWAYS be charged by running the engine unless you happen to be on wind, nuke or hydro power.
But people get their power from the power grid. Every joule of energy you leave in the grid by using your internal compustion engine results in a joule of energy that doesn't have to be generated. But the generation plants that shut down due to relaxed supply are not those burn coal. Coal is cheap so power producers use coal first when possible. It's the oil and natural gas plants that will slow down when demand drops.
Buring gas in an internal compustion engine is less efficient then either oil or natural gas so it is best to use electricity if available. And if you are worried about the environmental impact of generating power, be sure to support environmental tarrifs/taxes on any new coal based facilities - like that will ever happen.
This will also probably also be good for FreeBSD in terms of its codebase as well. I expect Sony will probably be feeding back some patches.
This man is in denial.
Not really. It is much less expensive to allow the patches to be integrated into the parent project then it is to patch the project after every update. In addition, others will be able to test/verify that changes don't break the patches if they are given access to them. So it makes sense to feed back as many patches as they can as it greatly reduces the effort required to maintain their port.
LED PWM frequencies are FAR higher than the old CRT refresh rates.
That's not the problem here. The flicker that is being observed is not the refresh rate of the LEDs but the refresh rate of the LEDs when masked by the refresh rate of the LCD.
Try looking at a video recording of a CRT screen. The refresh rate of the CRT is plenty fast but, when sampled at the sampleing rate of the video recorder, visual artifacts are introduced. This is why newsrooms always synchronize the CRTs visible from the camera from a single source.
What the original poster described is likely an artifact of the LED and LCD hardware not being designed to work together. The manufacturer probably took off-the-shelf parts to design their product without worrying about how they interfaced with each other. Who knows, the design might have originally worked great but then someone changed one of the parts to save some money. As a result, %5 of the resulting products end up showing flicker.
This is not a hard problem to solve and I assume most high quality manufacturers have done so. But manufacturers that bundle the lowest cost components together could very well see this problem.
Just host the GIT repository on a VM in the cloud. Look at TurnkeyLinux or Bitnami. Configure the VM to only accept encrypted connections and use an excrypted file system. One could still break into your VM if they wanted to - but it would be a lot of work and no government agency would bother investing the time and money to do so. If the NSA wants your source code you can bet they will get it - even if it's hosted locally.
But the reality is you are being paranoid. The government does not care about your source code. They want to know who your friends are and when you communicate with them. If a rotten egg is found they want to be able to check for rot in neighboring eggs - because rotten eggs are generally connected.
And here we have a perfect example of (one of the reasons) why Greece has the problems it has. People so convinced that the are owed more of everything as to think that goods being sold by private companies can be price fixed by the government so they can afford them.
The point of regulation is to prevent companies from market manipulation. Companies will naturally move to maximize profits and will, if allowed, perform any action to do so. Competition gets eaten up while at the same time no room is left for new players. Eventually, the market dies.
So regulation is required to facilitate a healthy market. Rules are put in place to ensure that established companies can not prevent competition from entering a market. Limits to what monopolies can do are instigated. Everybody is forced to play fair in an attempt to maximize competition and the benefits of capitalism.
People go on and on about how capitalism and regulation are polar opposites. This is ludicrous. Without regulation the benefits of capitalism do not exist. The invisible hand is an idealized concept which, much like communism, ignores reality and is doomed to failure. A market without sufficient regulation will not optimizes overall efficiency. Of course too much regulation also reduces efficiency - but a certain amount is always required.
So this isn't about the Greek people wanting the government to fix prices - this would obviously not work. It's about opening up the markets that have been sewn shut by the current players. This required effective regulation - far easier said then done.
The radio, and associated amplifiers, will generate the majority of the heat. Just look how much longer a cell phone will operate if you disable wireless. One must also take into consideration that wireless routers operate at higher power levels.
A better way to test the effects wireless signals would be to disable wireless by replacing the antenna with 50 ohm resistors. The radio would utilize the same amount of power but would not radiate any significant signals.
People are funding client skeptics, and people are finding Climate Change studies.
You're right in that we have two groups - but only one is involved in actually science.
When you receive funding only when your "research" produces the desired results it becomes nearly impossible to have unbiased results. It becomes propaganda masquerading as research. To actually perform real research, the researcher must receive funding regardless of result.
The problem with the skeptics is that their "research", which is always biased, is taking away from the real research that is being done. When an outsider observes two publications making opposite claims, both publications are discredited. And if you ask that outsider which publication they believe, they will usually pick the one they want to be right - which is the one that says they can keep on burning oil.
The scientific community knows that climate change is real and that human activity is to blame. But the general populous does not partly because of the fake research and the arguments it spawns. So no, we shouldn't accept funding from all sides. Funding should only come from a neutral side - if the rich want to fund more they can donate funds to that neutral side.
Yeah, I had come across that one. Then again, you first have to know it exists. Apple won't warn you nor inform you. And when you investigate and find out, it's usually because the regular Unix tools have already wrought havoc.
All of the standard Unix tools for moving / copying files have supported resource forks for some time now. But it's really not a big deal because only Classic / Carbon MacOS apps make use of resource forks. Classic will not run on new hardware and Carbon was depreciated a while ago. If you are a Unix user, I can't imagine a situation where you would want a resource fork.
It's a case-preserving filesystem by default. Because it's a Mac and needs backward-compatibility.
Whatever. Have fun developing on a case-insensitive file system and not noticing case mismatches that will suddenly stop the show when you run your stuff on a proper Unix.
You have it wrong. The file system is not really case-insensitive as per the traditional sense. If you have a file named "SomeFile.pdf" and try to open "SomeFile.Pdf" it will fail. The case is sensitive just as with the other Unix based operating systems. Where it differs is that it will not allow you have files named "Readme" and "readme" in the same location.
Get hold of portable property. -- Charles Dickens, "Great Expectations"