Uh, no. By default all your internal addresses will be blocked by the firewall on your router, so you will still have to enable them manually. Even though NAT will no longer be necessary, nobody should be leaving access opened by default. Security is done in layers. Blocking all external access to hosts that do not need to be accessed is one such obvious layer.
Well, singleton is useful, if only because it is the only way to implement the application object right. Doing it as a singleton allows access from outside the object, handles constructor exceptions, and ensures the destructor always gets called. Making the app object into anything else is bad:
If the app object is a global variable, you can not have exceptions in its constructor; terminate always gets called. Also, you do not get to control initialization order, so if you have any other global objects, they may or may not be initialized before it.
If the app object is a local variable in main, you can not get a pointer to it from anywhere else (and you commonly need to). The second problem is that the destructor will not be called if someone uses exit() (signal handler) or terminate() (some EH problem), causing many problems of resource leaks if the app object is the root of your object tree, as is often the case.
If the app object is a static variable in main, that solves the exit() problem, but you still need to set a global pointer to access it.
Making the app object a singleton, first called from main in a try block, avoids all of the above problems.
When you use laws to advance your agenda, you will find that the effects are not what you intended. These "good guys" appear to believe that enforcing the GPL would result in more mobile devices with all software on them open sourced. But that, of course, isn't going to happen. If a company does not want to release the source code now, it will not release the source code in the face of legal sanctions either. It will simply stop shipping the product. Then it will purge all GPL software from any future devices. Linux is not the only OS available, you know. Thus the end result of GPL enforcement is not more open source devices, but fewer. It is true that none of them will be "stealing" the work of GPL programmers, but is that really of any concern to anybody but them? The result for users is fewer available choices, each running on a proprietary OS with weird UIs. Is that what you are really after?
the vast majority of licensed bands are still the age old single peak and often at insane output powers
I wouldn't call a few kW insane. Only the largest transmitters in the world go into the megawatt range; the vast majority are things like wifi, which are small and weak, at They are looking for aliens who have set up multi-Gigawatt transmitters all over their planet, just like we have.
You obviously don't know much about transmitters. There are no multigigawatt transmitters anywhere in the world. The most powerful transmitter in the world is the Roumoules transmitter in France, which outputs 1.4MW, three orders of magnitude less than you think. It is notable that only its longwave broadcasts can be heard past 100km, because those reflect off the ionosphere. At night, the medium waves can do that too and so can be heard farther.
Notice that most of that radiated power will be reflected from the ionosphere and won't even make it as far as Earth's orbit. But for argument's sake, let's assume a full half of the signal makes it through. The antenna is somewhat directional, though the wikipedia article does not specify the beam width. Let's be generous and say it's a cone 30 degrees wide.
This cone will form a moving beam across the sky as the Earth rotates. A 30 degree beam will illuminate any particular star in its path for 2 hours each day. The study in the article we're discussing listened only for 8 hours, which is too short to always catch it.
Even if the signal is not reflected from the atmosphere, it will be significantly attenuated. Let's say 1MW makes it through. Gliese 581 is 20 light years away, ~2e17m. The base of the radiated cone is 2e17*tan30=1e17. The area of the base is pi*1e17^2=3.75e34. 1MW/3.75e34m2 = 2.67e-29W/m2.
Minimum detectable signal with a 1kHz bandwidth is -144dBm of the 1mW reference signal. That's 4e-15W. As a dumb estimate, we can calculate that 1.5e14m2 of continuous antenna area would be necessary to receive such a signal. That's approximately equal to the cross section of the Earth.
Of course, that's if the signal can be received at all. At low levels like that electrons in the antenna are unlikely to absorb anything at all. The ground state energy, for example, is 13eV = 2e-18J, 11 orders of magnitude lower than the signal per square meter. I find it difficult to believe that any excitation can occur here.
Having no detectable radio emissions does not preclude possibility of a civilization. Our civilization's emissions are already mostly in spread-spectrum format, which is by design indistinguishable from noise unless you know the encryption key. The transmitters we do have usually do not radiate omnidirectionally; that would be wasteful. Antennas are designed to cover the intended audience and minimize leakage outside of it, which makes detecting their radiation unlikely at any appreciable distance.
Futhermore, natural inverse square weakening of the signal makes the signal fade into the background before leaving the solar system anyway. Our TV and radio transmitters are not going to be heard outside the solar system. It is no coincidence that our satellites communicate with highly directional dishes. Directed signals are the only ones that will make it to the next star, so what SETI is really looking for is aliens who are actively broadcasting toward Earth. I don't know why they would be doing such a dumb thing, but who knows, maybe they are a not-too-intelligent life.
Great. Now every website hacking attempt would be called "going rogue". All "roguelike" discussions will be censored and prosecuted. And God help you if you are found in possession of a certain amulet...
Well, duh! You're using the 32-bit version, missing out on half the bits. If you want all the bits to work, install the 64-bit version, like any sane person would.
The law does not work this way. You can't just suspend law enforcement because too many things that depend on breaking the law would stop working. The lawful answer is always to do the right thing, and if you have to stop billions of dollars' worth of illegal activity, well, tough. I am not, of course, arguing that this is a good thing for civilization, but "too big to fail" must never be allowed as an excuse for criminal activity.
> this device was quite much copied from Nokia's symbian phones
Even though we have remote controls today, and clicking on the article link no longer requires you to get your ass out of your chair, you can still make a fool of yourself by being too lazy to read it and discover that the first remote control was invented in 1955, long before there was Symbian, or mobile phones.
Re:Most programs don't need a 64-bit address space
on
Linux 3.4 Released
·
· Score: 1
Although 64 bit programs also have to load libraries, those are shared among all the other programs. Since your 32 bit program is alone, all its libraries are not shared. xterm, for example, loads 6M worth of libraries, all of which will be shared with any other X application. Only 1.6M is used for runtime data. If you were to compile a 32 bit xterm and run it on the same machine, it will load an additional 6M of 32 bit libraries, increasing the amount of unshareable memory from 1.6M to 6M+1.6M, a fivefold increase.
Actually, the main problem with web pages is the current fad of using div background images as ui elements. "Use my colors" in Firefox turns off all backgrounds, and while that is indeed what I want, the UIs break. The correct solution, of course, is to use the img tag for images that are part of page content. Displaying backgrounds is supposed to be optional and any web designer relying on them for displaying content is doing it wrong.
There are a lot of people in the world who have sensitive eyes. A lot more than the blind. And still there is a lot of software that uses the black-text-on-white-background color scheme. Of all the possible choices, this is the one that causes the worst eyestrain. So if you are a software developer, take pity on hurting and watering eyes and allow us to use a darker color scheme. Windows Aero, I'm (not) looking at you!
Re:Most programs don't need a 64-bit address space
on
Linux 3.4 Released
·
· Score: 1
When you talk about space savings due to use of 32 bit pointers, you forget that a 32 bit program running on a 64 bit system will need to load all 32 bit libraries, the size of which greatly exceeds the amount of whatever savings you may or may not achieve. I'd say that most programs don't need to be 32 bit, and should only be compiled for 32 bit only if there is a substantial measurable performance gain. Otherwise, it's nothing but premature optimization, which usually does more harm than good.
One huge benefit of using x86_64 for everything is that it is now the only desktop platform you need to support. Mobile apps are on ARM, but desktops are all x86_64. Having a common binary format that works on every machine saves a lot of work for developers and should allow Linux finally get some good commercial software.
Using x32 is simply not worthwhile. Maybe there are a few programs out there that will benefit, but I have not seen a single one mentioned or any benchmarks listed. People just assume that using larger pointers will make a program slower, even though today's programs are so bloated, any increase in size would be an insignificant drop in an ocean. Put up benchmarks, or use x86_64!
In Russia, back in the days of USSR, all letters had to be sent in special envelopes upon which you had to trace machine-readable destination code in specially provided boxes. No code - no delivery. And in the US, the supposed birthplace of computing and internet, letters still have no required machine-readable codes (at least) 30 years after the USSR had them.
Because of whom you are asking. When you ask the government to solve your problem, the government can only offer solutions it can implement - the ones in its job description. That job includes passing laws, collecting taxes, and maintaining the military. So why are you surprized when the help it offers you includes doing its job?
Wouldn't these miss the case of negative indices? rangeCheck(5,-3,2) will not throw. Now, a C++ programmer would use unsigned types, as everyone ought to do unless the variable can be negative, but this is Java, so I guess you're screwed;)
Slashdot Mirror
> no more fiddling with port forwarding
Uh, no. By default all your internal addresses will be blocked by the firewall on your router, so you will still have to enable them manually. Even though NAT will no longer be necessary, nobody should be leaving access opened by default. Security is done in layers. Blocking all external access to hosts that do not need to be accessed is one such obvious layer.
I am so glad that KDE has finally discovered that new "beta testing" thing. It is sure to improve the quality of future releases.
Linux games that try to make use of advanced features of OpenGL often suffer from driver bugs.
Well, singleton is useful, if only because it is the only way to implement the application object right. Doing it as a singleton allows access from outside the object, handles constructor exceptions, and ensures the destructor always gets called. Making the app object into anything else is bad:
If the app object is a global variable, you can not have exceptions in its constructor; terminate always gets called. Also, you do not get to control initialization order, so if you have any other global objects, they may or may not be initialized before it.
If the app object is a local variable in main, you can not get a pointer to it from anywhere else (and you commonly need to). The second problem is that the destructor will not be called if someone uses exit() (signal handler) or terminate() (some EH problem), causing many problems of resource leaks if the app object is the root of your object tree, as is often the case.
If the app object is a static variable in main, that solves the exit() problem, but you still need to set a global pointer to access it.
Making the app object a singleton, first called from main in a try block, avoids all of the above problems.
A much more interesting conclusion of this study is that 99.2% of social network users will do anything their friends would tell them to do.
When you use laws to advance your agenda, you will find that the effects are not what you intended. These "good guys" appear to believe that enforcing the GPL would result in more mobile devices with all software on them open sourced. But that, of course, isn't going to happen. If a company does not want to release the source code now, it will not release the source code in the face of legal sanctions either. It will simply stop shipping the product. Then it will purge all GPL software from any future devices. Linux is not the only OS available, you know. Thus the end result of GPL enforcement is not more open source devices, but fewer. It is true that none of them will be "stealing" the work of GPL programmers, but is that really of any concern to anybody but them? The result for users is fewer available choices, each running on a proprietary OS with weird UIs. Is that what you are really after?
And they say there is no innovation in America...
I wouldn't call a few kW insane. Only the largest transmitters in the world go into the megawatt range; the vast majority are things like wifi, which are small and weak, at
They are looking for aliens who have set up multi-Gigawatt transmitters all over their planet, just like we have.
You obviously don't know much about transmitters. There are no multigigawatt transmitters anywhere in the world. The most powerful transmitter in the world is the Roumoules transmitter in France, which outputs 1.4MW, three orders of magnitude less than you think. It is notable that only its longwave broadcasts can be heard past 100km, because those reflect off the ionosphere. At night, the medium waves can do that too and so can be heard farther.
Notice that most of that radiated power will be reflected from the ionosphere and won't even make it as far as Earth's orbit. But for argument's sake, let's assume a full half of the signal makes it through. The antenna is somewhat directional, though the wikipedia article does not specify the beam width. Let's be generous and say it's a cone 30 degrees wide.
This cone will form a moving beam across the sky as the Earth rotates. A 30 degree beam will illuminate any particular star in its path for 2 hours each day. The study in the article we're discussing listened only for 8 hours, which is too short to always catch it.
Even if the signal is not reflected from the atmosphere, it will be significantly attenuated. Let's say 1MW makes it through. Gliese 581 is 20 light years away, ~2e17m. The base of the radiated cone is 2e17*tan30=1e17. The area of the base is pi*1e17^2=3.75e34. 1MW/3.75e34m2 = 2.67e-29W/m2.
Minimum detectable signal with a 1kHz bandwidth is -144dBm of the 1mW reference signal. That's 4e-15W. As a dumb estimate, we can calculate that 1.5e14m2 of continuous antenna area would be necessary to receive such a signal. That's approximately equal to the cross section of the Earth.
Of course, that's if the signal can be received at all. At low levels like that electrons in the antenna are unlikely to absorb anything at all. The ground state energy, for example, is 13eV = 2e-18J, 11 orders of magnitude lower than the signal per square meter. I find it difficult to believe that any excitation can occur here.
Having no detectable radio emissions does not preclude possibility of a civilization. Our civilization's emissions are already mostly in spread-spectrum format, which is by design indistinguishable from noise unless you know the encryption key. The transmitters we do have usually do not radiate omnidirectionally; that would be wasteful. Antennas are designed to cover the intended audience and minimize leakage outside of it, which makes detecting their radiation unlikely at any appreciable distance.
Futhermore, natural inverse square weakening of the signal makes the signal fade into the background before leaving the solar system anyway. Our TV and radio transmitters are not going to be heard outside the solar system. It is no coincidence that our satellites communicate with highly directional dishes. Directed signals are the only ones that will make it to the next star, so what SETI is really looking for is aliens who are actively broadcasting toward Earth. I don't know why they would be doing such a dumb thing, but who knows, maybe they are a not-too-intelligent life.
I'm sure the NSA would love to have a mathematician.
Great. Now every website hacking attempt would be called "going rogue". All "roguelike" discussions will be censored and prosecuted. And God help you if you are found in possession of a certain amulet...
Well, duh! You're using the 32-bit version, missing out on half the bits. If you want all the bits to work, install the 64-bit version, like any sane person would.
The law does not work this way. You can't just suspend law enforcement because too many things that depend on breaking the law would stop working. The lawful answer is always to do the right thing, and if you have to stop billions of dollars' worth of illegal activity, well, tough. I am not, of course, arguing that this is a good thing for civilization, but "too big to fail" must never be allowed as an excuse for criminal activity.
> this device was quite much copied from Nokia's symbian phones
Even though we have remote controls today, and clicking on the article link no longer requires you to get your ass out of your chair, you can still make a fool of yourself by being too lazy to read it and discover that the first remote control was invented in 1955, long before there was Symbian, or mobile phones.
Although 64 bit programs also have to load libraries, those are shared among all the other programs. Since your 32 bit program is alone, all its libraries are not shared. xterm, for example, loads 6M worth of libraries, all of which will be shared with any other X application. Only 1.6M is used for runtime data. If you were to compile a 32 bit xterm and run it on the same machine, it will load an additional 6M of 32 bit libraries, increasing the amount of unshareable memory from 1.6M to 6M+1.6M, a fivefold increase.
Now all we need is for someone to use Emacsy to implement vi. That would be totally mindblowing!
The same thing that will happen to Windows 8.
Actually, the main problem with web pages is the current fad of using div background images as ui elements. "Use my colors" in Firefox turns off all backgrounds, and while that is indeed what I want, the UIs break. The correct solution, of course, is to use the img tag for images that are part of page content. Displaying backgrounds is supposed to be optional and any web designer relying on them for displaying content is doing it wrong.
There are a lot of people in the world who have sensitive eyes. A lot more than the blind. And still there is a lot of software that uses the black-text-on-white-background color scheme. Of all the possible choices, this is the one that causes the worst eyestrain. So if you are a software developer, take pity on hurting and watering eyes and allow us to use a darker color scheme. Windows Aero, I'm (not) looking at you!
When you talk about space savings due to use of 32 bit pointers, you forget that a 32 bit program running on a 64 bit system will need to load all 32 bit libraries, the size of which greatly exceeds the amount of whatever savings you may or may not achieve. I'd say that most programs don't need to be 32 bit, and should only be compiled for 32 bit only if there is a substantial measurable performance gain. Otherwise, it's nothing but premature optimization, which usually does more harm than good.
One huge benefit of using x86_64 for everything is that it is now the only desktop platform you need to support. Mobile apps are on ARM, but desktops are all x86_64. Having a common binary format that works on every machine saves a lot of work for developers and should allow Linux finally get some good commercial software.
Using x32 is simply not worthwhile. Maybe there are a few programs out there that will benefit, but I have not seen a single one mentioned or any benchmarks listed. People just assume that using larger pointers will make a program slower, even though today's programs are so bloated, any increase in size would be an insignificant drop in an ocean. Put up benchmarks, or use x86_64!
In Russia, back in the days of USSR, all letters had to be sent in special envelopes upon which you had to trace machine-readable destination code in specially provided boxes. No code - no delivery. And in the US, the supposed birthplace of computing and internet, letters still have no required machine-readable codes (at least) 30 years after the USSR had them.
Damages: $15,000,000,000.00
User compensation: $2,100.00
Lawyer fees: $14,999,997,900.00
Because of whom you are asking. When you ask the government to solve your problem, the government can only offer solutions it can implement - the ones in its job description. That job includes passing laws, collecting taxes, and maintaining the military. So why are you surprized when the help it offers you includes doing its job?
Wouldn't these miss the case of negative indices? rangeCheck(5,-3,2) will not throw. Now, a C++ programmer would use unsigned types, as everyone ought to do unless the variable can be negative, but this is Java, so I guess you're screwed ;)