MRK
@marma.dev
I seek meaning in systems, both digital and human.
🌐 marma.dev
🌐 marma.dev
We are using TypeScript. We could also explicitly set the return type, but the problem is that the types don't exist during runtime. They are being checked through the LSP during development and before building. Our function was being changed to an async one after type checking.
November 2, 2025 at 12:12 PM
We are using TypeScript. We could also explicitly set the return type, but the problem is that the types don't exist during runtime. They are being checked through the LSP during development and before building. Our function was being changed to an async one after type checking.
I already switched to tanstack start for my personal projects. It's really a joy to work with and thank you very much for your contributions to this amazing stack!
November 2, 2025 at 10:40 AM
I already switched to tanstack start for my personal projects. It's really a joy to work with and thank you very much for your contributions to this amazing stack!
Yes, it should've never built successfully and throw us an error that the function must be an async one.
Which, to be fair, does it now. But I don't want to imagine how many people might have stepped into this and/or maybe still running this version without knowing...
Which, to be fair, does it now. But I don't want to imagine how many people might have stepped into this and/or maybe still running this version without knowing...
November 2, 2025 at 10:39 AM
Yes, it should've never built successfully and throw us an error that the function must be an async one.
Which, to be fair, does it now. But I don't want to imagine how many people might have stepped into this and/or maybe still running this version without knowing...
Which, to be fair, does it now. But I don't want to imagine how many people might have stepped into this and/or maybe still running this version without knowing...
This one is lying on my desk for too long untouched. I think it is time to pick it up. Thanks for reminding me :)!
October 6, 2025 at 3:29 PM
This one is lying on my desk for too long untouched. I think it is time to pick it up. Thanks for reminding me :)!
Yes, this is me and thank you very much for this feedback! I really appreciate it! Have a good day sir :)
October 1, 2025 at 8:43 AM
Yes, this is me and thank you very much for this feedback! I really appreciate it! Have a good day sir :)
The more I think about it, the more I agree with you. I've heard multiple times that seasoned engineers struggled longer until it clicked bc they had to unlearn a lot of bad practices learned through other languages. So I think first timers might have an advantage here.
September 10, 2025 at 6:10 PM
The more I think about it, the more I agree with you. I've heard multiple times that seasoned engineers struggled longer until it clicked bc they had to unlearn a lot of bad practices learned through other languages. So I think first timers might have an advantage here.
May I ask which resources you used and what was lacking?
September 9, 2025 at 1:40 PM
May I ask which resources you used and what was lacking?
No problem. Thanks for replying!
August 25, 2025 at 8:46 PM
No problem. Thanks for replying!
If it's open source would you mind sharing it for us to also read and learn from it? :)
August 25, 2025 at 7:43 AM
If it's open source would you mind sharing it for us to also read and learn from it? :)
I guess when it comes to features, godot might be the clear winner here.
August 19, 2025 at 5:53 PM
I guess when it comes to features, godot might be the clear winner here.
It depends on what you mean by advantage. I use bevy bc I like rust and coding in general. I tried all the GUI engines but I just can't work with so much clicking. With pure coding frameworks I have a sense of being in full control. Does that count as an advantage? Maybe... For me at least it is.
August 19, 2025 at 2:39 PM
It depends on what you mean by advantage. I use bevy bc I like rust and coding in general. I tried all the GUI engines but I just can't work with so much clicking. With pure coding frameworks I have a sense of being in full control. Does that count as an advantage? Maybe... For me at least it is.
It may be... The tv is at my parents place. It's so frustrating and honestly enraging that this is possible or even legal!
August 13, 2025 at 8:59 AM
It may be... The tv is at my parents place. It's so frustrating and honestly enraging that this is possible or even legal!
As bad as it is the software would keep working. We bought a Smart TV about 6 to 7 years ago with Netflix. But they decided, that our TV won't get an update of the Netflix app anymore and the service requires a specific version to connect. So we now have a "broken" tv since we only watch Netflix...
August 13, 2025 at 6:17 AM
As bad as it is the software would keep working. We bought a Smart TV about 6 to 7 years ago with Netflix. But they decided, that our TV won't get an update of the Netflix app anymore and the service requires a specific version to connect. So we now have a "broken" tv since we only watch Netflix...
Yeah my day to day job is also JS/TS and I'm always longing to get cozy with rust after work :D
August 13, 2025 at 6:00 AM
Yeah my day to day job is also JS/TS and I'm always longing to get cozy with rust after work :D
The initial productivity boost from Copilot is a trade-off. By outsourcing design and algorithmic thinking, I failed to build a mental map of the code, making it feel foreign weeks later. The temptation is too great, so I deactivated it to prioritize my engineering skills over superficial speed.
August 13, 2025 at 5:59 AM
The initial productivity boost from Copilot is a trade-off. By outsourcing design and algorithmic thinking, I failed to build a mental map of the code, making it feel foreign weeks later. The temptation is too great, so I deactivated it to prioritize my engineering skills over superficial speed.
Definitely commit by commit. But sometimes colleagues put everything in a giant sole commit... The horror!
August 13, 2025 at 5:43 AM
Definitely commit by commit. But sometimes colleagues put everything in a giant sole commit... The horror!
Really interested in the outcome. I'm also really interested in zig but learning rust changed me. Any language without the safety guards feels like a battlefield... So that's what holding me back right now.
August 13, 2025 at 5:41 AM
Really interested in the outcome. I'm also really interested in zig but learning rust changed me. Any language without the safety guards feels like a battlefield... So that's what holding me back right now.
are there any official news about this? and what's the rationale behind this decision?
May 13, 2025 at 9:45 AM
are there any official news about this? and what's the rationale behind this decision?
Ah thank you very much! Was always wondering how to do stuff like this. Excited to skim through the code!
April 30, 2025 at 4:25 PM
Ah thank you very much! Was always wondering how to do stuff like this. Excited to skim through the code!
I guess this is not open source? 🥲
Awesome work! looks really clean!
Awesome work! looks really clean!
April 30, 2025 at 2:20 PM
I guess this is not open source? 🥲
Awesome work! looks really clean!
Awesome work! looks really clean!
In addition, anything that implements Drop is not allowed to implement copy.
doc.rust-lang.org/std/marker/t...
doc.rust-lang.org/std/marker/t...
Copy in std::marker - Rust
Types whose values can be duplicated simply by copying bits.
doc.rust-lang.org
April 20, 2025 at 6:48 AM
In addition, anything that implements Drop is not allowed to implement copy.
doc.rust-lang.org/std/marker/t...
doc.rust-lang.org/std/marker/t...
Very well written! I'd also add:
Strings/Vectors manage heap data and impl Drop. Their stack part holds pointer info. If Copy, these pointers duplicate, meaning multiple pointers reference the same heap data. Drop called for each then causes a double-free error. For memory safety, they are not Copy
Strings/Vectors manage heap data and impl Drop. Their stack part holds pointer info. If Copy, these pointers duplicate, meaning multiple pointers reference the same heap data. Drop called for each then causes a double-free error. For memory safety, they are not Copy
April 20, 2025 at 6:44 AM
Very well written! I'd also add:
Strings/Vectors manage heap data and impl Drop. Their stack part holds pointer info. If Copy, these pointers duplicate, meaning multiple pointers reference the same heap data. Drop called for each then causes a double-free error. For memory safety, they are not Copy
Strings/Vectors manage heap data and impl Drop. Their stack part holds pointer info. If Copy, these pointers duplicate, meaning multiple pointers reference the same heap data. Drop called for each then causes a double-free error. For memory safety, they are not Copy