It'd be very unfortunate if Postgres didn't have regression tests for data loss due to bad io patterns. Should be possible to do some checks against those in an appropriate test harness. Which might mean "have qemu run…
Yes, I agree it would be very nice to have a way to integrate ACME into zeroserve. I'm not sure if zeroserve's plugin system might allow one to add a plugin to support it?
zeroserve doesn't use the Linux kernel's eBPF runtime to run the eBPF it uses, so the constraints of the Linux kernel's eBPF runtime (chosen because of how the Linux kernel thinks about protecting the Linux kernel from…
I hope this signals a departure from us being stuck without web usb in firefox too. It's a shame that I've been stuck using chrome for it. And maybe we'll get web bluetooth too.
The idea with either requiring very wide band or frequency hopping on the 900Mhz band is to make it so that usages of the 900Mhz band 1. are tolerant to some loss (ie: by temporary collision) and 2. don't collide…
The Apple way for hardware is more to design the thing so it breaks under normal use very quickly, and then refuse to replace it under warranty.
It's not a leading colon: It is a colon separator between the username and password, and the command used has the username as an empty string.
> Also, the "obvious reason" that American politics sent zero ex-presidents to prison is that Biden chickened out. So, there's that. Don't forget Ford deciding to protect his political allies (by pardoning Nixon). And…
I'm not sure I follow. This outage seems like it occurred for less than 1 day. The post you link to is about having certificates expire after 45 days. What's the connection you see?
Seems you could use a single SQL statement for that particular formulation. Something like this, using CTEs is possible, but alternately one can reformat them as subqueries. (note: not sure how the select of orders is…
Garbage collection is not required for memory safety. Languages that have garbage collection are not all memory safe.
It seems like the messenger might endorse the message though, and is attempting to be coy. Folks should be careful of people using the "messenger" title to attempt to obtain the appearance of impartiality.
> So no one that actually has to renew these certificates. I believe google, who maintain chrome and are on the CAB, are an entity well known for hosting various websites (iirc, it's their primary source of income), and…
OpenBSD does start X. And subsequently OpenBSD apparently hangs (or did so previously) when OpenBSD was running under Qemu. The subject in the parent comment changed to OpenBSD when they mentioned it, and it appears you…
Possibly a better comparison (though a bit dated now) would be AT&T (or whatever telephone monopoly one had/has in their locality) charging an additional fee to use a telephone that isn't sold/rented to them by AT&T.
> I am assuming the message durability guarantees lean towards YOLO rather than ACID? "Core" nats doesn't have durability. Nats jetstream is the api built on top of nats that in the main nats-server impl provides…
You've linked to a bug that was unintentional and was fixed. Go allowing torn writes for their slices and interfaces (their fat pointer types) is intentional behavior in the go implementation and has no sign of being…
Here's an example where a bug could exist in go due torn writes in a real program. I found this by searching for places where folks reload there config at runtime, as they are generally a place where people forget to…
In that case, I can just refer back to my original comment: https://news.ycombinator.com/item?id=46388948 And then note that memorysafety.org says this (in case folks haven't read it): > Memory safety is a property of…
"at the moment" implies that Go would need to change for that statement to change, but instead we're waiting on a programer to make a mistake (A mistake that memory safe languages prevent). Which does get us to why…
Interesting interpretation of that phrase. I think saying "probabilistically memory safe" would be more accurate (and more clearly communicate that idea), because we're betting on when a known case of memory unsafety in…
It sounds like you have a definition of memory safety you aren't disclosing. Please fully provide your definition of memory safety. Not interested in trying to figure out what it is in a 20-questions-over-hn way.
One can evaluate Go using the extent of the definition from the site itself, which uses out of bounds reads and writes as a sign of memory unsafety. Go's implementation allows torn writes for interfaces (which are 2…
Go can have memory unsafety leading to arbitrary memory reads and writes by having an interface replaced by another thread (go interfaces use 2 words, one for the vtable and another for the data. It does not replace…
This site is curious in that in incorrectly categorizes go as memory safe. Perhaps in part because the sponsors are invested in using go and benefit from its inclusion in a list of memory safe languages.
It'd be very unfortunate if Postgres didn't have regression tests for data loss due to bad io patterns. Should be possible to do some checks against those in an appropriate test harness. Which might mean "have qemu run…
Yes, I agree it would be very nice to have a way to integrate ACME into zeroserve. I'm not sure if zeroserve's plugin system might allow one to add a plugin to support it?
zeroserve doesn't use the Linux kernel's eBPF runtime to run the eBPF it uses, so the constraints of the Linux kernel's eBPF runtime (chosen because of how the Linux kernel thinks about protecting the Linux kernel from…
I hope this signals a departure from us being stuck without web usb in firefox too. It's a shame that I've been stuck using chrome for it. And maybe we'll get web bluetooth too.
The idea with either requiring very wide band or frequency hopping on the 900Mhz band is to make it so that usages of the 900Mhz band 1. are tolerant to some loss (ie: by temporary collision) and 2. don't collide…
The Apple way for hardware is more to design the thing so it breaks under normal use very quickly, and then refuse to replace it under warranty.
It's not a leading colon: It is a colon separator between the username and password, and the command used has the username as an empty string.
> Also, the "obvious reason" that American politics sent zero ex-presidents to prison is that Biden chickened out. So, there's that. Don't forget Ford deciding to protect his political allies (by pardoning Nixon). And…
I'm not sure I follow. This outage seems like it occurred for less than 1 day. The post you link to is about having certificates expire after 45 days. What's the connection you see?
Seems you could use a single SQL statement for that particular formulation. Something like this, using CTEs is possible, but alternately one can reformat them as subqueries. (note: not sure how the select of orders is…
Garbage collection is not required for memory safety. Languages that have garbage collection are not all memory safe.
It seems like the messenger might endorse the message though, and is attempting to be coy. Folks should be careful of people using the "messenger" title to attempt to obtain the appearance of impartiality.
> So no one that actually has to renew these certificates. I believe google, who maintain chrome and are on the CAB, are an entity well known for hosting various websites (iirc, it's their primary source of income), and…
OpenBSD does start X. And subsequently OpenBSD apparently hangs (or did so previously) when OpenBSD was running under Qemu. The subject in the parent comment changed to OpenBSD when they mentioned it, and it appears you…
Possibly a better comparison (though a bit dated now) would be AT&T (or whatever telephone monopoly one had/has in their locality) charging an additional fee to use a telephone that isn't sold/rented to them by AT&T.
> I am assuming the message durability guarantees lean towards YOLO rather than ACID? "Core" nats doesn't have durability. Nats jetstream is the api built on top of nats that in the main nats-server impl provides…
You've linked to a bug that was unintentional and was fixed. Go allowing torn writes for their slices and interfaces (their fat pointer types) is intentional behavior in the go implementation and has no sign of being…
Here's an example where a bug could exist in go due torn writes in a real program. I found this by searching for places where folks reload there config at runtime, as they are generally a place where people forget to…
In that case, I can just refer back to my original comment: https://news.ycombinator.com/item?id=46388948 And then note that memorysafety.org says this (in case folks haven't read it): > Memory safety is a property of…
"at the moment" implies that Go would need to change for that statement to change, but instead we're waiting on a programer to make a mistake (A mistake that memory safe languages prevent). Which does get us to why…
Interesting interpretation of that phrase. I think saying "probabilistically memory safe" would be more accurate (and more clearly communicate that idea), because we're betting on when a known case of memory unsafety in…
It sounds like you have a definition of memory safety you aren't disclosing. Please fully provide your definition of memory safety. Not interested in trying to figure out what it is in a 20-questions-over-hn way.
One can evaluate Go using the extent of the definition from the site itself, which uses out of bounds reads and writes as a sign of memory unsafety. Go's implementation allows torn writes for interfaces (which are 2…
Go can have memory unsafety leading to arbitrary memory reads and writes by having an interface replaced by another thread (go interfaces use 2 words, one for the vtable and another for the data. It does not replace…
This site is curious in that in incorrectly categorizes go as memory safe. Perhaps in part because the sponsors are invested in using go and benefit from its inclusion in a list of memory safe languages.