![](https://campfyre.nickwebster.dev/pictrs/image/040dfe35-7b71-4a33-aa44-f2c8938bcdde.webp)
![](https://lemmy.world/pictrs/image/db7182d9-181a-45e1-b0aa-6768f144911a.jpeg)
It’s falsifying business records, which becomes a felony when combined with it being a campaign finance violation.
Not as strong of a case as the docs one but it is a crime.
It’s falsifying business records, which becomes a felony when combined with it being a campaign finance violation.
Not as strong of a case as the docs one but it is a crime.
I think they’re lawful evil, more devils than demons.
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.
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.
It was nice, although fairly mellow because I pulled it 20g:60g (so two 30g singles)
Yep! They’re based in the city I live in, so everything is quite reasonably priced. I think that deep blue is my favourite colour of theirs.
You need everyone else in the EU to agree to remove them. Poland and Hungary sort of protect each other from EU consequences.
((a, b) => a ?? b)();
const fn = (a, b) => a ?? b
ARM, but Apple has the most advanced ARM chips and macOS /The AS Platform has the best amd64 to arm64 translation layer.
I mean at that point you’re basically running macOS 😉
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.