1,574 karma · joined June 27, 2011
But if you're comparing with products from Ubiquiti (especially the Unifi line) you're probably going to see similar performance anyway. I switched to a APU2 as my home router two years ago, and I've been very happy with it. Doesn't seem to break a sweat handling a gigabit connection in a typical home setting, running VyOS. I'd probably think about something more powerful in an office or data center.
It's not like it's in the best interest of the workers to see the company go belly up. Or be less competitive. If the company can show that this is why they're defering merit pay there's no reason to believe that unions won't accept it and agree with them.
It gives employees leverage, and healthy competition in all aspects should just strengthen the company.
But like you said, you also run the risk of flipping the car. It would be interesting to see some actual data on this. It's the sort of thing that has been repeated so much that it's easy to make bad assumptions.
Anecdotally, I've almost hit a moose two times. Both times I just completely froze up and slammed the breaks. They jumped out of nowhere, the only reason I didn't hit any of them was just pure luck and timing, and had nothing to do with my ability to react or steer away.
You can create 100 delegation sets (until you reach a quota, which can be raised) per account. This would give you 100 possible combinations, rinse and repeat for more account and I'm sure you've exhausted all possible combinations rather quickly. You can also create more accounts programatically.
The mitigations does make it negligible harder for someone to swoop in and take control over domains that currently have misconfigured name servers. But at that point the domains won't be resolving anything, so either the user don't care or aren't even using the domain.
On Amazon you can request a delegation set, which means a combination of four name servers. Do that enough times and I'm sure you'll have all the possible variations that could exist. For every Amazon account you can request 100 delegation sets, but it's easy to scale this out over multiple accounts. I'm also willing to bet you can easily get that limit raised to thousands of delegation sets by just telling support you're going to use the account for hosting tons of zones. I don't know the specifics of how CloudFlare does it, but I assume you're more than welcome to do the same, programatically.
There's no hill to die on. I don't work for a provider, and how is that even relevant? Seems like a weird straw man argument or something.
The potential risks of this is blown way out of proportions. You're still in control over the domain, just not the zone. Do stupid things, win stupid prices? In this case, letting someone else control your zone because you failed to understand how DNS works.
Some TLDs check for this, they won't transfer a domain to new name servers unless they already respond as authoritative name servers for that domain.
The argument is that someone else could set up a zone before you. But there can't be duplicate zones, and the user should create this zone before changing the name servers. There are mitigation strategies that have already been discussed, but other than being a Nice Thing (tm) and likely lowering the volume of support tickets I don't see how this is the providers fault. You set the name servers before checking that you had control over said name servers, or forgot to change them when moving away.
And don't get me wrong, I think the solution that Amazon and CloudFlare use are better than nothing. Having safe guards against people misconfiguring things are always helpful, and I'm sure it would result in fewer support cases.
That said, having some safe guards for a common pattern of misconfiguration is always good.
Given the decentralized nature of DNS it's very simple to set things up before you change the nameservers, and this is widely considered to be the best practice. This also solves the "two accounts trying to claim a domain at the same time".
The way Amazon does it sure helps mitigate it. I'm just not sold on the idea that it's their responsibility to solve this. And I suspect they do this for other reasons as well, like spreading out across multiple TLDs.
You can partially mitigate the issue the way Amazon does it. But even that isn't foolproof and I suspect they have other reasons than just this for their approach.
I'm a little skeptical to the claim that passthrough is so much faster than virtio-scsi or something similar. I'd imagine that the disk controllers and network would be the bottleneck. And as an added bonus you prevent people from doing shenanigans on disk firmware. We're talking about plate spinners here, latency isn't really what they're known for.
But you can use Shared VPCs that spans many accounts and drastically reduce the need for things like attachments to virtual gateways, nat gateways, service endpoints, and so on.
There's simply no good reason to periodically write your data from flash to $other every now and them, and then back to flash. There are heaps of other ways to prevent data loss or performance degradation in flash storage.
There are methods like tiered storage, where only the most active data is present in Flash-storage, much like write back caching.
The article also doesn't mention spot pricing and per-second billing. Being able to burst up to hundreds of machines in minutes is super nice. I did some back of the envelope calculations for some build servers and it came out favorably for $cloud providers. Having idle machines also cost money.
For a highly optimized and predictable work load I'm sure providers like OVH can provide better bang for bucks. But that also assumes you don't use any of the cost reduction methods that are available with $cloud, like using spot pricing for variable load and reserved capacity for base load.
This is where hydro-based power plants excel, they're able to adjust the power output as quickly as gravity can push the water down the pipes. They're able to ramp up from almost no output to full capacity in minutes. Gas-turbines are also able to do this.
There are some good lessons in what you shouldn't do, perhaps not intended so, but still interesting.
We don't have many forest fires here in Norway, but we do have very harsh winters. Every year a family or group of people are trapped in a blizzard and die. And most of it could have been avoided by following the "Norwegain Mountain Code"[1], which I imagine is similar all over the world. Turning back before it's too late, seeking shelter, and not exhausting yourself when you realize that you're in trouble. I'd be very worried if people in my group started getting nauseous. That's when you start making those deadly mistakes.
If the non-TouchBar one was cheaper then I guess you'd be right. But all else equal I imagine people would want it. I quite like it, of all the things that have been wrong with the previous lineup of Macbooks, the TouchBar really isn't one of them.
However - the way Apple implemented the TouchBar leaves much to be desired. You need something like BetterTouchTool or MTMR in order to make it usable.
Some brave people that were running the public beta reported these issues to Apple, but we're now four point releases in and still no fix. Apple seem to not even want to acknowledge the issue, they just send users to their FAQ which sums up to "have you rebooted?"
The issues seems to start if you have bluetooth devices connected and your laptop becomes memory constrained. And after that it's in a broken or bricked state it seems. You can do tricks like killing coreaudiod to get audio devices to connect, but trackpad is still broken.
- My external trackpad isn't able to connect, at all. Audio devices require that I kill coreaudiod before connecting, otherwise they just disconnect after a few seconds.
- I can wake the laptop with a bluetooth keyboard, but when it's awake the keyboard stops working. Flipping the switch on the backside of the keyboard lets it reconnect again.
- There are transitions that you cannot disable that makes your laptop feel super slow. In Mojave you could disable them, in Catalina you can't unless you want to run with SIP disabled.
- There's also a super fun bug with mobile hotspot failing to activate, and there's no way for you to just manually connect to your own hotspot, it has to go through this bluetooth activation, even though your mobile hotspot is visible and connectable on all other devices. You end up in situation where you connect to your friends hotspot and they connect to yours, since neither of you are able to connect to your own.
I've given up. The quality control in Apple is down the drain, and have been for quite some time. I'm fixing to downgrade to Mojave this weekend, hopefully that will make it more stable. But I'm not holding my breath. To add injury to insult I'm on my third broken keyboard now. Next time it breaks I might just use the consumer laws and make them refund the laptop so they'll have to take a big loss for creating such a flawed device.