Nah I’d rather have a specialized inktober community, as people who want to see/post inktober will search for an inktober community. Not art share. This is also the fediverse. If you don’t like something, fork/create an instance!

Although crossposting exist if you want to double dip

Uh? Well I had my 3d art posts removed due to not being inked sketches…

Same. I don’t do it, I do not post pictures. I won’t let them force my personal info on a site that doesn’t respect boundaries

I think you’re lost. It’s the programming meme community, not a question board

One thing I do love about the LLM era is that people get forced to be way more pendantic when it comes to code, and that’s a win for everyone.

… Well admist the enormous losses LLM brings

What about Garbage collector? Group chat? Gold chunk?

Thank you. Really cool.

Off to kill myself now!

Damn she’s all grown up now

In the case of France there’s two possible broken laws (not a lawyer btw):

• If the glasses wearer upload the video/photo online, you are one of the primary subject of the frame (aka not just in he background), and didn’t consent to being on the internet, you can sue.

• Companies must legally ask you for your concent to collect personal and identifying information. If the video/photo is sent to meta for big data/ai training, they must ask for consent

Edit: “primary subject” is kinda vague and may change depending on the context. If you do a VLOG and someone does something funny in the background, not aware of the camera, and the video is re-uploaded to only feature the guy, then it becomes the primary subject, and must be asked for concent

It’s been mocked to death, but it’s still better than a regular cell tower. Instead of a boring pylon with antennas, you get a funny fake tree.

Personally I find home manager really hard to use. The documentation is really bad, and I never find what want… Nor what’s possible. I don’t use it because I don’t want to, just I don’t know how to

It was that or spaghetti an override and compile krita from scratch. So I chose the lazy way

Yeah I see it when I nix run krita lol

I actually use it to run krita, prism launcher when the Minecraft mood peek in, inkscape, MusicBrainz picard, Alistral, peazips, libre Office.

Aka, anything that I don’t use enough to warrant opening my config and adding them in (and forgetting when I do open my config.

Although krita is currently being installed through flatpack because nixpkgs ship broken alpha versions…

Most of the time, async tutorial makes you learn tokio, not async. If your program can run with only tokio::main, then you learned async. If not, you learnt tokio (except if you are spawning a future that should never stop)

For example, my pet project only uses tokio::main to do async stuff. The only instances of tokio::spawn is make sure some SQLite transactions get polled to completion. I do need to replace them with a proper mechanism now that sqlx supports smol-rs

A lot of the time it’s not about options. It’s about not messing up the async pattern.

If you have something that either:

• requires a lot of CPU time
• requires to run permanently, independently to the caller’s future polling. Then you can spawn it on a global tokio executor.

If not, just use future polling tricks like the futures::join!() macro or a stream with .buffered(). It won’t be slower. The bottle neck is IO. Not the program.

Personally I even try to replace the heavy reqwest library with ureq + blocking, and it works perfectly and compiles faster (you can see that in the api_bindium crate)

Keep in mind that it doesn’t remove tokio from the stack tho. Don’t use this to try to improve compilation time

Yeah but it’s not really a problem with rust but how the language pattern is made. It’s the same in JavaScript/typescript, and Python IIRC

Well you just need that crate :3

https://crates.io/crates/async-compat

Viral async?

Tbh the borrow checker isn’t a problem for 75% of cases. If you actually need the performance/memory optimization then yes you will have to deal with it… Otherwise just .clone()

And if you find the borrow checker annoying in async rust, that’s mostly a tokio issue. Look into smol-rs as it offers alternatives

If you want real cons…

• Compile times
• easy build time arbitrary code execution
• trait bounds spaghetti