The #rust community is so big now that you stumble over awesome crates with thousands of stars on github, and you don't stumble over them because someone mentioned them to you, but because they just "appear" on your way through the internet.
This is awesome.
Can we please, please – PLEASE! not make the nonsensical US date format month/day/year the default in applications? 🤦♂️
PRE 👏 TTY 👏 PLEASE
And to all users of that format: it makes no sense, it's counter-intuitive, it makes collaboration frustrating, it introduces inconsistencies and errors... Just stop. Please. Use international standards.
(And don't get me started on your other units of weights, volumes and distances. Bloody hell.)
Boost if I'm right.
#Tusky 12.1 is out with a new setting to remove the top app bar, bug fixes and improved translations!
Thx to everyone reporting bugs and translating the app 💙
@mdszy I'm still mad about command.com being a home utility product site instead of a shell interpreter
To be clear I'm not sure actually python is the problem here just it is not really known for performance.
I used fail2ban with ufw as backend. Recently found out when calling ufw from rust that it's super slow and maybe that was actually the problem. Now using iptables and ipset as backend for my mini clone.
Maybe it was just a bad choice to use ufw and not fail2ban's fault but it's still fun to write a mini clone in rust so I'll continue on it.
So I installed #fail2ban the other day on my small vps and during a load test I found out that it takes up more than 60% of the CPU during high load. I use(d) it to block annoying attempts to open random php admin pages (I don't even use PHP).
Figured out it's written in python and actually expected such a popular basic tool to be written in C for best performance...
So I started writing a mini clone in #rust and it can handle 300,000 lines/sec on 1 cpu core in first tests.
Eager to checkout new vgtk release, a gtk-rs wrapper. gtk-rs (and gtk) is so powerful but requires so much boilerplate. https://github.com/bodil/vgtk/releases/tag/vgtk-v0.3.0
1939: software doesn't exist
1949: software is limited
1959: software improves because faulty software costs a LOT of money
1979: software might start costing less, even faulty software
1989: we still care about optimized software, but say yer prayers, varmint.
1999: results of "it compiles; SHIP IT"
2009-: "stop being a cheap-ass; just buy more RAM, a faster CPU, a larger hard drive, a GPU from this century, and run software how developers TELL you to run it, you pleb."
🦀 Rust, 🐹 Go and 🍵 Kotlin enthusiast
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!