going from 80% QE to 90%QE (assuming that charge collection is near perfect, and does not change), means you detect about 12% more photons, so you use a 12% faster shutter speed, or work with 12% less light.
exposure is logarithmic, so a 12% improvement is pretty much negligible. you need to double your sensitivity to claim a '1 stop' improvement.
Old, manual-focus, non-zoom lens are in many ways better than modern lenses for filming, and cheaper and lighter than modern equivilents. * Good manual focus rings, you dont usually want AF for film (technically because not many DSLRs can do autofocus in video, and also because autofocus does not always do what you want it to do in video, eg rack between to faces as they talk). AF lens tend to be poor for manual focus, the whole focus range may only take a small rotation, so it is hard to be preciese. * Large aperture. there are plenty of old F/1.8 and F/1.4 around. You dont have so much freedom with shutterspeed as you do with stills. * No zoom. Not commonly used in film. You wont find an F/1.8 zoom easily * Not as sharp as a modern lens. But this does not matter, HD is only 2 megapixels where as modern lens need to be sharp at 20 megapixels
You can't put an old canon lens on a new canon camera (without an adaptor containing an extra lens element). Old nikkon lens only require a cheap ($20) adaptor to fit a modern canon.
There are also some complaints about it absorbing other components e.g. udev. to the developers this makes sense because udev is about responding to hardware events and systemd can trigger this based on these events (e.g. starting network servers when you plug in a network card, or a backup script when you plug in an external drive). also they shared a lot of code. To people who don't want to use systemd, this makes them worry about where they will get udev from, and if udev will continue to work on non systemd systems. (there is now a fork of udev called eudev)
systems with poor GPUs probably have poor CPUs as well, so LLVM pipe is not going to be fun.
You don't have to go back to far to find GPUs with max textures size of 2048x2048 or lower. for a composited desktop across multiple desktops the total desktop size cant exceed the max texture size. So on a few year old netbook you may not be able plug into to an external monitor or projector with GNOME3 where you could with GNOME2.
i booted fedora18 in a kvm virtual machine today. The GNOME3 desktop displayed, but with horrible corruption.
if you liked Gnome2 you will like MATE (because its basically the same, plus a name change so it can coexist with Gnome3, plus bug fixes, library updates and a few small new features)
gstreamer support has been there (but disabled by default) since fedora 14. on gentoo you just add gstreamer to your use flags and you can watch h.264.
moore's law only talks about transistor counts. building a supercomputer means getting thousands of CPUs to cooperate which is a much harder challenge.
Anyone (with a large wallet) can stick an exoflop worth of CPUs in a large room. by 2020 you'll be able to do that with a not so large wallet. but that does not result in a useful exoflop computer
I wonder if the communication about edits and why they are being made can be improved. maybe there was some trivial reason, that nobody ever tried to explain to you. or maybe it was vandalism, i'm not sure what mechanisms they have in place to prevent it.
It was not hard to edit before (I mostly used josm), but lowering the bar is probably a good thing.
What I would like to see is better history viewing. on wikipedia it is quick to see if a page has been edited recently and by who. obviously this is a harder problem for a map. clicking history on openstreet map does not show much of use (right in the middle of an inland city i am seeing edits like "Update harbour tags ").
the term perpetual motion is used in different ways. usually to imply that something is a magical source of endless motion.
There are actually plenty of physical systems that will move for ever. anything that moves with no friction. bodies in space is almost an example of this, but would actually be a small friction from interstellar (and intergalactic) gas and dust, and interaction with CMBR. also there are plenty of quantum 'motions' that could qualify. you can't extract energy from these systems without slowing them. in the quantum case they might still 'move' in the ground state, so you can't extract that energy.
Then there are the crazy mechanical designs that people invent. generally (ignoring the flat out fraudsters) the inventor believes that they have found a system that generates a perpetual force that for example rotates a wheel. They usually believe that they just need to get the friction a bit lower, and then it will run. This is a good example http://www.lhup.edu/~dsimanek/museum/unwork.htm#stevinprob (in fact everone should go and read that whole site.)
yes, but you have no idea if the data in the files has become corrupted by the same hardware error. to be robust a filesystem needs data checksums.
there have been reports on the btrfs mailing list of bugs, that turn out to be due to hardware issues. the drives were corrupting the data and btrfs notices pretty quickly. the drives were also corrupting data when they had other filesystems on them, but it had not been noticed.
I was involved in making a low (GPB2000) budget film, which was released with a CC-BY-NC licence. For distribution we used youtube, vimeo, archive.org and bittorrent. Youtube was by far the most popular option for downloads (over 90%), but bittorrent was the only method that worked for the highest quality (~20GB 1080p file). we set up our own tracker, because we could not get clearbits to work. we seeded from a friends colo server, VPS and a few home broadbands.
might be doable. but i suspect not in a way that a distro could offer them both and have selecting between them at gdm work (most distros would not accept the kind of hacks you would need).
I dont think that is right.
going from 80% QE to 90%QE (assuming that charge collection is near perfect, and does not change), means you detect about 12% more photons, so you use a 12% faster shutter speed, or work with 12% less light.
exposure is logarithmic, so a 12% improvement is pretty much negligible. you need to double your sensitivity to claim a '1 stop' improvement.
most criminals in the UK are unarmed.
Old, manual-focus, non-zoom lens are in many ways better than modern lenses for filming, and cheaper and lighter than modern equivilents.
* Good manual focus rings, you dont usually want AF for film (technically because not many DSLRs can do autofocus in video, and also because autofocus does not always do what you want it to do in video, eg rack between to faces as they talk). AF lens tend to be poor for manual focus, the whole focus range may only take a small rotation, so it is hard to be preciese.
* Large aperture. there are plenty of old F/1.8 and F/1.4 around. You dont have so much freedom with shutterspeed as you do with stills.
* No zoom. Not commonly used in film. You wont find an F/1.8 zoom easily
* Not as sharp as a modern lens. But this does not matter, HD is only 2 megapixels where as modern lens need to be sharp at 20 megapixels
You can't put an old canon lens on a new canon camera (without an adaptor containing an extra lens element). Old nikkon lens only require a cheap ($20) adaptor to fit a modern canon.
I was using virt-install which (according to its man page) defaults to --graphics vnc if the DISPLAY variable is set.
That sounds about right.
There are also some complaints about it absorbing other components e.g. udev. to the developers this makes sense because udev is about responding to hardware events and systemd can trigger this based on these events (e.g. starting network servers when you plug in a network card, or a backup script when you plug in an external drive). also they shared a lot of code. To people who don't want to use systemd, this makes them worry about where they will get udev from, and if udev will continue to work on non systemd systems. (there is now a fork of udev called eudev)
systems with poor GPUs probably have poor CPUs as well, so LLVM pipe is not going to be fun.
You don't have to go back to far to find GPUs with max textures size of 2048x2048 or lower. for a composited desktop across multiple desktops the total desktop size cant exceed the max texture size. So on a few year old netbook you may not be able plug into to an external monitor or projector with GNOME3 where you could with GNOME2.
i booted fedora18 in a kvm virtual machine today. The GNOME3 desktop displayed, but with horrible corruption.
if you liked Gnome2 you will like MATE (because its basically the same, plus a name change so it can coexist with Gnome3, plus bug fixes, library updates and a few small new features)
gstreamer support has been there (but disabled by default) since fedora 14. on gentoo you just add gstreamer to your use flags and you can watch h.264.
moore's law only talks about transistor counts. building a supercomputer means getting thousands of CPUs to cooperate which is a much harder challenge.
Anyone (with a large wallet) can stick an exoflop worth of CPUs in a large room. by 2020 you'll be able to do that with a not so large wallet. but that does not result in a useful exoflop computer
For folk who even after RTFA wonder whats new in 3.10, the best source is probably LWN
https://lwn.net/Articles/548834/
https://lwn.net/Articles/549477/
is it even possible?
most estimates of population over the next century are not too scary. the massive growth seen in the 20th century has damped down https://en.wikipedia.org/wiki/World_population .
you might need to make sure you use the right option when creating the volume. i am not sure winxp support is really needed these days.
any good reason not to use UDF for large flash cards? it has read and write support in linux, mac and windows. I use it for USB sticks.
I wonder if the communication about edits and why they are being made can be improved. maybe there was some trivial reason, that nobody ever tried to explain to you. or maybe it was vandalism, i'm not sure what mechanisms they have in place to prevent it.
it has been able to play h.264 since firefox 14. just build it with --enable-gstreamer. (this is easy to do if you run gentoo. most major distros have a bug open asking them to enable the gstreamer support. eg https://bugzilla.redhat.com/show_bug.cgi?id=843583 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1051559 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682917 )
--
my name is ssam and i have been flash free for 5 months
It was not hard to edit before (I mostly used josm), but lowering the bar is probably a good thing.
What I would like to see is better history viewing. on wikipedia it is quick to see if a page has been edited recently and by who. obviously this is a harder problem for a map. clicking history on openstreet map does not show much of use (right in the middle of an inland city i am seeing edits like "Update harbour tags ").
but given that '*' is a wild card it will actually match any password that i try to log in with.
thanks that makes sense. i couldn't really believe that folk smart enough to make homomorphic crypto would not have though of this.
my password is '*********' so there will be no change for me
so then i can do a/a to get 1, and so find E(1), then 1+1 to find E(2) and so on until i have full mapping of plaintext numbers to cyphertext numbers.
the term perpetual motion is used in different ways. usually to imply that something is a magical source of endless motion.
There are actually plenty of physical systems that will move for ever. anything that moves with no friction. bodies in space is almost an example of this, but would actually be a small friction from interstellar (and intergalactic) gas and dust, and interaction with CMBR. also there are plenty of quantum 'motions' that could qualify. you can't extract energy from these systems without slowing them. in the quantum case they might still 'move' in the ground state, so you can't extract that energy.
Then there are the crazy mechanical designs that people invent. generally (ignoring the flat out fraudsters) the inventor believes that they have found a system that generates a perpetual force that for example rotates a wheel. They usually believe that they just need to get the friction a bit lower, and then it will run. This is a good example http://www.lhup.edu/~dsimanek/museum/unwork.htm#stevinprob (in fact everone should go and read that whole site.)
yes, but you have no idea if the data in the files has become corrupted by the same hardware error. to be robust a filesystem needs data checksums.
there have been reports on the btrfs mailing list of bugs, that turn out to be due to hardware issues. the drives were corrupting the data and btrfs notices pretty quickly. the drives were also corrupting data when they had other filesystems on them, but it had not been noticed.
I was involved in making a low (GPB2000) budget film, which was released with a CC-BY-NC licence. For distribution we used youtube, vimeo, archive.org and bittorrent. Youtube was by far the most popular option for downloads (over 90%), but bittorrent was the only method that worked for the highest quality (~20GB 1080p file). we set up our own tracker, because we could not get clearbits to work. we seeded from a friends colo server, VPS and a few home broadbands.
might be doable. but i suspect not in a way that a distro could offer them both and have selecting between them at gdm work (most distros would not accept the kind of hacks you would need).