Many modern chips that have analog components have the analog supply and ground close to the pins used for the analog functions (for pretty obvious reasons)
You many no longer be worried about running a few extra digital datapaths to make the outside data bus be in order but you still need to seperate analog and digital functions and that limits the output pins they can use
With programs generally being much much larger many such optimisations can just be lost in the noise. In some domains it is still useful but even more difficult than it was in times gone by. Pipelining/OOE/register renaming and the multitude of processors with the same IS but remarkably different implementations, cache sizes/associativity/memory, memory size and connectivity How many cores per CPU and how do they share those caches and memory buses. How many independent memory banks per processor/chip (can change the cache miss time) Memory architectre and or federated levels of connectivity (on high processor # manchines) Operating systems can make it nigh on impossible to predict cache hits/misses as they premptively trash all your cache local code)
Just trying to optimize on modern proessors and OS's is stupidly difficult even if there were not so many variants. Still there can be significant gains sometimes (although that tends to be on small timescales relative to the OS task time. Sometime it is better to use performance libs and hope that whoever wrote them did it well:)
If you had read the article you would know that it is part of an effort to deconstruct the Z80 using optical information and yes they can see all the transistors although identifying them and thier function can be tricky as they were layed out by hand to minimise the space needed.
I have no connection to the project but reading some of the pages on the site are quite interesting if you are electronics minded.
If I remember correctly changing display modes mid scan was often done so that workbench could do things like display HAM images in windows. I think the OP may be talking about the "copper" which was a FSM with three states (MOVE, WAIT and SKIP) and a list of instructions to be processed when screen timing events occur. All three were used though and it was used for many things such as sprites and the above mentioned screen mode changes.
MOVE (put data in pretty much any register such as changing the location of a sprite to allow the sprite to be reused in another location) WAIT (wait for a screen event such as a pixel position.) SKIP (skip the next instruction in the copper list) An interesting thing that could also be done in change the screen mode so that the top part of the screen displays the game and the bottom in a different mode (colour deapth/resolution) to display the game controls
It is not as simple as saying "I'm free" and I would have liked to hear more about it.
I think the most amusing was yes scotland talking about the oil and gas available. Then the shetland Isles said if our vote goes no then what oil are you talking about. It is ours.:)
I thought that this was a really good point. If the isles had said fuck off to scotland then the exclusion zone would be much different. So who gets the oil?
The US is not legally allowed to record the secretary of state talking to anyone (snigger). So why do you think that someone would think that they are recording it? An why do you think that the person with the recording would necessarilly know that the recording was recorded by another agency anyway?
So who knows who is recording who and who has access to those recordings and who needs access to the recording and why they need to know who is talking to who and whether you should notify your chain of control that someone is talking to someone about something and which agency is interested in that something.
Secrecy is fun as nobody knows what anyone else is doing or should be doing:P
I have worked with large java codebases. They are generally a few versions behind the latest release. That is not a Java thing it occurs in all code. Updating legacy code (or even slightly old code) can be a real pain in the arse. You have to fully test all the changes on the new compiler/runtime and mistakes will be made. Strong typing can actually help here as refactoring can tell you a lot about it (try refactoring java 1.3 to 1.5 (generics) and you will see how much was skipped over and just plain odd when you try to give things strong types) And that is with java being remarkably backwards compatible (actually that is part of the problem as it does not require you to upgrade your code)
Moving up is not that hard but you end up with a lot of code that is old style and could be improved. Changing that takes money and time so often it is not done. There is a lot of code out there still on 1.3 (or 1.2) that still compiles and has to be bridged to best practices on 1.5, 1.7 And muh of it has no automated tests. It is painful but at least the compiler tends to tell you when you bugger up (a bit).
Do you think that other languages are immune to these problems? hee hee.
Ahh. Seems to be a US problem (and other parts of the world)
"Many cordless telephones and baby monitors in the United States and Canada use the 2.4 GHz frequency, the same frequency at which Wi-Fi standards 802.11b, 802.11g and 802.11n operate. This can cause a significant decrease in speed, or sometimes the total blocking of the Wi-Fi signal when a conversation on the phone takes place. There are several ways to avoid this though, some simple, and some more complicated."
A different question is can you call the device an interference source within your house as it will not do much unless someone is using it. If someone is using it then it hurts but then someone using wifi next door is just as likely to cause problems. (and most wifi can default to g(2.4Ghz) but if you are worried about data rates then you are probably not using that anymore.
I don't live in the US so Comcast is rather abstract for me. But I know I have over 20 access points visible and interfering with my wifi goodness visible from here.
Bluetooth, cordless keyboards, telephones etc. are not generally in the same spectrum as wifi so little to no issue there (and they are all low data rate) Your wifi in your home is going to be disrupted by others using wifi near by anyway (it is a shared medium). If you have people close enough to use your in home wifi then they likely are already degrading your service by being near and using any other wifi.
Not that I agree with comcast rolling this out without notifying people.
DU is only a slightly radioactive heavy metal. It is pretty safe and easy to handle. Sort of like lead is.
That is until you shoot it at someone and it burns and fragments and does all sorts of nasty stuff to spread itself around.:P (sorry I just had to add to your comment; in that is is mostly safe but as with most materials it depends on what you do with it)
California did have lots of oil and to some extent does but there are reasons why they do not want the crap load of problems it caused http://www.westernsun.us/wp-co...
For a company like L3 it won't matter much either way as the data providers that they link to the data consumers are spread around thier network and peers. So thier data haluage is probably fairly well balanced. Thier peering with consumer ISPs is highly biased but also distributed pretty well around thier network in most places.
Slashdot Mirror
Many modern chips that have analog components have the analog supply and ground close to the pins used for the analog functions (for pretty obvious reasons)
You many no longer be worried about running a few extra digital datapaths to make the outside data bus be in order but you still need to seperate analog and digital functions and that limits the output pins they can use
With programs generally being much much larger many such optimisations can just be lost in the noise. In some domains it is still useful but even more difficult than it was in times gone by.
Pipelining/OOE/register renaming and the multitude of processors with the same IS but remarkably different implementations, cache sizes/associativity/memory, memory size and connectivity
How many cores per CPU and how do they share those caches and memory buses.
How many independent memory banks per processor/chip (can change the cache miss time)
Memory architectre and or federated levels of connectivity (on high processor # manchines)
Operating systems can make it nigh on impossible to predict cache hits/misses as they premptively trash all your cache local code)
Just trying to optimize on modern proessors and OS's is stupidly difficult even if there were not so many variants. Still there can be significant gains sometimes (although that tends to be on small timescales relative to the OS task time. Sometime it is better to use performance libs and hope that whoever wrote them did it well :)
If you had read the article you would know that it is part of an effort to deconstruct the Z80 using optical information and yes they can see all the transistors although identifying them and thier function can be tricky as they were layed out by hand to minimise the space needed.
I have no connection to the project but reading some of the pages on the site are quite interesting if you are electronics minded.
If I remember correctly changing display modes mid scan was often done so that workbench could do things like display HAM images in windows.
I think the OP may be talking about the "copper" which was a FSM with three states (MOVE, WAIT and SKIP) and a list of instructions to be processed when screen timing events occur. All three were used though and it was used for many things such as sprites and the above mentioned screen mode changes.
MOVE (put data in pretty much any register such as changing the location of a sprite to allow the sprite to be reused in another location)
WAIT (wait for a screen event such as a pixel position.)
SKIP (skip the next instruction in the copper list)
An interesting thing that could also be done in change the screen mode so that the top part of the screen displays the game and the bottom in a different mode (colour deapth/resolution) to display the game controls
Maybe I missunderstood the OP?
Where is my +1 snigger vote?
It is not quite that simple as there is a fairly big movement in Argentina to reclaim the Islands.
Why? Who knows...
I must agree.
It is not as simple as saying "I'm free" and I would have liked to hear more about it.
I think the most amusing was yes scotland talking about the oil and gas available. Then the shetland Isles said if our vote goes no then what oil are you talking about. It is ours. :)
I may not agree with you but this person has set it up to hunt you down. Oh well that is slashdot.
I am tired of the pointless posts.
I thought that this was a really good point. If the isles had said fuck off to scotland then the exclusion zone would be much different. So who gets the oil?
All if and what haves but it amused me
Wales says We have sheep and .... fair point.
Learn why it is that way and how it mostly works.
A good idea? well probably not. It is not idealistic but also has stood the test of time (more or less)
Not easily as there is quite a lot of back and forth comunication over a very long period of time (up to multiple years) before a patent is granted.
If it requires an extra digit on a display it does.
But think of the jobs that the superfund remediation will bring to the area for decades to come /snark
Symptom does not mean what you think it does. It does not only mean indicators of a disease.
The US is not legally allowed to record the secretary of state talking to anyone (snigger). So why do you think that someone would think that they are recording it? An why do you think that the person with the recording would necessarilly know that the recording was recorded by another agency anyway?
So who knows who is recording who and who has access to those recordings and who needs access to the recording and why they need to know who is talking to who and whether you should notify your chain of control that someone is talking to someone about something and which agency is interested in that something.
Secrecy is fun as nobody knows what anyone else is doing or should be doing :P
I have worked with large java codebases. They are generally a few versions behind the latest release.
That is not a Java thing it occurs in all code.
Updating legacy code (or even slightly old code) can be a real pain in the arse. You have to fully test all the changes on the new compiler/runtime and mistakes will be made. Strong typing can actually help here as refactoring can tell you a lot about it (try refactoring java 1.3 to 1.5 (generics) and you will see how much was skipped over and just plain odd when you try to give things strong types)
And that is with java being remarkably backwards compatible (actually that is part of the problem as it does not require you to upgrade your code)
Moving up is not that hard but you end up with a lot of code that is old style and could be improved. Changing that takes money and time so often it is not done. There is a lot of code out there still on 1.3 (or 1.2) that still compiles and has to be bridged to best practices on 1.5, 1.7 And muh of it has no automated tests. It is painful but at least the compiler tends to tell you when you bugger up (a bit).
Do you think that other languages are immune to these problems? hee hee.
Ahh. Seems to be a US problem (and other parts of the world)
"Many cordless telephones and baby monitors in the United States and Canada use the 2.4 GHz frequency, the same frequency at which Wi-Fi standards 802.11b, 802.11g and 802.11n operate. This can cause a significant decrease in speed, or sometimes the total blocking of the Wi-Fi signal when a conversation on the phone takes place. There are several ways to avoid this though, some simple, and some more complicated."
A different question is can you call the device an interference source within your house as it will not do much unless someone is using it. If someone is using it then it hurts but then someone using wifi next door is just as likely to cause problems. (and most wifi can default to g(2.4Ghz) but if you are worried about data rates then you are probably not using that anymore.
I don't live in the US so Comcast is rather abstract for me. But I know I have over 20 access points visible and interfering with my wifi goodness visible from here.
Bluetooth, cordless keyboards, telephones etc. are not generally in the same spectrum as wifi so little to no issue there (and they are all low data rate)
Your wifi in your home is going to be disrupted by others using wifi near by anyway (it is a shared medium). If you have people close enough to use your in home wifi then they likely are already degrading your service by being near and using any other wifi.
Not that I agree with comcast rolling this out without notifying people.
Sir Holo,
Thanks for the book reference. It sounded interesting so I just bought a copy.
Steve Fosset was one of the pilots of Perlan 1
DU is only a slightly radioactive heavy metal. It is pretty safe and easy to handle. Sort of like lead is.
That is until you shoot it at someone and it burns and fragments and does all sorts of nasty stuff to spread itself around. :P
(sorry I just had to add to your comment; in that is is mostly safe but as with most materials it depends on what you do with it)
California did have lots of oil and to some extent does but there are reasons why they do not want the crap load of problems it caused
http://www.westernsun.us/wp-co...
For a company like L3 it won't matter much either way as the data providers that they link to the data consumers are spread around thier network and peers. So thier data haluage is probably fairly well balanced. Thier peering with consumer ISPs is highly biased but also distributed pretty well around thier network in most places.
Should have been
"unlike silver, copper and aluminium"
all are good conductors but the oxides are not so none are good for push fit connections.
Hurm yes I must be a dwarf.
How does it go?
Gold gold gold
Gold gold gold gold
gold gold Au Au
GOLD
TP got it right