The real drawbacks of using PostgreSQL: your hosting may not support it, the application you want to use may only support MySQL.
In the olden days, MySQL was synonymous with using the MyISAM storage engine, which was not very reliable but was faster than the alternatives (the InnoDB storage engine for MySQL or PostgreSQL. MySQL+MyISAM was also far easier to setup and configure than MySQL+InnoDB or PostgreSQL.
And the logic was that for most websites, speed was more important than reliability. There are, however, two problems with that logic. Problem 1: Your website may not need full ACID compliance level reliability, but it needs some. It's mighty inconvenient when then system crashes and boots to a corrupted database. It's like when Windows used FAT32 instead of NTFS.
Problem 2: Nowadays, MyISAM is actually only good at simple, read only, workloads. Complicated queries or writes tend to bog it down. And even simple websites have growing amounts of both. Nowadays, InnoDB has improved to the point it is, in general, faster than MyISAM while providing better reliability (and it's finally been made the default MySQL storage). PostgreSQL also improved a lot in performance. In particular, it tends to be better at handling complicated queries and at scaling better in multi-CPU systems.
You're not missing anything, running a bridge at your home is fine. But since you're not willing to spare your scarce bandwidth, then AWS instance is an easy and cheap way to contribute.
What you suggest is being done, see Sender Policy Framework and DKIM. And it does help a lot.
However, it's not a solution to end all spam. - Many domains don't yet publish SPF/DKIM, so they can still be spoofed. - Spammers often use hijacked legitimate e-mail accounts. - Spammers sometimes spam from a domain which they do control.
Spamhaus are not self appointed. We, the system administrators, choose to use or not Spamhaus' black list (or any black list) in our systems to reject potential spammers. And we, the system administrators, are responsible for consequences of choosing to use a black list in our systems, including the possibility of rejecting legitimate messages and users and all that stems from it, from complains from your users to your boss yelling at you because the e-mail system rejected that important e-mail he was expecting.
Many of us choose to use Spamhaus' black list because they do a good job at a) identifying spammers b) keeping legitimate users out of their black list. They help us keep our jobs.
And if you care, Spamhaus are in a better position to identify what is spam and what is not than most. They have spent the last 15 years building up the means and experience to identify spammers, without falling victim of such simple tactics as complaining that you're being spammed by a mailing list you've subscribed.
You've got some weird setup there. It has to be doing some state tracking to do NAT or else your outgoing connections won't work. Unless you've set a specific high/low port range in each computer..
Anyway.. whatever rules you have there for IPv4, you can set them for IPv6 as well and it will be less work for your CPU.
Regarding the address space: yes, there are probably many possible avenues. Never quite stopped to think much about them, I just firewall my IPv6 networks.
Your router already implements stateful IPv4 NAT. Implementing a comparable (or better) IPv6 stateful firewall will put a similar or even smaller load on it's CPU.
Also, you might not need a stateful IPv6 firewall. The premise is that the minimum IPv6 network your ISPs should assign you is a/64, which has 2^64 possible addresses, which is too large to be scanned. By using an appropriate address assignment scheme (stateless autoconfig or random DHCPv6), it would be impossible for a potential external attacker to find your devices' addresses via a network scan. So, unless your device exposes it's address on the Internet in some way it's safe and this should be enough for things like printers, TVs, etc. Devices like your PC, tablet or smartphone are more likely to expose their IP address (ie, via participating in a BitTorrent swarm) but those need to be able to cope with being on a hostile network anyway. Ie, consider when you use your tablet in a hotel's WiFi.
Then again, this may be just wishful thinking and we'll need IPv6 stateful firewalls!
Like most cable providers, Comcast uses the 10.0.0.0/8 private address range internally to, among other users, manage their clients' modems. That is, in addition to the client's public IP address, each modem gets a private 10.0.0.0/8 address for management purposes. Their problem is that they have so many clients.. they ran out of private addresses. So, they want to deploy IPv6 earlier than most.
Also, the drivers being closed source, you are at the mercy of NVIDIA for features, fixes, etc. Now, NVIDIA has generally been good -- they know they have paying customers using their hardware in Linux. But there are some negative aspects, which NVIDIA has neglected. NVIDIA proprietary drivers don't implement all the features of the Linux graphic subsystem and so, there are some corner cases that don't work. The most obvious one nowadays is the support for Optimus and the cumbersome way it's being implemented.
Occasionally, it takes a while for NVIDIA to update their drivers to make them compatible with the latest kernel or X.org server.
The kernel code is mostly processor agnostic. But someone has to deal with the processor specific details and that someone is the kernel. So it also has some very fundamental processor specific bits. The 386 specific bits just got removed.
It's not a particular problem with hydrogen or even turbine engines. Pretty much all thermal engines benefit of having a cold air intake Broadly, two reasons: - Colder air is denser and it takes less effort to feed more air into the engine, in order to be able to burn more fuel. - Higher temperatures (can) yield higher efficiencies, but the engines are limited by what engine materials can whistand.
Turbocharged petrol or diesel engines usually have a intercooler to cool down the air between the turbocharger and the engine itself. Some gas-turbine electric plants in hot locations pass the air through a room full of ice before intake.
What these guys did was, taking advantage that they use liquid hydrogen (very cold) as fuel, they cool the air down before the intake, making life easier to everything that comes next. The tricky part really was designing the heat exchanger.
It took what worked and made it not work, not too mention turning over a disproportionate amount of CPU time. Pulseaudio was just to get mixing to work basically because some twits decided it couldn't be done in the kernel (it can, and no one apart from OSS has tried). They broke the whole sound system for a very long time to do it. Lunacy.
You're just spewing contradicting bullshit.
As you wrote, nobody but OSSv4 has ever tried to do mixing within the kernel; largely because the upstream kernel maintainers have made clear several times they won't accept it. So, before PulseAudio, audio in Linux did not work properly. It got by and mostly worked using either hardware mixing (when those cards were common) or one of a few user space mixing solutions (esd, artds, ALSA dmix). None of the user space mixing solutions worked quite well, so something else was needed.
It actually depends on the plant type, not the fuel.
All traditional thermal power plants suffer of the problem, independently of what they use: coal, oil, gas or nuclear. As Smidge wrote, they use massive steam boilers which take lots of time to heat up and cool down.
Combined cycle power plants are much better, as the gas turbine can be throttled quickly and the steam system is much smaller and hence also reacts quicker. But the gas turbines can't burn coal, unless it goes through a complicated (expensive) process to convert into a synthesis gas.
So, in practice all coal power plants are traditional thermal plants. There are old thermal power plants burning oil and gas, but most of the new ones are combined cycle --cheaper and more efficient.
AFAIK, oil is getting less and less used to produce electricity as it's just too expensive compared to coal and natural gas.
SR motors are not "far more efficient" than permanent magnet or the other types of electric motors used in high power applications. All of these motors can achieve efficiencies in the 90% range. The differences come down to few % efficiency, cost, weight and other factors depending on application.
For example, Renault has chosen wound rotor synchronous motors for the Zoe, which is a very rare choice. But this allows them to re-purpose the motor driver as charging circuit and gave the Zoe a built-in 44 kW charging ability for almost free.
Agreed. So don't do that. Instead, use the Zero Install techniques, both the one's they've implemented, and the ones they wish they had time for. I run $100K software packages on Linux boxes from Cadence and Mentor. The exact same executables run on Fedora, Ubuntu, and Debian. The way they accomplish this is statically linking all the way down to the linux kernel interface (maybe they link to libc - not sure).
I'm afraid you're incorrect. I have the Cadence binaries at hand and they're all dynamically linked against a large set of libraries. What they (and most developers like they do) is to specifically target a reasonable set of distributions, RHEL4 and 5 in particular. Running on other distributions mostly works, but they provide no guarantees and no support. In fact, I can't launch 64 bit Virtuoso because of an incompatible Qt library.
I'm not going to say it's an unmitigated horror but I share a similar experience with the other poster.
Unity looks great. And it works great for the majority of cases. I used it on my netbook since 10.10 for web browing, e-mail, etc and I always liked it. My mother and sister also use it in our home computer without any issues.
The problem is that window management stops being comfortable after a very small number of windows. Too small for when I'm working. And my co-workers who tried Unity seem to feel the same, leading them to switch away.
Trying to put my finger to it, I'd say it's missing one more switching mechanism.
Alt-Tab/` switching is nice but requires cycling/using the arrow keys to select. It is worse in Gnome2 (cycling only only) but better in Gnome3, as you can use both arrow keys and the mouse to select windows.
Switching through the Dash becomes too cramped when you have many windows, made considerably worse because windows of the same type always get grouped together. Gnome 3's launcher has the same problem.
Gnome2 doesn't have a launcher. But it does have a window switcher applet in the panel, which has lots more room and doesn't group windows until it has to. This makes it able to comfortably manage a lot more windows.
Gnome 3 too has one more mechanism, compared to Unity. When you bring out the Activities view (press OS key or throw your mouse to the upper left corner) you get a nice mosaic of all the windows in the desktop which you can then select with the mouse (along with the side panel and the desktop switcher).
In my experience, this feature makes the difference between a hard-to-use-for-work-desktop and best-desktop-I-ever-had.
Mostly agreed, though I have a slightly different take on the succession of events.
Cell phones are already, mostly, behind LS-NAT (without IPv6). My guess is that consumers will be next. Many if not most consumers won't want to pay much to have a public IPv4 because, for them, sitting behind a ISP level NAT (LS-NAT) won't be too bad -- at first, at least. Web browsing will mostly work; most P2P applications will work as long as one of the peers has a public IPv4, etc. So, when faced with the option to pay extra for a public IPv4, I think they'll be the first to opt to have a IPv4 LS-NAT.
Eventually though, being behind a LS-NAT or having your website's users behind a LS-NAT will become troublesome though, as more and more people do. Ie, performance might be worse, P2P applications won't work between two customers which are both behind LS-NAT, etc. At that point, ISPs will need to offer IPv6 access to their IPv4 LS-NAT customers, websites will want to support IPv6 so communication can go around the LS-NAT.
I'm actually a bit optimistic about this. Major "fixed" (DSL/Cable/Fiber) ISPs seem to have plans to deploy (IPv4+) IPv6 before to their customers before they have to start deploying LS-NAT.
I've been using Unity (or whatever it was called back then) on my 10.1" netbook since it was available and I never liked it for the desktop.
But I've gown to like Gnome 3 and, in particular, it's task switching. While Gnome 2 style task switching works well, it becomes a bit painful when you have a more than a few windows in the same desktop. If I have more than a few, names in the task list buttons will become truncated, which tends to require extra effort to figure out which button I want. If I have a lot (and I sometimes do), then the task list button will group windows, requiring me to navigate through the groups.
Gnome 3's requirement of the mouse to the upper left corner or pressing the "Windows key" is a hassle, but a very small one in imho. The Windows key is well at hand, and I don't really move the mouse to the upper left corner: I just throw it there. And in return, I get a visual overview of all windows. Of course, your mileage may vary but for me it's a boon.
I also like being being able to navigate windows when I keep "Alt+tab" down. Although I'd prefer if the new scheme was activated just with "Alt+~" and "Alt+tab" operated in a more traditional manner.
Fourier's theorem PROVES that ANY signal can be represented as spectrum -- a sum of pure sine waves, each with their own (frequency, amplitude, phase). No matter what it's shape and how complicated it is, ANY signal can be decomposed into a spectrum. In the domain of digital processing, bandwidth is usually meant in the sense of decomposing a signal into a spectrum.
So, when Nyquist-Shannon's theorem PROVES that any signal with a bandwidth less than B can be sampled at a rate 2B without loss of information, it refers to a signal whose spectrum is contained in a band B.
When we say human's can't hear above 20 kHz, it's also in the same sense.
Now, consider a 1 kHz pure square wave. No sampling frequency is good enough. When decomposed into a frequency spectrum, this signal has infinite bandwidth.
However, we can't hear the higher frequency parts of the spectrum. Or said in another way, we wouldn't be able to tell the difference between a signal and the same signal smoothed by an ideal low 20 kHz low pass filter.
It can be heard, but you need to turn your volume way up. Try this: sox -V -t sl -r 44100 -b 16/dev/zero silence.wav trim 0 1:00 This first command will produce a WAV consisting on a stream of 16 bit null samples.
sox -V -t sl -r 44100 -b 24/dev/zero -b 16 dithered_silence.wav trim 0 1:00 This second command will convert a stream of 24 bit null samples to 16 bit, adding dithering noise in the process. This will be a good representative of the noise floor "intrinsic" to a 16 bit format.
Play the dithered_silence.wav file and turn up the volume knob until you can hear the noise. Then play the silence.wav just to check that the noise was coming from the file, not from your playback system. And then ask yourself: do you really listen to music that loud?
Also, a warning: many classical music recording have way higher noise floors, due to ambient noise.
Like most others, Yahoo's website is only available through IPv4. Thus, even computers that have IPv6 still use IPv4 to get to access Yahoo.
When they enable IPv6, computers which have IPv6 will try to use IPv6 to access Yahoo.
Computers which aren't compatible with IPv6 are actually fine: they'll just use IPv4 like always. The problem here is that there's a large number of computers which (thinks) it has IPv6 connectivity but actually, the IPv6 connectivity is broken. Thus, when Yahoo enabled IPv6 on their site, these computers will have trouble getting to Yahoo.
The reasons vary. One reason are computers that sit on a network that has IPv6 for internal use but doesn't have IPv6 internet connection. Another reason (or set of reasons) is that the computer has an IPv6 internet connection but, somewhere between the computer and Yahoo (ISP, etc, etc) , it's broken.
Because the existing route between Pollegion and Faido imposes limits on both trains' speed and load. The tunnel will not just reduce the distance, it will also allow the passenger trains to go faster and the freight trains to carry heavier loads.
They have been protected by law in their respective countries for a long (long) time. But these denominations could never been made as registered trademarks. In order to register something as trademark, it must not be in common use. Being mostly names of regions, these denominations were already in common use when the registered trademarks laws were created. So, they had to be protected under a different legal scheme; which was never upheld in the rest of the world.
Actually, a bunch of them were protected *before* any registered trademarks were created. The Tokaj protected region was established in 1717, Chianti in 1730 and Port in 1756. Meanwhile, UK's Trademark Registration Act was only passed in 1875.
In Europe, wine names such as "Tokaj", "Chianti", "Port", "Champagne" and many others have been trademarks bound, by law, to specific regions and types of grape and even production methods. Some of these parameters are so narrowly defined that winemakers from those regions sometimes opt to skip the protected trademark in order to have more freedom in their wine making.
Some of these legal protection schemes go back to the 18th century: Chianti in 1717, Tokaj in 1730, Port in 1756. Champagne is much more recent, only being legally defined in 1927.
That said, I really do understand that citizens from non-European countries, who are quite accustomed to use these words in a more generic sense, think it's wrong to suddenly take these words from the public domain and make them into protected trademarks.
Slashdot Mirror
The real drawbacks of using PostgreSQL: your hosting may not support it, the application you want to use may only support MySQL.
In the olden days, MySQL was synonymous with using the MyISAM storage engine, which was not very reliable but was faster than the alternatives (the InnoDB storage engine for MySQL or PostgreSQL.
MySQL+MyISAM was also far easier to setup and configure than MySQL+InnoDB or PostgreSQL.
And the logic was that for most websites, speed was more important than reliability. There are, however, two problems with that logic.
Problem 1: Your website may not need full ACID compliance level reliability, but it needs some. It's mighty inconvenient when then system crashes and boots to a corrupted database. It's like when Windows used FAT32 instead of NTFS.
Problem 2: Nowadays, MyISAM is actually only good at simple, read only, workloads. Complicated queries or writes tend to bog it down. And even simple websites have growing amounts of both.
Nowadays, InnoDB has improved to the point it is, in general, faster than MyISAM while providing better reliability (and it's finally been made the default MySQL storage).
PostgreSQL also improved a lot in performance. In particular, it tends to be better at handling complicated queries and at scaling better in multi-CPU systems.
You're not missing anything, running a bridge at your home is fine.
But since you're not willing to spare your scarce bandwidth, then AWS instance is an easy and cheap way to contribute.
What you suggest is being done, see Sender Policy Framework and DKIM.
And it does help a lot.
However, it's not a solution to end all spam.
- Many domains don't yet publish SPF/DKIM, so they can still be spoofed.
- Spammers often use hijacked legitimate e-mail accounts.
- Spammers sometimes spam from a domain which they do control.
Spamhaus are not self appointed.
We, the system administrators, choose to use or not Spamhaus' black list (or any black list) in our systems to reject potential spammers.
And we, the system administrators, are responsible for consequences of choosing to use a black list in our systems, including the possibility of rejecting legitimate messages and users and all that stems from it, from complains from your users to your boss yelling at you because the e-mail system rejected that important e-mail he was expecting.
Many of us choose to use Spamhaus' black list because they do a good job at a) identifying spammers b) keeping legitimate users out of their black list. They help us keep our jobs.
And if you care, Spamhaus are in a better position to identify what is spam and what is not than most.
They have spent the last 15 years building up the means and experience to identify spammers, without falling victim of such simple tactics as complaining that you're being spammed by a mailing list you've subscribed.
You've got some weird setup there. It has to be doing some state tracking to do NAT or else your outgoing connections won't work. Unless you've set a specific high/low port range in each computer..
Anyway.. whatever rules you have there for IPv4, you can set them for IPv6 as well and it will be less work for your CPU.
Regarding the address space: yes, there are probably many possible avenues.
Never quite stopped to think much about them, I just firewall my IPv6 networks.
Your router already implements stateful IPv4 NAT. Implementing a comparable (or better) IPv6 stateful firewall will put a similar or even smaller load on it's CPU.
Also, you might not need a stateful IPv6 firewall. /64, which has 2^64 possible addresses, which is too large to be scanned.
The premise is that the minimum IPv6 network your ISPs should assign you is a
By using an appropriate address assignment scheme (stateless autoconfig or random DHCPv6), it would be impossible for a potential external attacker to find your devices' addresses via a network scan.
So, unless your device exposes it's address on the Internet in some way it's safe and this should be enough for things like printers, TVs, etc.
Devices like your PC, tablet or smartphone are more likely to expose their IP address (ie, via participating in a BitTorrent swarm) but those need to be able to cope with being on a hostile network anyway. Ie, consider when you use your tablet in a hotel's WiFi.
Then again, this may be just wishful thinking and we'll need IPv6 stateful firewalls!
Like most cable providers, Comcast uses the 10.0.0.0/8 private address range internally to, among other users, manage their clients' modems.
That is, in addition to the client's public IP address, each modem gets a private 10.0.0.0/8 address for management purposes.
Their problem is that they have so many clients.. they ran out of private addresses.
So, they want to deploy IPv6 earlier than most.
Some people just like the concept of open source.
Also, the drivers being closed source, you are at the mercy of NVIDIA for features, fixes, etc.
Now, NVIDIA has generally been good -- they know they have paying customers using their hardware in Linux.
But there are some negative aspects, which NVIDIA has neglected.
NVIDIA proprietary drivers don't implement all the features of the Linux graphic subsystem and so, there are some corner cases that don't work. The most obvious one nowadays is the support for Optimus and the cumbersome way it's being implemented.
Occasionally, it takes a while for NVIDIA to update their drivers to make them compatible with the latest kernel or X.org server.
The kernel code is mostly processor agnostic.
But someone has to deal with the processor specific details and that someone is the kernel. So it also has some very fundamental processor specific bits.
The 386 specific bits just got removed.
It's not a particular problem with hydrogen or even turbine engines. Pretty much all thermal engines benefit of having a cold air intake
Broadly, two reasons:
- Colder air is denser and it takes less effort to feed more air into the engine, in order to be able to burn more fuel.
- Higher temperatures (can) yield higher efficiencies, but the engines are limited by what engine materials can whistand.
Turbocharged petrol or diesel engines usually have a intercooler to cool down the air between the turbocharger and the engine itself. Some gas-turbine electric plants in hot locations pass the air through a room full of ice before intake.
What these guys did was, taking advantage that they use liquid hydrogen (very cold) as fuel, they cool the air down before the intake, making life easier to everything that comes next.
The tricky part really was designing the heat exchanger.
It took what worked and made it not work, not too mention turning over a disproportionate amount of CPU time. Pulseaudio was just to get mixing to work basically because some twits decided it couldn't be done in the kernel (it can, and no one apart from OSS has tried). They broke the whole sound system for a very long time to do it. Lunacy.
You're just spewing contradicting bullshit.
As you wrote, nobody but OSSv4 has ever tried to do mixing within the kernel; largely because the upstream kernel maintainers have made clear several times they won't accept it.
So, before PulseAudio, audio in Linux did not work properly. It got by and mostly worked using either hardware mixing (when those cards were common) or one of a few user space mixing solutions (esd, artds, ALSA dmix).
None of the user space mixing solutions worked quite well, so something else was needed.
It actually depends on the plant type, not the fuel.
All traditional thermal power plants suffer of the problem, independently of what they use: coal, oil, gas or nuclear.
As Smidge wrote, they use massive steam boilers which take lots of time to heat up and cool down.
Combined cycle power plants are much better, as the gas turbine can be throttled quickly and the steam system is much smaller and hence also reacts quicker. But the gas turbines can't burn coal, unless it goes through a complicated (expensive) process to convert into a synthesis gas.
So, in practice all coal power plants are traditional thermal plants.
There are old thermal power plants burning oil and gas, but most of the new ones are combined cycle --cheaper and more efficient.
AFAIK, oil is getting less and less used to produce electricity as it's just too expensive compared to coal and natural gas.
SR motors are not "far more efficient" than permanent magnet or the other types of electric motors used in high power applications.
All of these motors can achieve efficiencies in the 90% range. The differences come down to few % efficiency, cost, weight and other factors depending on application.
For example, Renault has chosen wound rotor synchronous motors for the Zoe, which is a very rare choice.
But this allows them to re-purpose the motor driver as charging circuit and gave the Zoe a built-in 44 kW charging ability for almost free.
GIMP depends on GTK, not GNOME.
Agreed. So don't do that. Instead, use the Zero Install techniques, both the one's they've implemented, and the ones they wish they had time for. I run $100K software packages on Linux boxes from Cadence and Mentor. The exact same executables run on Fedora, Ubuntu, and Debian. The way they accomplish this is statically linking all the way down to the linux kernel interface (maybe they link to libc - not sure).
I'm afraid you're incorrect.
I have the Cadence binaries at hand and they're all dynamically linked against a large set of libraries.
What they (and most developers like they do) is to specifically target a reasonable set of distributions, RHEL4 and 5 in particular.
Running on other distributions mostly works, but they provide no guarantees and no support.
In fact, I can't launch 64 bit Virtuoso because of an incompatible Qt library.
I'm not going to say it's an unmitigated horror but I share a similar experience with the other poster.
Unity looks great. And it works great for the majority of cases.
I used it on my netbook since 10.10 for web browing, e-mail, etc and I always liked it. My mother and sister also use it in our home computer without any issues.
The problem is that window management stops being comfortable after a very small number of windows. Too small for when I'm working. And my co-workers who tried Unity seem to feel the same, leading them to switch away.
Trying to put my finger to it, I'd say it's missing one more switching mechanism.
Alt-Tab/` switching is nice but requires cycling/using the arrow keys to select. It is worse in Gnome2 (cycling only only) but better in Gnome3, as you can use both arrow keys and the mouse to select windows.
Switching through the Dash becomes too cramped when you have many windows, made considerably worse because windows of the same type always get grouped together. Gnome 3's launcher has the same problem.
Gnome2 doesn't have a launcher. But it does have a window switcher applet in the panel, which has lots more room and doesn't group windows until it has to. This makes it able to comfortably manage a lot more windows.
Gnome 3 too has one more mechanism, compared to Unity. When you bring out the Activities view (press OS key or throw your mouse to the upper left corner) you get a nice mosaic of all the windows in the desktop which you can then select with the mouse (along with the side panel and the desktop switcher).
In my experience, this feature makes the difference between a hard-to-use-for-work-desktop and best-desktop-I-ever-had.
Mostly agreed, though I have a slightly different take on the succession of events.
Cell phones are already, mostly, behind LS-NAT (without IPv6). My guess is that consumers will be next.
Many if not most consumers won't want to pay much to have a public IPv4 because, for them, sitting behind a ISP level NAT (LS-NAT) won't be too bad -- at first, at least.
Web browsing will mostly work; most P2P applications will work as long as one of the peers has a public IPv4, etc.
So, when faced with the option to pay extra for a public IPv4, I think they'll be the first to opt to have a IPv4 LS-NAT.
Eventually though, being behind a LS-NAT or having your website's users behind a LS-NAT will become troublesome though, as more and more people do. Ie, performance might be worse, P2P applications won't work between two customers which are both behind LS-NAT, etc.
At that point, ISPs will need to offer IPv6 access to their IPv4 LS-NAT customers, websites will want to support IPv6 so communication can go around the LS-NAT.
I'm actually a bit optimistic about this.
Major "fixed" (DSL/Cable/Fiber) ISPs seem to have plans to deploy (IPv4+) IPv6 before to their customers before they have to start deploying LS-NAT.
I've been using Unity (or whatever it was called back then) on my 10.1" netbook since it was available and I never liked it for the desktop.
But I've gown to like Gnome 3 and, in particular, it's task switching.
While Gnome 2 style task switching works well, it becomes a bit painful when you have a more than a few windows in the same desktop.
If I have more than a few, names in the task list buttons will become truncated, which tends to require extra effort to figure out which button I want.
If I have a lot (and I sometimes do), then the task list button will group windows, requiring me to navigate through the groups.
Gnome 3's requirement of the mouse to the upper left corner or pressing the "Windows key" is a hassle, but a very small one in imho.
The Windows key is well at hand, and I don't really move the mouse to the upper left corner: I just throw it there.
And in return, I get a visual overview of all windows. Of course, your mileage may vary but for me it's a boon.
I also like being being able to navigate windows when I keep "Alt+tab" down.
Although I'd prefer if the new scheme was activated just with "Alt+~" and "Alt+tab" operated in a more traditional manner.
Fourier's theorem PROVES that ANY signal can be represented as spectrum -- a sum of pure sine waves, each with their own (frequency, amplitude, phase).
No matter what it's shape and how complicated it is, ANY signal can be decomposed into a spectrum.
In the domain of digital processing, bandwidth is usually meant in the sense of decomposing a signal into a spectrum.
So, when Nyquist-Shannon's theorem PROVES that any signal with a bandwidth less than B can be sampled at a rate 2B without loss of information, it refers to a signal whose spectrum is contained in a band B.
When we say human's can't hear above 20 kHz, it's also in the same sense.
Now, consider a 1 kHz pure square wave.
No sampling frequency is good enough. When decomposed into a frequency spectrum, this signal has infinite bandwidth.
However, we can't hear the higher frequency parts of the spectrum.
Or said in another way, we wouldn't be able to tell the difference between a signal and the same signal smoothed by an ideal low 20 kHz low pass filter.
It can be heard, but you need to turn your volume way up. /dev/zero silence.wav trim 0 1:00
Try this:
sox -V -t sl -r 44100 -b 16
This first command will produce a WAV consisting on a stream of 16 bit null samples.
sox -V -t sl -r 44100 -b 24 /dev/zero -b 16 dithered_silence.wav trim 0 1:00
This second command will convert a stream of 24 bit null samples to 16 bit, adding dithering noise in the process.
This will be a good representative of the noise floor "intrinsic" to a 16 bit format.
Play the dithered_silence.wav file and turn up the volume knob until you can hear the noise.
Then play the silence.wav just to check that the noise was coming from the file, not from your playback system.
And then ask yourself: do you really listen to music that loud?
Also, a warning: many classical music recording have way higher noise floors, due to ambient noise.
That's exacly what Yahoo's been proposing.
It depends on the case.
Like most others, Yahoo's website is only available through IPv4. Thus, even computers that have IPv6 still use IPv4 to get to access Yahoo.
When they enable IPv6, computers which have IPv6 will try to use IPv6 to access Yahoo.
Computers which aren't compatible with IPv6 are actually fine: they'll just use IPv4 like always.
The problem here is that there's a large number of computers which (thinks) it has IPv6 connectivity but actually, the IPv6 connectivity is broken. Thus, when Yahoo enabled IPv6 on their site, these computers will have trouble getting to Yahoo.
The reasons vary.
One reason are computers that sit on a network that has IPv6 for internal use but doesn't have IPv6 internet connection.
Another reason (or set of reasons) is that the computer has an IPv6 internet connection but, somewhere between the computer and Yahoo (ISP, etc, etc) , it's broken.
Because the existing route between Pollegion and Faido imposes limits on both trains' speed and load.
The tunnel will not just reduce the distance, it will also allow the passenger trains to go faster and the freight trains to carry heavier loads.
It's a bit more complex than that.
They have been protected by law in their respective countries for a long (long) time. But these denominations could never been made as registered trademarks. In order to register something as trademark, it must not be in common use. Being mostly names of regions, these denominations were already in common use when the registered trademarks laws were created.
So, they had to be protected under a different legal scheme; which was never upheld in the rest of the world.
Actually, a bunch of them were protected *before* any registered trademarks were created. The Tokaj protected region was established in 1717, Chianti in 1730 and Port in 1756. Meanwhile, UK's Trademark Registration Act was only passed in 1875.
You're somewhat wrong.
In Europe, wine names such as "Tokaj", "Chianti", "Port", "Champagne" and many others have been trademarks bound, by law, to specific regions and types of grape and even production methods. Some of these parameters are so narrowly defined that winemakers from those regions sometimes opt to skip the protected trademark in order to have more freedom in their wine making.
Some of these legal protection schemes go back to the 18th century: Chianti in 1717, Tokaj in 1730, Port in 1756.
Champagne is much more recent, only being legally defined in 1927.
That said, I really do understand that citizens from non-European countries, who are quite accustomed to use these words in a more generic sense, think it's wrong to suddenly take these words from the public domain and make them into protected trademarks.