Hacker Newsnew | past | comments | ask | show | jobs | submit | njs12345's commentslogin

When not per tenant you still have this problem, and typically resolve by releasing database migrations separately to the code that uses changes (ensuring backwards compatibility).

I guess per-tenant you would handle similarly but build some tooling to monitor the state of migrations. It might even be easier in some ways, as you might be more able to take table locks when migrating per-tenant.


Confessionalism is probably just as large a confounder as communism in this context though..


There is the Images Batch API that isn't subject to the 1200 requests/5 minutes limit: https://developers.cloudflare.com/images/cloudflare-images/u...


I could see a combination of this approach and one of the audit approaches like `cargo crev` working well in the unsafe case:

- Require audit if there is new unsafe code

- Otherwise, rely on cackle to enforce no use of fs/net etc in safe Rust

This could provide the best of both worlds, automating most of the audit burden while still providing strong guarantees.


The lenders will come out alright. Even if the utilities end up being renationalised their debt will be converted into government bonds. The mugs here are the public, which end up paying to service the debt that has been used to issue dividends.


https://ourworldindata.org/grapher/carbon-intensity-electric...

With an ageing nuclear fleet built mostly in the 70s and 80s France has the cleanest electricity of any country in Europe (except those with abundant hydro).


A good place to start with Coq is Software Foundations: https://softwarefoundations.cis.upenn.edu/


> Even rust's memory model has places where it can't do what C++ can. (you can't use atomic to write data from two different threads at the same time)

Perhaps not in safe Rust, but can you provide an example of something Rust can't do that C++ can? It has the same memory model as C++20: https://doc.rust-lang.org/nomicon/atomics.html


You totally can in safe rust: https://doc.rust-lang.org/std/sync/atomic/struct.AtomicU64.h...


The atomics themselves sure, but I guess often they'll be used as a barrier to protect an UnsafeCell or something, like in the implementation of Lazy<T>: https://docs.rs/lazy-init/0.5.0/src/lazy_init/lib.rs.html#85


China has just hooked a pebble bed reactor up to its grid: https://en.wikipedia.org/wiki/HTR-PM


A fun Postgres extension to require this: https://github.com/eradman/pg-safeupdate


What's fun about it? I cant imagine why this is not the first recommendation when you setting up a new postgres DB.

And yeah, thank you. Today i learned new thing.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: