He deserved it.
He deserved it.
Online users brush aside weightist comment, just happy to be noticed.
Sorry. Couldn't resist.
Older jacks may be terminated with too much untwisted wire at the end and the traces to the pins might not be as crosstalk-free as they could. YMMV.
For 1G the answer has always been only change the jack out if there are problems with the connection, because usually it's not needed. For this, who knows?
But even though connectors "rated" for higher speeds are a bit on the pricey side, this cost pales in comparision to runnng new cable... that's a lot more manpower.
The main drive for this is terminating wifi APs. Sometimes those connections are male on the AP side, depending on your local installer's druthers. (mostly we do jacks there too, but if we needed to eek a bit more performance out we could go male in most spots.) The male side is much less likely to have such issues.
Bah! Real geeks write in microcode
It actually can have quite profound effects. Take, for example, the ARM "only execute this instruction if this CPU bit is set nevertheless go to the next" feature. That allows you to carry boolean states down a whole list of instructions and pick and choose which ones run. Writing that same thing with jumps is quite more tedious. (Not to say ARM is necessarily a great instruction set.) Differences like that make two hand-coded ASM programs that do the same thing on different CPU families massively different on the whole, because the coder adapts to use the more convenient constructs and those constructs build off each other.
It also make compiler guts the sausage factory of computing, notwithstanding game code.
This is why you need to learn to write legibly. You know, sort of like handwriting, unless apparently, you are a doctor.
Basically the only way to detect intrusions on these systems is to have A) a characterization of their nominal protocol behavior including bandwidth usage patterns, connection/disconnection behaviors and other such information in addition to the basic port/service stuff. B) Have a list of the cloud servers they normally contact under standard operation, and C) Have regular automatically installed updates for A) and B) as the owner of the device screws with firmware and/or CDN contracts or the CDN itself makes changes and D) have some sort of alerting system that tells you when the nominal behavior pattern has been broken, but does not generate so many false alarms that you start to ignore said alerts and E) Have a device inline, sniffing, or on a mirror port capturing all traffic on the segment.
The big problem is C) because it requires a steady supply of manpower. Which is why companies pay more for the subscriptions on most NGFWs these days than they do for the hardware.
Pretty much precisely: we pay our diplomats/politicians/experts to take the best of the risky choices available. Just because they picked the best risks to take, does not mean they weren't risks. Then when some of the risks don't pan out well, we blame the diplomats/politicians/experts for taking the wrong risks in hindsight. Then we run to a "change agent" because well "what do we have to lose."
As a nation we often behave like one of those sad cases you hear about where some guy panicked during the recession, withdrew everything from his 401k, and bought into an Alpaca farm and ended up eating instant ramen for his entire retirement.
Problems with that idea:
1) It's probably not possible, and definitely not before many of these people suffer for (more) years in horrible living conditions
2) We get a lot smaller field to recruit future America-friendly arabic-passable intelligence assets from.
3) The "culture clash" is actually healthy and makes our society more robust long-term
4) We will have much less influence over the region due to having citizens with influence/interest in the region.
5) It's actually more expensive than adding taxpaying population.
While there are dupes a lot of those stories are actually different stories on the same subject.
It is important for consumers of recycling services to be informed of this (It would be more useful to
have a list of bona-fide recyclers) and not everyone reads every article in the feed, so it's not
a huge deal to have periodic reminders on the subject -- though, the actual dupes we could do well
without. In other words if we all just pointed a problem out once when it is first discovered and then
never mentioned it again, a lot less people would know about it.
Reminds me I have a cellar full of old PCBs to eventually figure out who to dispose it with.
Yeah but all the promo photos make them look like they have chiclets, so you have to really dig if you want to make sure you have real buttons. Personally I can't stand having these on screen -- I want to be able to have my thumb on the button, feel that it is in the right place, be prepared to press it, but not press it until/unless I actually want to. So, yet another reason Apple products have never had any appeal to me goes onto the pile.
Moreover once the anti-tobacco movement started, they often played the role of useful idiots to the national tobacco industry, by promoting an abstinence-only mentality that prevented the development of harm-reduction products. Also it won't be long before I have to scramble to find materials to roll non-radioactively-fertilized clove cigarettes because apparently anything flavored with cloves is attractive to children -- which you would not know from their attitudes towards the Christmas ham. Now, not that there isn't a big problem with the Indonesian tobacco industry and child farm labor/safety, but this will also ruin a significant portion of that country's economy, given traditional clove cigarettes is a principal export. Guess which country's tobacco industry hopes to gain customers from that move?
No, just to deplore them.
They probably got suckered into VPC and similar, guess what I dont care what they say all stacks share a single failure domain, dont get me wrong they are great but you need at least A+B stacks.
Yeah and reading release notes is an easy way to convince yourself that unless you need something like VPS or are cheesing license limits on a management platform, stacking should just be purged entirely from your configurations.
Smart IT people build data centers out of heterogeneous hardware and set it up to degrade gracefully when something fails.
That would always be a preferred model, if you have that kind of budget, but...
Blame the PHB/CTO not the hardware.
...I'd say the equipment vendors should share some of that blame. I don't work anywhere near the 5 9's area and even I find some really appalling feature bugs introduced on even routine patchlevel upgrades. Stuff like the combination of DHCP-snooping/arp-inspection/source-lockdown on a port, which is the right way to configure access ports for anyone who gives a flip about security in depth, suddenly blocking all traffic after an upgrade. This is in general availability software releases. Things that clearly should be getting tested in QA are being left up to the customers to discover. We're no longer customers but unpaid beta testers.
Now with an access switch I can make up for the slack and script up some tests and a test environment. With a core switch an operation like mine doesn't just have a test switch sitting around, so it's hit the button and hope.
If the vendors want places like us to try the new fancy features they force feed to the sales reps, they'll have to up the game because A) kicking the tires on routine software upgrades saps the time we would normally use to kick the tires on a new feature and B) repeatedly finding bugs that would have really horribly screwed over your infrastructure during these tests tends to encourage a minimalist design approach.
Equipment vendors simply are not doing their job in the post race-to-the-bottom era.
Time to take stock. Go home with some office supplies.