Add to it the arcing that occurs from bad insulators on the grid - sometimes they cause a lot of RFI - and they are local. Just go out and listen to a high voltage power line when the weather is humid - there's usually a buzzing on the line caused by surface currents on the insulators.
The electric noise would only be useful for a very rough approximation of where someone is located and largely depend on interference on the grid. At best you may find the county or town where someone is located, but it won't necessarily be conclusive since it's important to also match that to the correct time slot.
The noise brought in as location information in CSI etc. is often depending on more distinct noises that are well-known. A subway station has one set of specific noises, a harbor has a different set. Sometimes among the general noises there are some distinct parts that can help pinpointing.
But if someone records the noises of an out of place location and then use that as a background then it will throw investigation off track. It's impossible to realize straight away that a certain noise is good or misleading unless a repetitive pattern is heard because the noise is looped.
There are no inventions in operating system UIs since the release of XP, right now we are suffering one big experiment that seems to be led by a horde of drunken chickens...
Doesn't help when they move around whenever you resize. They are never in the same place, and they never look the same which forces me to search for them every time. Sometimes only resort is to maximize the window on the largest screen I have to find what I'm after.
Especially since the ribbon changes shape and size of the icons "at will" whenever you change something or resize the window. Ulcers and dandruff is the result.
In most of the world the cars and the fuel is taxed enough to not only cover their own costs (roads etc.) but also feed into other parts of the big government sinkhole.
Not only Atlanta but essentially every major city uses those card systems, and almost everywhere the security is broken.
The only thing that stops it from making the news is that it's silenced - the public transport companies don't want the information to get leaked that they use a broken system.
Blame the spammers that fake the senders. Microsoft is a popular faked sender, and then the junk mail filters throws away the mails and nobody sees the patch info mail.
If I want to view/edit random code I go for VIM as long as it's a small scale action. If I'm going to work with larger scale projects in C++ or Java it's Eclipse. For hash-coding in C# it's Visual studio.
I gave up on Emacs 20 years ago because it was never as default on the systems I was on then and it was too much of a hassle to build it on them.
If the land you use consists of roof tops then it's not consuming any precious space.
Solar is no replacement for existing energy, it's a supplement. In the price for nuclear energy plants you must also consider the cost not only for construction but also to take care of the remainders when the plant is no longer in service, some material is "hot" for millenia - and it's not only the fuel.
There are even a few warnings that at least with gcc won't show up unless you use the plain "-W" flag, and even cases where they won't show up at the "-O0" level but only at "-O2". And there are a few that you have to enable explicitly.
Add a run of "splint" and/or cppcheck to make sure that the code is as good as it can be. Then execute the binary under Valgrind to make sure that there are no memory leaks. The remaining errors should be those caused by a bad system design rather than plain coding errors. In a few cases the errors might be in third party runtime libraries, but that's hard to protect against and outside the scope here.
It's not a question of turning off warnings, it's a question of correcting the code to get rid of the warnings.
If you turn off the warnings you turn off the warnings for all occurrences in the code, and that is really a dangerous thing to do. In most cases warnings are harmless but in some cases the warning is an important explanation to why something behaves in an erratic way.
Ignoring compiler warnings is stupid, dangerous and can cause serious problems to become hidden.
The most important thing is not to avoid that the build fails but to avoid distributing software packages that can't be built.
However if something can't be built due to a mistake it's often easy to find and correct. The big problems are often not that visible and it can take a while to figure them out.
What really grinds my gears is that people release source code that is possible to build, but so full of compiler warnings that you can't be certain that it's going to work as intended.
What Solar can do is to lower the need of power from regular power plants, it will never replace them.
And if you have solar panels over a whole country there will often be some part that has incoming sunshine or at least some light. Add to it that when the sun shines it's when you run the air conditioning - and that's a power hungry system, so compensating for the AC units that you run by using solar is not causing any bad side effects.
Some people may not afford to work less because they need the extra income from a 50 hours workweek.
Of course - this means either that they try to have a higher living standard than what's possible for a normal salary or that the salary is too low.
However there are demands for competent people, the problem is to find competent people because a lot of the unemployed can't even swing a hammer or do basic math - much less do engineering math. It doesn't matter that you are an expert in the works of Van Gogh or can play xylophone with your feet - only a few can live on that.
The question is - do you always need a parallel tasking software? Most tasks are bread&butter tasks, no need to chew them up. Put your energy into the few things that do need to be broken up.
But mostly it's a "hen and egg" problem - can't do multi-core software since there aren't enough serious multi-core machines, or the owners in software companies don't see a benefit in it.
Boeing still builds the 737...
Add to it the arcing that occurs from bad insulators on the grid - sometimes they cause a lot of RFI - and they are local. Just go out and listen to a high voltage power line when the weather is humid - there's usually a buzzing on the line caused by surface currents on the insulators.
The electric noise would only be useful for a very rough approximation of where someone is located and largely depend on interference on the grid. At best you may find the county or town where someone is located, but it won't necessarily be conclusive since it's important to also match that to the correct time slot.
The noise brought in as location information in CSI etc. is often depending on more distinct noises that are well-known. A subway station has one set of specific noises, a harbor has a different set. Sometimes among the general noises there are some distinct parts that can help pinpointing.
But if someone records the noises of an out of place location and then use that as a background then it will throw investigation off track. It's impossible to realize straight away that a certain noise is good or misleading unless a repetitive pattern is heard because the noise is looped.
There are no inventions in operating system UIs since the release of XP, right now we are suffering one big experiment that seems to be led by a horde of drunken chickens...
Brings up to me that I think that "First Contact" was the best movie among the Star Trek movies.
Doesn't help when they move around whenever you resize. They are never in the same place, and they never look the same which forces me to search for them every time. Sometimes only resort is to maximize the window on the largest screen I have to find what I'm after.
Especially since the ribbon changes shape and size of the icons "at will" whenever you change something or resize the window. Ulcers and dandruff is the result.
Who cares? He has had his 15 minutes of fame.
In most of the world the cars and the fuel is taxed enough to not only cover their own costs (roads etc.) but also feed into other parts of the big government sinkhole.
Not only Atlanta but essentially every major city uses those card systems, and almost everywhere the security is broken.
The only thing that stops it from making the news is that it's silenced - the public transport companies don't want the information to get leaked that they use a broken system.
The problem I encountered last time I tried that I was offered two options, either a phone packaged with it or to lock my private phone to that SIM.
It's a problem since you need to find a vendor that carries those.
Blame the spammers that fake the senders. Microsoft is a popular faked sender, and then the junk mail filters throws away the mails and nobody sees the patch info mail.
If I want to view/edit random code I go for VIM as long as it's a small scale action. If I'm going to work with larger scale projects in C++ or Java it's Eclipse. For hash-coding in C# it's Visual studio.
I gave up on Emacs 20 years ago because it was never as default on the systems I was on then and it was too much of a hassle to build it on them.
Just be aware that your job resume may be on the bottom half when you decide to change employment.
If the land you use consists of roof tops then it's not consuming any precious space.
Solar is no replacement for existing energy, it's a supplement. In the price for nuclear energy plants you must also consider the cost not only for construction but also to take care of the remainders when the plant is no longer in service, some material is "hot" for millenia - and it's not only the fuel.
We are Tornado. Resistance is futile, you will be assimilated.
There are even a few warnings that at least with gcc won't show up unless you use the plain "-W" flag, and even cases where they won't show up at the "-O0" level but only at "-O2". And there are a few that you have to enable explicitly.
Add a run of "splint" and/or cppcheck to make sure that the code is as good as it can be. Then execute the binary under Valgrind to make sure that there are no memory leaks. The remaining errors should be those caused by a bad system design rather than plain coding errors. In a few cases the errors might be in third party runtime libraries, but that's hard to protect against and outside the scope here.
It's not a question of turning off warnings, it's a question of correcting the code to get rid of the warnings.
If you turn off the warnings you turn off the warnings for all occurrences in the code, and that is really a dangerous thing to do. In most cases warnings are harmless but in some cases the warning is an important explanation to why something behaves in an erratic way.
Ignoring compiler warnings is stupid, dangerous and can cause serious problems to become hidden.
The most important thing is not to avoid that the build fails but to avoid distributing software packages that can't be built.
However if something can't be built due to a mistake it's often easy to find and correct. The big problems are often not that visible and it can take a while to figure them out.
What really grinds my gears is that people release source code that is possible to build, but so full of compiler warnings that you can't be certain that it's going to work as intended.
What Solar can do is to lower the need of power from regular power plants, it will never replace them.
And if you have solar panels over a whole country there will often be some part that has incoming sunshine or at least some light. Add to it that when the sun shines it's when you run the air conditioning - and that's a power hungry system, so compensating for the AC units that you run by using solar is not causing any bad side effects.
Anyone that noted that the article actually was from 2012???
Some people may not afford to work less because they need the extra income from a 50 hours workweek.
Of course - this means either that they try to have a higher living standard than what's possible for a normal salary or that the salary is too low.
However there are demands for competent people, the problem is to find competent people because a lot of the unemployed can't even swing a hammer or do basic math - much less do engineering math. It doesn't matter that you are an expert in the works of Van Gogh or can play xylophone with your feet - only a few can live on that.
I'd rather crowdfund a Star Trek movie - at least there are some nice ones already made that way.
The question is - do you always need a parallel tasking software? Most tasks are bread&butter tasks, no need to chew them up. Put your energy into the few things that do need to be broken up.
But mostly it's a "hen and egg" problem - can't do multi-core software since there aren't enough serious multi-core machines, or the owners in software companies don't see a benefit in it.