So, last I checked you could still buy PCB mountable sockets for them, bit does anyone know if anyone's still manufacturing NES-compatible controllers?
All bluetooth audio devices should be required to have a button on them to disconnect and re-enter pairing mode without the device they're connected to relinquishing control.
What if the reason we've never seen a time traveler isn't because it's impossible, but because humanity is going to wipe itself out before anyone figures out how?
Building a small personal project in #Rust to teach myself the language. As I was looking over my code, I noticed a mistake I'd made that technically worked, but was kind of silly so I fixed it.
This got me to wondering if Rust had a linter (it does) because surely I'd made other similar rookie mistakes. I found the linter and ran it on my project. It came back with one result that I already knew about: a value in a struct that doesn't get read because I haven't written that code yet. That was it.
I was surprised. It's still a very small project, but perhaps I'm a more competent developer than I give myself credit for.
I wan to use the current_local_offset function from the time library, but I apparently need to import it into my project with the local-offset feature.
I assume I need to specify this in Cargo.toml but for the life of me, I can't figure out how. Can someone point me in the right direction?
I've been holed up in the (home) office for most of the day (not uncommon). I happened to look out the window and noticed that our building was surrounded by cops.
Interesting.
Turns out they arrested one of the downstairs neighbours... for what, I don't know.
Here's the interesting bit though: apparently, the landlord offered them the key to the apartment, but they couldn't legally use it because there was no warrant. I guess that makes sense, but while they weren't allowed to to that, they apparently were allowed to enter the apartment by prying a window open or kicking the door in. In what world does that make any sense?
@me My actual guess is that it's easier to justify forcefully entering the apartment because there would be some "safety concern" if you actually entered forcefully.
People who don't like #Rust: why specifically don't you like it?
I'm in the process of learning it now. There are definitely some things about the language that I can see some as finding irritating (i.e.: the borrowing system). Personally though, I'd rather have a dozen complie-time errors than a single runtime error. This is the reason I tend to gravitate towards Haskell, for instance.
It's certainly not the right language for everything, but if you want better safety in code that needs to be highly efficient, it seems a reasonable alternative to C/C++.
@me@screwtape when I first looked at rust, the concepts in the docs made sense but writing code was difficult. I put it down for 6 months and when I came back the curve was more natural. I think there's just a necessary bake period for the consequences of the simple concepts and their interactions to become intuitive, practical, applicable patterns. Main piece of advice I'd give is "keep calm and call clone". It will look "inefficient", but it will get you unstuck to learn the rest of the lang.
@ekuber@me@screwtape Do you still find it necessary to use clone a lot? I resisted -- not on the basis of efficiency, but wanting to understand the language's approach to handling memory -- and found it wasn't often needed.
So, options for newcomers include:
The "steep route": avoid cloning until you learn to work "with the grain" of the borrow checker.
The "gentler route": clone liberally until you're comfortable with the rest of the language, and then try to understand ownership.
Today while I was out, I saw a guy at a busy intersection holding a handwritten sign. Obviously, I assumed he was panhandling, because people frequently do that there.
As I approached, I saw that his sign only had a URL on it. Out of curiosity, I visited it. Turns out it was some bitcoin mining scam.
While this was definitely a novel marketing approach, I wonder how they figured this particular tactic would instill confidence in anyone...
Sitting in a waiting room in a medical imaging place and they have an ad for their app to get your results on a mobile device. Among other things, it reads:
"Permanently store them with bank level encryption" (emphasis theirs)
In my experience, if banks are their gold standard of #infosec, I really don't want my medical data anywhere near this system. Just sayin'.
I don't like that a literal 0 is accepted as a null pointer. I just spent an embarrassingly long time tracking down a segfault because in an attempt to zero out a buffer, I accidentally used memcpy(&buf, 0, sizeof(buf)) instead of memset(&buf, 0, sizeof(buf)).
@me This was a specific design decision, not due to lack of ability to implement a warning around. You can use acid(1) on the broken proc to get the exact source line that the code crashed on. Which can help narrow down the cause of a segfault.
Katy and I have made the trek out to this little #KoreanBBQ place downtown Kitchener almost every Sunday for the past several months now. Every time we do, We're once again shocked at how good it is. You'd think we'd have just gotten over it by now, but not so. #KWAwesome#WRAwesome#DTK