In those days, they had punt guns. These were wide bore barrels mounted directly onto a punt. and each could propel pellets in a wide and long enough range to take out a good number of a flock of ducks at one time. But there seem to be others that might have been used on land:

http://homemadedefense.blogspo...

I'd imagine they decompress the video into it's constituent frames. That's easy to do with various Linux command line tools. Now you have to determine whether each adjacent pair of images are moving forwards or backwards in time. You can split this task up into small tiles to make use of parallel processing. Now you've got various sorts of movement; no change (eg. blue sky), upwards movement (smoke, clouds, rockets), sideways movement (cars, people), downwards movement (stuff falling, parachutists). Each of those will have it's own pattern of pixel movement and colors.

If you can understand what an object is, you can impose some sort of expectations on how it will move. You just need to look at some of those early comedy movies where the directors discovered how to play a film reel backwards. A tractor/trailer going backwards wasn't unusual, but someone lying on the ground, rolling backwards then jumping back into a standing position on the trailer was. Another one would be paratroopers receive an order to retreat, standing in a field, inflating their parachutes and jumping upwards into the back of an aircraft. So some rules are: human figures don't jump higher than 2 or 3 feet without help of a trampoline or unless they are a super hero. Smoke doesn't concentrate itself back into a small tube. Liquids don't fall upwards into the ceiling. If the system can understand those rules, it can tell when a video is being played backwards or forwards.

Neighbors have gone to war over the location of a fence. What happens is that a building company does two things; apply for planning permission and apply for change of registered land ownership. Sometimes they do one, and the paperwork fails to complete for the other. So the builder constructs a row of terraced homes and say, "Oh, by the way, a bit of your garden is owned by the residents on the other side of the fence, but they don't mind, so there really isn't anything to worry about".

Then the ownership of the other property changes, the new owner sees a way of increasing their market value of their property as well as gain new resources, and the bulldozers move in, leading to court action and bankruptcy.

Anyone has visited or lived in Africa will tell you that. You just need to look at satellite photographs of Earth at night to see that Africa has electricity. Like any rural area, the main hazards to power supply are thunderstorms and local wildlife. Power failures are frequent, along with the associated power surges and fluctuating power line voltages.

Africa is on the equator, so the climate is like Florida or New York in Summer but all year round. Sunrise at 6am, sunset at 6pm. Air conditioning is a luxury usually available only to office blocks and hotels. Any building without air conditioning becomes an oven. So having a 32" 600 watt plasma display wouldn't be appreciated. A small 12" black/white CRT is ideal and the bulkiness prevents looters from stealing it.

If it is a small mini-portable TV that fits in the corner of a mud-brick hut, then probably yes. There isn't much space once you have a couple of bunk-beds on each side of the door, a cooker and refrigerator on the far wall, and some cupboards on each side. The only space left is an upper corner, which is just enough space for a small TV.

Then we end up putting dioxins into the environment. You have to burn the plastic in high-temperature incinerators to prevent that from happening.

The problem is that you also end up filtering out all the other life out of the ocean; amoeba, plankton, larvae stages of fish and crustaceans, which sortof defeats the purpose of trying to filter out the plastic in the first place.

That's the hard part - finding something that will remove the plastic but not the DNA lifeforms.

Something significant would be a decades worth of pay-rises for each employee affected.

That would be $10,000 x 10 x 64000 = $6.4 billion

It's not just eyes, they also try and replicate the limitations of cameras; lens flare, the Bokeh effect, motion blur, depth-of-field. If a title doesn't have those effects, it's not keeping up to date with everyone else.

Even with the Ultra 64, the Quake version gave you the choice of enabling/disabling mip-mapping. For a while mip-mapping looks cool because everything looks less pixelly. Then when you switch it off, everything looked better because it was sharper.

At the time I was in my first undergraduate course, the major demotivators for the female students were mainly the long hours of study and work in front of a computer. At other colleges, it was being located in a remote off-campus building away from the main social centers like cafes and student union bars. One college even had a dispute between the computer services department and their department over how a funding grant for equipment should be spent, leading to Email service being denied.

And graphics programmers need both frame rate and pixels. 120Hz seems perfect, but once you try using 3D vision glasses, those LCD shutters bring back the flicker.

The problem with the higher resolutions is that application developers just seem to think they can then make their application main window even bigger so it still fills the entire screen. Then they have to use bigger fonts to maintain compatibility with past versions of the same application.

You should look at the latest OpenGL ES specification. This is OpenGL optimized for mobile devices and gets rid of most of the old API bits while still supporting vertex, fragment and compute shaders. Anything else is just implemented using shaders.

But mantle gives you access to the hardware registers (those descriptors) while avoiding the overhead of updating the OpenGL state, then determining what has changed and hasn't, then writing those values out to hardware.

I'd say the fundamental problem is that the specifications themselves are a patchwork of code changes written in a natural language.
The original specification is written before the original driver code is modified, or derived from an existing driver for one hardware system, and then recoded for a new driver for another hardware system. With other device drivers (networking), each extension specification is actually specified in a high-level language which can be processed straight into device driver code.

Direct3D has the advantage that the hardware must match the software specification, while OpenGL is more extension applied over extension on different hardware. Since each vendor has different hardware and supported extensions, the implementation of one extension may or may not affect other extensions. For example, you could support FBO (framebuffer objects) using textures as a destination. But then if you implement compressed textures, then those textures can't be used with FBO's, and so additional code has to be added to prevent that use. Usually the reason that you can't use a particular combination of extensions is simply because the hardware logic hasn't been implemented yet.

HP already became a "box integrator" back in the 1990's when Microsoft went on their "UNIX is legacy, Windows NT is the future" rampage. HP caved in, dumped HP-UX, started packaging Windows workstations, and ended up competing against Dell and other companies.

They were in two minds about open source. On the one hand it kept Microsoft at bay, on the other hand, open source projects had cut into their revenue in the past. In the days of "UNIX prices", companies could charge for printed copies of system manuals, development kits, compilers, user and CPU core licenses