That's not particularly meaningful, given that totalitarian regimes are to the UN as the tea party is to the US Congress. They've got enough votes to accomplish a lot of things that don't make sense and they vote in blocks.
Data structures, OSI network model, big O notation, all these things are as relevant today as they were decades ago. University isn't vocational school.
I rode on the articulated subway in Berlin this year during a weekend, including early Saturday morning. Lots of partiers, no vomit. Maybe Canadians drink like teenagers?:)
What ship has ever been invincible? I think the idea here is that between stealth for defense and enhanced radar and electronics for offense, this ship will shoot first.
Until the oversubscribed DSLAM starts dropping packets at 3PM. Jitter and latency will be worse as well. T1 is dedicated bandwidth to the router or switch.
We've got 100Gbps optics live on our network. Granted, even the Coherent stuff is broken down into two polarized carriers or two different wavelength carriers that are modulated at 50Gbps using QPSK. It's expensive, but it's cheaper than the equivalent number of 10Gbps circuits.
You probably work with two telcom companies to make sure your website and/or company has network access
As someone who works in telecom, this is not as good an idea as you think it is. You're almost always better off buying diverse/protected service from one company than trying to use 'carrier diversity' to save your butt. Very often both telecom companies will be using the same fiber, or leasing transport capacity from one another. Example: You buy an unprotected Ethernet Private Line from Level 3, and then turn around and buy another unprotected EPL from XO. They're both unprotected linear transport, but what are the odds both carriers will have an outage at once? The answer, 100%. XO uses Level3 fiber everywhere.
This is essentially how hardware NTP servers work I believe, with the hardware directly supplying the timestamp information as the packet is assembled.
I don't think that really counts as true ad hoc networking. There's no layer 3 routing accounted for there, so the gateway and subnet are pretty much fixed, and you've got your 'client' devices acting as wi-fi repeaters. If ad hoc networking is the flying car of the network world, this would be a hovercraft.
You're talking about Ad Hoc networking there. People have been working on it forever, but so far it's never made it into a production environment that I know of.
The problem is the solution proposed isn't going to do anything to reduce costs or improve quality. It just makes the existing overpriced health insurance mandatory, without reforming the issues that cause the care to be overpriced and lower quality.
He probably means obfuscated, where all the variable and method names are replaced with gibberish. The other way to do it would be to have a small shell javascript that translates and runs a payload of what is apparently gibberish, so that it's not quite as trivial as a 'show source' to see what naughty business is being done.
Some towers can be microwave links, but those links are going to have to home back to another tower that is fiber or copper fed. Even then you are hurting your ability to run LTE base stations at those microwave towers.
I would agree that you can't generally say "1 HP-UX server can always be replaced by 1 Linux server", but I don't think it's a stretch to say "1 HP-UX server that isn't doing anything that can't be ported to Windows, could be even more easily replaced by Linux". Also the fact that they multiplied their hardware footprint by 8 is a pretty good indication that Windows wasn't a good fit for whatever application they were needing.
Slashdot Mirror
That's a fairly modern distiction. For decades the progression was Single Action - Double Action - Automatic. I still refer to "revolver vs automatic"
It's going to be hard not to notice the person staring into space and drooling.
That's not particularly meaningful, given that totalitarian regimes are to the UN as the tea party is to the US Congress. They've got enough votes to accomplish a lot of things that don't make sense and they vote in blocks.
Cheap power is profitable power for the guys that own factories, foundries, datacenters, etc.
Still more deaths than Fukushima though.
Data structures, OSI network model, big O notation, all these things are as relevant today as they were decades ago. University isn't vocational school.
Legal drinking age in Germany is 16, try again.
I rode on the articulated subway in Berlin this year during a weekend, including early Saturday morning. Lots of partiers, no vomit. Maybe Canadians drink like teenagers? :)
What ship has ever been invincible? I think the idea here is that between stealth for defense and enhanced radar and electronics for offense, this ship will shoot first.
Until the oversubscribed DSLAM starts dropping packets at 3PM. Jitter and latency will be worse as well. T1 is dedicated bandwidth to the router or switch.
We've got 100Gbps optics live on our network. Granted, even the Coherent stuff is broken down into two polarized carriers or two different wavelength carriers that are modulated at 50Gbps using QPSK. It's expensive, but it's cheaper than the equivalent number of 10Gbps circuits.
You probably work with two telcom companies to make sure your website and/or company has network access
As someone who works in telecom, this is not as good an idea as you think it is. You're almost always better off buying diverse/protected service from one company than trying to use 'carrier diversity' to save your butt. Very often both telecom companies will be using the same fiber, or leasing transport capacity from one another. Example: You buy an unprotected Ethernet Private Line from Level 3, and then turn around and buy another unprotected EPL from XO. They're both unprotected linear transport, but what are the odds both carriers will have an outage at once? The answer, 100%. XO uses Level3 fiber everywhere.
This is essentially how hardware NTP servers work I believe, with the hardware directly supplying the timestamp information as the packet is assembled.
I don't think that really counts as true ad hoc networking. There's no layer 3 routing accounted for there, so the gateway and subnet are pretty much fixed, and you've got your 'client' devices acting as wi-fi repeaters. If ad hoc networking is the flying car of the network world, this would be a hovercraft.
Yes, I can't think of too many applications for copper/fiber ad hoc networking.
You're talking about Ad Hoc networking there. People have been working on it forever, but so far it's never made it into a production environment that I know of.
The problem is the solution proposed isn't going to do anything to reduce costs or improve quality. It just makes the existing overpriced health insurance mandatory, without reforming the issues that cause the care to be overpriced and lower quality.
I especially like the way it was +5 before you posted this, and now it's +1.
He probably means obfuscated, where all the variable and method names are replaced with gibberish. The other way to do it would be to have a small shell javascript that translates and runs a payload of what is apparently gibberish, so that it's not quite as trivial as a 'show source' to see what naughty business is being done.
Some towers can be microwave links, but those links are going to have to home back to another tower that is fiber or copper fed. Even then you are hurting your ability to run LTE base stations at those microwave towers.
Human drivers are far short of 99.999999% reliable, so I say hurry it up even if they're at Five Eights reliability...
The shock value isn't the problem, the number of casualties and the proportion of civilian casualties is the problem.
I would agree that you can't generally say "1 HP-UX server can always be replaced by 1 Linux server", but I don't think it's a stretch to say "1 HP-UX server that isn't doing anything that can't be ported to Windows, could be even more easily replaced by Linux". Also the fact that they multiplied their hardware footprint by 8 is a pretty good indication that Windows wasn't a good fit for whatever application they were needing.
Because instead of replacing 1 HP-UX server with 8 Windows servers, it could have been replaced by 1 Linux server.
If it's on nasa.gov that's a pretty good start.