ecs78

3 ms·

1.
by ecs78 3y ago
I think they just wanted a quick post-mortem. I'm sure they will add more to the blog later in the year when they implement mitigations.
2.
by ecs78 3y ago
They are a younger company than these other providers. Microsoft, Google, and AWS had their own growth pains and disasters. Remember when Microsoft deleted all the data (contacts, photos, etc) off all their customers Danger phones by accide
3.
by ecs78 3y ago
Cloudflare vowed to be extremely transparent since the start of their existence. I'm very happy with the fact they have managed to keep this a core company value under extreme growth. I hope it continues after they reach a stable marke
4.
by ecs78 3y ago
It was more of an incident report. The efforts to get back online were mostly around Flexential, so it makes sense to dive in to their failings. That said, it is clear there were major lapses of judgement around the control plane design sin
5.
by ecs78 3y ago
haha. The control plane was eventually consistent after 3 days
6.
by ecs78 3y ago
Traditional GC isn’t less complex to program then automatic reference counting. Traditional GC has its place in short running extension languages, but in longer running programs you run the same risk of memory leaks as automatic reference c
7.
by ecs78 5y ago
You still have value semantics to lean on. They integrate really well with Swift’s actor implementation.
8.
by ecs78 5y ago
Yes, this is basically the new non-ObjC Distributed Objects or high level XPC interface.
9.
by ecs78 5y ago
I think the language and runtime are evolving too fast for good support of other platforms outside of NIO based apps running in a Docker container. This should change once Swift has all the features originally planned for it. They are getti
10.
by ecs78 5y ago
Distributed actors don’t actually have compiler support. They use a standalone code generator much like GRPC. The plan is to call the generator automatically during a build process using upcoming SPM plugin support. EDIT: It looks like ther