Forgot your password?

Comment: Re:Germany not responsible for call recordings (Score 1) 170

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

Comment: Re:Is this what the masses want (Score 1) 371

by matfud (#47632415) Attached to: Oracle Hasn't Killed Java -- But There's Still Time

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.

Comment: Re:Service in exchange for a free modem? (Score 1) 224

by matfud (#47631561) Attached to: The Hidden Cost of Your New Xfinity Router

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.

Comment: Re:Service in exchange for a free modem? (Score 1) 224

by matfud (#47629693) Attached to: The Hidden Cost of Your New Xfinity Router

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.

Comment: Re:Texas? (Score 1) 172

by matfud (#47504271) Attached to: California In the Running For Tesla Gigafactory

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)

Comment: Re:So who pays who? (Score 1) 234

by matfud (#47503753) Attached to: Verizon Boosts FiOS Uploads To Match Downloads

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.

At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.