Don't forget data races.
Don't forget data races.
Well, that's an eloquent argument. You don't care about memory management and data synchronization? Fine, go ahead, you can build your console based tic-tac-toe game app without it. No problem.
This is what you can expect in a country where money is considered free speech.
Agreed, it has been far too long for the refresh on the Pro models - and it's very hard to recommend them at their current price.
With that said, they might not be letting them die a slow death, but rather been unhappy with that particular generation of Intel mobile chips in a "Pro" model.
To be fair, some of us like Macs because it's a super-easy way to get a smoothly operating unix laptop. The hardware is generally within +/- 10% of equivalent Windows gear - though that calculus got difficult for a while when Apple fell behind the Intel upgrade curve. I run Linux all day, every day, but it's in a VM, so at the end of the day I don't really care what the underlying OS is.
My base ideology is libertarian, so I'm all for individual freedoms. I honestly believe that, in the vast majority of cases, a system that emphasizes strong individual freedom and personal responsibility will leave humanity better off.
With that said, all ideologies eventually smack into reality, and none to date deal with it perfectly. One of these realities are germs. Disease does not respect the individual model and demands a coordinated approach. Absent a 100% safe and effective vaccine (which would be compatible with individualism), the only way to stomp out a communicable disease is to reduce the population with it to such a degree that it fizzles out.
As such, I feel that we can and should make allowances for individuals to act selfishly or in ignorance, but only up to the point where the vaccines are no longer effective in wiping out the diseases. At that point, you have to make the pragmatic decision to set your failed ideology to the side for the moment and solve the problem at hand.
STP failures and flaps can cause outages, but requiring an admin to manually move patch cables and activate hardware almost always causes larger, longer outages.
Yes. But how often have you had an untouched cable fail? Maybe once in a lifetime career? How many times should you expect STP to take down a network? I've seen that happen many more times. Though, touched cables fail often. The barely-on connector that fails when you brush it getting to a power connection on an unrelated piece of gear. But, you are right there and prepared for it, so you can fix it before STP convergence time.
(And I'm not involved in networking in our team, I look after servers and applications).
Good, because 802.1x isn't MAC authentication, so MAC spoofing is unrelated to that topic. And your solution of active/active load balancers still leaves you with a single point of failure. Active/active, by definition, has a single configuration across the devices. So one typo on one device can take down both. Back to a single point of failure.
A routing protocol, by its nature, can't be a single point of failure
Yet, and improperly injected route can take down the entire network. Single Point of Failure.
That does not make me filled with hate
Sure it does. You hate Hillary. You are voting for a moron, so you said.
I'm a Lisp variable -- bind me!