Huh, I always figured South Park made up Casa Bonita. TIL
Good for them though!
Huh, I always figured South Park made up Casa Bonita. TIL
Good for them though!
I would generally say to stick to approach 1, as much as that stinks. Your observation about approach 2 especially compounds once you start to look at more complex operations that need to be optimized based on how the underlying DB works. Care still needs to be taken in approach 1 to avoid non-optimal operations, but at least you have the freedom to rework individual methods on your DatabaseProxy instead of all FirebaseProxy methods using your underlying CRUD operations.
One of the fastest ways I get people thinking about this is asking
How would you implement a
listTimers
orlistTickets
API with cursors?
Generally that’s complex enough to bring out pain points.
Reads like an Onion headline
I’ll never federate my instance at least
That’s funny, I just emailed someone on gmail from my personal server.
This just isn’t true. It’s admittedly a bit of setup to get DKIM, SPF, and all the other fun stuff required to send email properly, but Google will accpet mail from my server with no issue.
I love my mono laser printer. It’s an older Canon I got from a retired lawyer, so it has probably printed a million pages already for all I know. Haven’t had to futz with it since I popped in a new toner cartridge that was ~$40. If I need to print color, I go to the local copy store, but that’s rare anyways. Been recommending the same for all my friends and family.