Why do you have 8 gpus and how were you able to afford all of them in this period of time lol
02.10.2025 21:18 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0@mempler.de.bsky.social
Backend Rust Developer
Why do you have 8 gpus and how were you able to afford all of them in this period of time lol
02.10.2025 21:18 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0Apps dont need ai
02.10.2025 21:17 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Ich finde rickyโs bluesky nicht (wahrscheinlich hat er es nicht mal)
Aber kannst du ihn das hier zusenden?
youtube.com/shorts/GDjvq...
Thanks
I really dislike apps that force me to give a review. It'll keep popping up until a review is being made.
Those kind of apps usually get a bad kind of review from me. Like common, leave me alone. If i want to do a review, I'll do it eventually.
Probably a couple reasons
1) it originated from windows
2) There were discrepancies and the author needed a stable base (which doesnโt update glibc since who knows what the fuck is going to happen when you bump that thing)
I really like Bazel, tools, especially LSP support have gotten really good in recent months
07.05.2025 15:35 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0But like, thatโs what you do anyway when you use third-party libraries (outside of a reasonable operating system called Linux)
Since prebuilt libraries are a pain to maintain
It feels like a double edged sword,
1) Yes, i get that some people just arenโt skilled enough, or simply donโt have the time to learn rust.
But 2) Why would you want to ship an entire python runtime? At that point, just use electron lol. Especially since itโs more mature.
Especially when people are stressed out due to a weekly deadline that keeps changing with different requirements.
04.05.2025 21:52 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Thatโs the difference between professional software development and hobby development.
You simply donโt have the time to write it properly to begin with. Yes, youโll improve, but there will always be something that you fuck up.
2/2
I would answer:
โSure, but by that logic, 99% of developers arenโt skilled. Everyone has written memory unsafe code at least once. Those rust compiler guardrails are there thanks to the mistakes a lot of people make when theyโre under a tight deadline (like usual in the SE field).โ
1/2
also this one:
youtu.be/zFELcHTki9U?...
You can technically also do it in C, but it is quite comber some.
Not just that, everything you need, you basically need to create it yourself.
low level learning has a great video that also mentions it
youtu.be/pnnx1bkFXng?...
Itโs simple, malloc abstracts memory allocation away. Each and every library uses it.
zig does not. You need to manually create the memory allocator (usually gpo) and pass it to everything that wants to allocate memory. You can even write your own!
Oh yea I agree, LLVMs tool chain gets better with every year
03.05.2025 16:57 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0I also donโt want to convince you to stick with rust, I just want to convince you to stick with rust for a couple of projects and move back to C.
Afterwards make a comparison of your C code before and after learning rust.
It blew my mind xD
I really like rusts way of teaching things, as it made me a better C/++ programmer as it rewired my entire brain into thinking: will this shit compile?
Which allows me to write correct code from the start
I really recommend sticking with it for a couple of projects, even if itโs absolutely horrific.
Regarding the community, thatโs usually just the loud minority. If you ask nicely, people tend to help out. (Well, unless you ask on stack overflow)
Regarding the language: The frustration is real, but there will be a tipping point where itโll feel natural.
Though, one thing I still fcking hate is async in rust. When done right, itโs quite nice to use. But a single mistake and the compiler will swear death to you
03.05.2025 16:47 โ ๐ 1 ๐ 0 ๐ฌ 2 ๐ 0There are definitely some annoyances, but i guess the pain just wears away after a couple of months working with it professionally
03.05.2025 16:46 โ ๐ 0 ๐ 0 ๐ฌ 2 ๐ 0Well, theyโre working on it lol
doc.rust-lang.org/std/random/i...
Though to be fair, how often do you need a random number besides for cryptographic operations
2) implement deserialise yourself. Itโs not hard at all.
3) (although I donโt know if itโll work) try wrapping it in a Box/Rc/Arc and remove the lifetime qualifier altogether.
I know this exact error and has also bugged me in the past.
There are a couple of approaches to solve this:
1) Remove the lifetime and change the inner workings so that it doesnโt require it. (I generally do not recommend working with raw references in structs)
Ui, I love that analogy :D
03.05.2025 15:42 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0One thing that I can give you as a piece of advice: if you fight the borrow checker; your approach is fundamentally flawed.
It helped me realise how to follow the flow without getting kicked in the balls by the borrow checker when dealing with lifetimes
That looks so dangerous lol, what does it do?
unwrap the lock guard and just get the direct reference? Copy the token and use that copy as a reference?
I would say so, yes. Even lower level than C.
Why? Because it exposes you to the memory allocation unlike C where itโs all hidden behind malloc.
You setup the memory allocation yourself and you choose whatโs best for your use case.
To be fair, no one forces you to use dependencies lol
Just use std:: and built your own http server, similarly what you need to do in C
Wellp, time to rewrite it in Rust :^)
20.04.2025 21:58 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0To be fair, Java is boilerplate as code.
20.04.2025 21:52 โ ๐ 3 ๐ 0 ๐ฌ 0 ๐ 0