A further development: instead of grooves, have long stretches of tiny electronically controlled bumps that can push up from the road. Now the tune can be changed.
Yes, it is possible, but it may not be feasible. Hypothetically, some hardware may have properties that would require emulation at, say, a quantum level to achieve identical output.
More practically, the hardware may simply be different enough that emulation would be infeasible for a hobbyist. Not that I would know about it myself.
If one piece of code requests a chunk of memory and another does the same, the two chunks cannot normally be shared, even if the code happens to run from the same place in memory. How is the OS to know whether the memory will be used for the same purpose, whether the two instances are synchronized, etc..
There is no reason at all to have several copies of the exact same exacutable code run on the same processor(s). It's much better to reuse the code, and let it run on different data, in separate threads if you need. Having several copies of the same app in memory is merely an ugly hack to gain functionality that already should be in one copy app itself.
Still pictures don't qualify as HDTV. Those Hasselblads took impressive stills, but no HD video.
It's a still from a video.
Yes, but those are still pics, nothing new there. This particular camera on Kaguya is 3CCD HD video, which is rather unusual to have in space.
A further development: instead of grooves, have long stretches of tiny electronically controlled bumps that can push up from the road. Now the tune can be changed.
More practically, the hardware may simply be different enough that emulation would be infeasible for a hobbyist. Not that I would know about it myself.
Are you seriously, really seriously suggesting that US citizens enjoy the most free speech in the world?
The point is very valid, but isn't there any way to make things more distributed?
That's right, no letters on the keys. We don't have colour TV in Europe either.
People read slashdot for current political commentary? That explains a lot...
Yes, but that is a different design concept from what apps usually have. Unfortunately, I say, but things are still that way.
If one piece of code requests a chunk of memory and another does the same, the two chunks cannot normally be shared, even if the code happens to run from the same place in memory. How is the OS to know whether the memory will be used for the same purpose, whether the two instances are synchronized, etc..
Bread is a commodity, film is a creative work, intellectual property.
Though the GP is trollish, those are not bugs but rather design flaws.
And what happens when all those instances of the same DLL allocates some memory...?
There is no reason at all to have several copies of the exact same exacutable code run on the same processor(s). It's much better to reuse the code, and let it run on different data, in separate threads if you need. Having several copies of the same app in memory is merely an ugly hack to gain functionality that already should be in one copy app itself.
Since always, I would say.
It was posted a few hours before the attack, so it's kinda unlikely anyone relevant saw it.
Makes no difference, the concept works anyway. Valve can figure those things out later on, if it's ever needed.
Two important points: 1) the study says specifically overweight, not obese, and 2) it doesn't talk about quality of life, only mortality rate.
The plug might be behind the dishwasher, in which case it is not immediately obvious, and definitely not a trivial solution.
Steve: Eeearlyadopterssufferfortherest of uuussss...
Apple congregation (with organ): Aaaaa- meeeeennn...
Dialog system, bah. In my days, all we had was "NAME", "JOB", and "I cannot help thee with that", and we were happy!
One bullet hole per bullet point ought to do the trick.
Once upon a time, it took three years for a Debian release...