I think they’re lawful evil, more devils than demons.
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.
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.
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.
I miss circles
I don’t think ActivityPub supports that. There’s just the “sensitive” flag (which Mastodon shows as a content warning and lemmy shows as NSFW). I think you’d have to do something outside of the specification.
Might be worth asking in !selfhosted@lemmy.world
True, you’re correct. I’m just not sure how you did it without corrupting the sled db. Maybe I’m just unlucky
Interesting, when I tried a while back it broke all images (not visible on the website due to service worker caching but visible if you put any pictrs url into postman or something)
I wrote a patch for Lemmy a week or so ago if you want to skip the caching: https://github.com/LemmyNet/lemmy/pull/3897
I think deleting images from the pictrs storage can corrupt the pictrs sled db so I would not advise it, you should go via the purge endpoint on the pictrs API.
Just a note that my PR there doesn’t disable pictrs for your own instance’s users. It just disables the caching of remote content.
The Lemmy instance I’m speaking from right now is running in my k8s cluster.
Fascinating! Thanks for sharing.
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.