2,031 karma · joined July 30, 2010
Some people love their realtors, although they do very little for their outlandish commissions. They do however, guide you through the process and give you transactional advice. Like any sales person, they generally have an interest in the transaction closing but they are only trusted if they come off as acting in your interest. That trust can ultimately help the transaction close — this is the line that I think good sales people walk.
I don’t think there’s a valid universal “hybrids are better” conclusion; it all depends on your specific needs and what you value. A single car for a single person is different than a family with multiple cars. For an electric car, Tesla still makes a compelling product (and while competitors in the US are getting much better, notably Hyundia/Kia, Tesla still feels like the market leader).
I just get tired of the idea that the president/executive completely colors every single government action. Let’s stop pretending that every election will completely rewrite the MO and agendas for every agency.
The comment I replied to was based on exactly those kinds of assumptions (“couldn’t possibly imagine this happening under Trump”) and was wrong. Now you’re just doing a no-true-Scotsman (“oh, it only happened because he wasn’t paying attention”).
I’ve personally seen no evidence that right-to-repair is a partisan issue in the way you’ve suggested, and I’ve seen plenty of evidence that the cronyism charges you’re levying are also not limited to a single party. You can hate the guy for lots of reasons, but the idea that Trump is uniquely capable of being bought on this issue seems very strange to me.
Where were you in Canada? I definitely didn’t have the same experience (in the GTA). Lots of Canadian Tire money circulation and regular trips there in my house, but it was not a thing beyond Canadian Tire.
I’m sure that we were not alone, and there were many of us appeasing the goblins in our brains yelling for order, diligently checking boxes row by row (or some other orderly pattern). If I had landed on the page with every box checked, I would have felt a sense of doneness and left it in that perfect state. It’s so hard to empathize with all these maniacs here who would destroy that beauty just to write “boobs” ;)
IIRC, CloudRun has multiple modes of operation (fully-managed and in a K8s cluster) and different sandboxes for the fully-managed environment (VM-based and gVisor-based). Like everything, performance depends a lot of the specifics — for example, the network depends a lot more on the network path (e.g. are you using a VPC connector?) than it does the specific sandbox or network stack (i.e. if you want to push 40gbps, spin up a dedicated GCE instance.) Similarly, the lack of a persistent disk is a design choice for multiple reasons — if you need a lot of non-tmpfs disk or persistent state, CloudRun might not be the right place for the service.
It sounds like you personally had a bad experience or hit a sharp edge, which sucks and I empathize — but I think you can just be concrete about that rather than projecting with system call times (I’d be happy to give you the reason gen1 sandbox would be slow for a typical heavy python app doing 20,000 stats on startup — and it’s real but not really system calls or anything you’re pointing at,… either way you could just turn on gen2 or use other products, e.g. GCE containers, GKE autopilot, etc.).
I’m not sure what’s wrong with advice re: optimizing for a serverless platform (like global variables). I don’t really think it would be sensible to recompute/rebuild application state on any serverless platform on any provider.
System call overhead does matter, but it’s not the ultimate measure of anything. If it were, gVisor with the KVM platform would be faster than native containers (looking at the runsc-kvm data point which you’ve ignored for an unknown reason). But it is obviously more complex than that alone. For example, let’s click down and ask — how is it even possible to be faster? The default docker seccomp profile itself installs an eBPF filter that slows system calls by 20x! (And this path does not apply within the guest context.) On that basis, should you start shouting that everyone should stop using Docker because of the system call overhead? I would hope not, because looking at any one figure in isolation is dumb — consider the overall application and architecture. Containers themselves have a cost (higher context switch time due to cgroup accounting, costs to devirtualize namespaces in many system calls, etc.) but it’s obviously worth it in most cases.
The redis case is called out as a worst case — the application itself does very little beyond dispatching I/O, so almost everything manifests as overhead. But if you’re doing something that has 20% overhead, you need hard security boundaries, and fine-grained multi-tenancy can lower costs by 80% it might make perfect sense. If something doesn’t work for you because your trade-offs are different, just don’t use it!
I’m so confused by this. Unless you use a dot import, isn’t this just bar.*?
It’s certainly possible, but my guess is sshd is likely to have a lot of open policy. I’m really curious if someone knows different and there are hard detection for those things. (Either way, I bet there will be in the future!)
I’m not arguing with the point, but this is a great place to hide — very difficult to have meaningful detection rules even for a sophisticated sysadmin.
I don’t believe the parent comment is saying the design is poor, it’s about the process during assembly and maintenance.
An interesting current data point for me is that the overwhelming majority of Palestinians support the actions of Hamas on October 7th specifically. If someone “just wants freedom” but doesn’t support the slaughter and kidnap of innocent Israeli citizens, they would actually be in the minority — so I don’t think your characterization is broadly correct. This isn’t even considering other historical events and opportunities for independent statehood.