Tootfinder

I've been waiting for more powerful const generics in #RustLang for since 2020 (blog post at <https://christian.amsuess.com/blog/website/2020-09-24_rust_2021/>). Se…

Zero days since #RustLang wanted to kill a platform.
https://github.com/rust-lang/rust/issues/162011

We're currently planning a new meetup of @… at the DHBW #Mannheim (in Neuostheim) and are looking for speakers. The topic can be anything related to #RustLang

Today's lesson in "Even when you're good with a hammer, you'll have a bad time treating everythinng as a nail":
When you have to do #SOAP, choosing #RustLang sends you on path of pain and suffering.

Official announcement will follow next week: we're meeting on Tuesday, October 7, for our next @… meetup in #Mannheim. We still have time for a second talk, so if you have a topic or project related to

Also, zero days (well, minus a lot of days because I've been slacking) since a random #Python package got a new #NIH dependency on another Python package which is actually a "fastest" #RustLang package which cannot be built because the author thinks it a great idea to require a nightly Rust compiler.
…and of course it's full of "unsafe" calls. Because Rust is obviously such a great language for making secure code.
https://github.com/awolverp/cachebox/issues/62

I'm giving an actual Rust university lecture next semester and I can't shake the idea of bringing the obligatory Rust cat ears for the first day.
#RustLang

Does #Bonn already have a #NixOS or #RustLang meetup? 🤔

I was running a test suite for pysequoia, and one test seemed to have been taking forever. I started suspecting it hit some infinite loop, then I recalled I have RUSTFLAGS=-Copt-level=0 in my development environment, to avoid wasting time on rebuilding the same thing over again. Yep, that was it.
Unoptimized #RustLang is like C code with -O(-1000). It's slow as hell that has frozen over twice, and I'm talking about the frozen part and not the part where sinners are skating on the ice.

I feel a bit dumb for having discovered that so late, but #VSCode / #VSCodium do not use the .gitignore file to decide what inodes to watch for changes...
Working on a big #Rustlang project can be a nightmare (burning CPU, eating up all the RAM...), given that the target/ directory can end up using more than 100gb of disk space.
Remember to set your "files.watcherExclude" setting to avoid that problem:
```
{
"search.useIgnoreFiles": true,
"search.useGlobalIgnoreFiles": true,
"files.watcherExclude": {
"target/**": true,
"**/target/**": true
}
}
```

Have you even considered that if you replaced your CPU with a hardware #RustLang interpreter, things would run even faster?
Of course, the downside is that every month you'd have to replace your CPU because some software would consider that version obsolete.

#Gentoo has a strict #NoAI policy, so our projects are slop-free. Unfortunately, these days you cannot run an up-to-date system without tons of random slop packages, because everyone insists on using that crap.
Gentoo supports a whole bunch of architectures that probably every other distribution dumped so far. Unfortunately, these days the available software list is shrinking, as everyone insists on adding some random meaningless dependencies on #RustLang (like using uv-build, which is the single most harmful meaningless #Python project ever created).
Gentoo has a strong upstream cooperation policy. However, these days I'm afraid to file issues, because just too often they just trigger more slop. I miss the "good" old days where the worst you could expect is some toxic asshole.
The state of #FreeSoftware is truly depressing. There is little joy in distribution work these days. You're overwhelmed with shit, burned out and end up doing a shitty job. And it's bad for your health.
#FLOSS

Do people actually understand #RustLang types and borrowing and whatever, or do you just write the first approximation and then follow compiler errors like I do?

#RustLang folks, could someone do me a favor and make a PR to fix #Gentoo work.

Finally reported the abusive behavior of #Cargo #jobserver: #RustLang

So if you're wondering how great #RustLang is, let's talk about #mypy. Mypy introduced its own Rust - #Python package, ast-serialize. This package had a deep crate dependency that was broken on PowerPC. The issue was fixed a month ago but everything is still blocked on a deep chain of dependencies being updated and released.
https://github.com/mypyc/ast_serialize/issues/68
EDIT: yes, I know, it's not Rust, it's Cargo. Because obviously Rust without Cargo makes so much sense for that one project using it.

If you are developing in #Rustlang then you should check this post: #cybersecurity #infosec #supplychain #supplychainattack

In other news, the #Python semver package has now #RustLang speedups. I'm sure they will come in handy in its reverse dependencies, which are (checks notes) net-analyzer/pontos. I'm sure that package needs to efficiently handle millions of semantic versions a second.
#Gentoo

A short video showcasing the current state of the #SoulCrafted Slicer I'm working on.
#3dPrinting #Resin3dPrinting #SoulCraftedSlicer #FLOSS #OpenSource #Rust #Rustlang

Oh, right, in case I thought I'm going to have time to do useful things, I just realized I still need to deal with the humongous #Gentoo fallout from #Hypothesis #Python package requiring #RustLang now.

Yeah, so #PyPy 3.12 support won't enter #Gentoo for a while, because it needs support in #PyO3 first (because of the brilliant idea that #Hypothesis should require it), so we're blocked on the whole #RustLang / #Cargo "implement, release and wait for everyone to update their pins" nonsense.