HN user

njs12345

1,175 karma
Posts9
Comments369
View on HN

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.

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.

Football Radar | Systems Engineer | London | Remote (UK) | Full-time

We're looking for an experienced Systems Engineer / Site Reliability Engineer to help us deliver high quality software and shape our technical roadmap over the coming years.

The Development department consists of 20 developers across 4 sub-teams: Analysis, Modelling, Systems and Trading. As part of the Systems team, you'll get the opportunity to enhance our DevOps culture, taking our collaboration and automation to the next level. We're on a mission to improve stability and standardisation, and shorten feedback loops in order to make our team more efficient in delivering business value. We're also looking for someone who can help us integrate security considerations into our development process.

Find out more about Football Radar and the role here: https://footballradar.recruiterbox.com/jobs/fk0mg3u/

This isn't quite the same, because it's just an alias - you can pass a UserID to a function accepting a PostID: https://play.golang.org/p/nSOgcJs_66y

It still provides a documentation benefit of course.

EDIT: Whoops, yes, as lentil points out, they are indeed distinct types not aliases. So it does provide the benefit of the Rust solution.

I agree in general with your comment, but..

If you can already tell ahead of time which company's stocks are going up, just take more cash and use it to buy those stocks.

These are pre-IPO companies so you can't easily buy their shares.

The base language is actually very small - you do need to know a lot on top to get anything done but arguably that's true with most languages.

CPU also causes a similar problem - for instance Java (and lots of runtime Java libraries) use the number of available CPUs to decide how many threads to use for various tasks, which can cause terrible performance if you're giving a container 1 CPU of a 48 CPU server and it thinks all 48 are available - we encountered this at work recently and eventually bodged around it, but definitely a gotcha that this stuff isn't handled properly by runtimes yet.

I imagine JSON serialisation overhead is pretty small when compared to parsing/typechecking a Rust program, which is probably what the Rust Language Server has to do whenever anything changes..

Not to mention that a lot of people capable of writing the tooling would struggle to export a C API. I write Scala in my day job and it would take me a while to learn how to do that - and I've done some programming in C/C++ before.

All of the places you listed have massive problems with NIMBYism. If the places a 30 minute cycle away from the City of London had the residential density of Hong Kong, what do you think house prices would be like?

Is there anything really wrong with sharing a PIN for all your cards? What sort of attack does this make easier? Maybe if someone sees you entering a PIN for one of your cards and then steals your wallet?