this post was submitted on 07 Dec 2025
983 points (99.1% liked)

memes

18374 readers
2973 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/Ads/AI SlopNo advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments

Welcome to Rust which "solves" this issue...

Yeah it takes more time than a quick and dirty python script. But when I'm counting the countless hours (what irony) into this equation because of mindless leaky abstractions and resulting debugging, I'm certain that I'm at least not a lot slower writing that. As I said I'm not talking about the last 10-20% of performance that's possible say even up to 40%, but more like an order of magnitude (at least), i.e. algorithmically insufficient or relying too much on that your abstractions do everything right and you use it correctly (which in the case of react is seemingly not the case, when looking at the modern web).

Taking that example (Rust) again, I very often get away with .clone() everywhere, i.e. not even caring much about performance while the performance is not significantly impacted. Then I switch to our typescript code-base in my job and get aggressions because of this extreme slowness (because of stupid abstractceptions, like wtf? shadcn needs to be built on radix-ui needs to be built on react etc. which in effect results in a slow abstraction-hell... and leaky abstractions everywhere)