

I’ve had mine on vibrate for years. Texting doesn’t trigger it, only calls. It’s been great. I look at my phone only when I’m ready to look at it.
I’ve had mine on vibrate for years. Texting doesn’t trigger it, only calls. It’s been great. I look at my phone only when I’m ready to look at it.
I prefer to just throw the state into a database. Each table has their own “repository” type that knows how to save/load models and then I have “manager” types that use “repository” types to compose larger, feature-specific domain models.
I usually just use Sqlite for it’s simplicity but I’m not opposed to Postgres via Docker.
When your management judges teams by lines-of-code written.
I’m surprised this doesn’t already exist.
After many years of using SO, I’ve started using ChatGPT for all of my programming questions and have not looked back once. For my usual “I know X is possible, but how do I do that in Y language” questions, it’s been a dream using ChatGPT.
In Rust, using the Option and Result types make the general flow of the application much easier to organize, make modular, and reuse.
This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: “Both of these functions check the same thing, but parseNonEmpty
gives the caller access to the information it learned, while validateNonEmpty
just throws it away.”
In what scenario could the first character be a newline character? I think that if-statement may be unnecessary, but I never use raw user input like you are here.
I’m not sure that you need a range when pulling the character from the input
variable. Simply input[i]
and input[input.len() - i - 1]
should work.
Boo, just missed it.
Is this already in a crate? I’d be happy to change over from rusqlite to limbo, at least for the async functionality.
Do you happen to know of a few situations where bloom filters are super useful? I need to identify when to use them.
I understand that the macro only affects compile time but I’m talking about the extra function that’s included in the resulting source code when the macro is expanded during compile. Based on other feedback, it looks like the unused function is optimized away.
This was a great post, but is the last state of the macro actually bad for performance in any way? I get that it’s ugly (and we should only choose to make code less readable like this when there’s actually an issue) but is it worse for runtime performance?
Oh, okay. Thank you for clarifying. So doesn’t that mean we should never have a compiler written in the same language that it compiles? Why would we ever choose to make the mistake of using the same language? Is it ever not a mistake?
Why would a Rust compiler written in C be more trustworthy than one written in Rust?
If the idea is that, in an ideal world, we would compile each layer of compilers from assembly-up-to-Rust for each build, that seems even more risky as then you have to trust each compiler instead of just one.
I’m still lost on why they’re doing it.
The idea that someone would introduce the verbiage “garbage collection” in the context of Rust is crazy to me. I hope they change that to “file cleanup” or… anything else.
AI is surprisingly helpful with providing a starting point. When you want a helloworld app, an example of how to use some part of a crate, or a code snippet showing how to take what you have and do something unusual with it, AI is super useful.
I would love to be able to get the same quality of AI locally as I do from ChatGPT. If that’s possible, please let me know. I’ve got two 3090s ready to go.
But for now, I’m just enjoying the fact that ChatGPT is free. Once they put up a pay wall, it’s back to suffering (or maybe/probably trying out some open-source models).
I don’t know anything about
screen
. I think it would be great if you included a niceREADME.md
file in the root of your repo for explaining what screen is and what your repo does both differently and the same. Please let me know if you do that. I’ll come and check out the repo at that point - kinda hard for me to want to jump directly into the code at the moment.