It’s different in different markets. In Australia and New Zealand it’s usually a reasonably well made medium-dark blend.
You’ll get much better at any dedicated café, but it’s also miles better than sbux (who don’t even use real espresso machines).
I enjoy OpenMW and I’m happy to host if you want, although my instance is basically just me and a few friends right now.
I think they’re lawful evil, more devils than demons.
Hi, I’ve been doing TypeScript in my day-job and hobbies for six and a bit years now. I would not write JS in any other way.
TS is also a superset of JS so all JS is valid (unless you turn on strict mode). So there is no productivity loss/learning curve unless you want there to be.
In fact, a lot of people who think they’re not using typescript are using it because their editors use typescript definitions for autocomplete and JSDoc type signatures are powered by typescript.
In my experience I haven’t had an issue because usually the refactorings are small. If they’re not I just hop on a call with the person who wrote the MR and ask them to walk me through it.
In theory I’d like to have time to dedicate solely to code health, but that’s not quite the situation in basically any team I’ve been in.
You should refactor as needed as you go because refactoring cases are never gonna be prioritised.
There’s a markdown entry thing in the drop down menu that’ll convert your MD to their formatting.
By doing this the connections are all severed, the RAM is freed up, and it’s all good again.
Ah, neat! I didn’t think of that. You can limit the size of the connection pool in your lemmy config fwiw.
Nice, that looks like it’s doing a similar thing to my weird mess of SQL and Python that I did last year haha
Good luck for the migration :)
cronjob to restart the backend lemmy container
Fair enough, that’d work. I run my database in a different pod to lemmy (I run this all in kubernetes), and I cannot restart that pod without causing an outage for a bunch of other things like my personal website. I ended up just needing to tune my config to have a maximum RAM usage and then configuring k8s to request that much RAM for the DB pod, so it always has the resources it needs.
pictrs image cache is 250-300gb
oof :(
That’s what my custom lemmy patch was, it turned off pictrs caching. That’s now in lemmy as a config flag (currently a boolean but in 0.20 it will be on/off/proxy where the proxy option goes via your pictrs but does not cache). I then went back through mine and did a bunch of SQL to figure out which pictrs images I could safely delete and got my cache down to 3GB.
Interesting. I have some New Relic stuff setup with my cluster but most of that is just resource usage stuff. I ran out of RAM a while back so I’ve had to be a bit more restrictive about how many connections Lemmy can have to postgres db.
There’s no progress meter and so far it has taken 2 days 😱.
Uh oh. I considered updating to 0.5 as part of my 0.18.3-ish (I was running a custom fork I made with some image caching stuff that has since been merged in to real lemmy) -> 0.19.3 upgrade but I’m glad I didn’t.
Thanks for the heads up. Are you migrating to postgres for pictrs too, or sticking with sled?
These are pretty neat graphs! Is it sourced from the Prometheus logs?
Just updated to 0.19.3 but the DB migrations failed due to a permissions change I made a while back to my DB, so I had to spend a few hours in the SQL dungeons fixing things.
Technically only some of HK was under the lease, some was indefinitely controlled by the British. However, you’re still right because of the military force difference.
The Breville Bambino (Plus) with a nice grinder is basically an impossible value-to-money ratio to beat. Also remember to factor in a scale that’s accurate to 0.1g, a cheap WDT tool with thin needles (i.e. 0.35mm), and a dosing funnel to make the WDT not messy. If your budget is limited then you can skip the WDT tool I guess.
I wouldn’t go for the Barista Express/Pro because the built in grinder is not very good. The “impress” version of the Barista Express could still be worth it if you’re not looking to make espresso a hobby and just want something easy that will make tasty drinks. I’d recommend joining the Espresso Afficianado’s discord server, which is where a lot of the /r/espresso long-stays moved to after the reddit API stuff. There’s a channel for beginners that can help you get started.
Rust is roughly similar to C in most of these benchmarks and beats it in a few: https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/rust.html
Arguably when LLVM gets a bit better, Rust can be even faster than C because rust can be optimised in more places safely than C code can. The issue is that LLVM wasn’t written with that in mind, so some performance is left on the table.
I chose not to care, I had both cups on the scale and they looked about even though. If I really wanted accuracy I would have pulled the shot into a shot splitting cup and then split afterwards.
Go, Java, and Nim (in most cases) are all memory safe but are generally slower than C or C++ due to the ways they achieve memory safety.
Rust’s memory safety approach is zero-cost performance wise, which makes it practical for low level, high throughput, and low latency applications.
That flag exists, it’s called unsafe for if you need to tell the borrow checker to trust you or unwrap if you don’t want to deal with handling errors on most ADTs.
You can always cast anything to an unmanaged pointer type and use it in unsafe code.
A crash is different to a SEGFAULT. I’d be very surprised to see a safe rust program segfault unless it was actively exploiting a compiler bug.
https://camposcoffee.com/product/colombia-el-jordan-2/ that I picked up when I was in Sydney earlier this month. It’s a little darker than I usually go for but it’s quite forgiving.
This reminds me of a great video about this sort of principle in reverse: https://youtu.be/wBBnfu8N_J0