o hai mark
This is all subjective, but because of nintendo’s bs, switch 2 is their first console I have almost zero interest getting. If your kids specifically really want the switch, they’ll be disappointed by anything else, but if not, I recommend looking into steam deck or other linux handhelds. There are lots of good PC games that fit the bill. Because of indie devs, the selection is should be a lot larger even.
Next up: the real reason we all stopped breathing oxygen
The bird could have been on a bombing run already.
These storefronts will allow viewers to … pick out products they’ve seen in their favorite shows
This should be funny but somehow it doesn’t do it anymore
What kind of magnet doesn’t rappel?
deleted by creator
“The simplest way” belongs both to occam and razor?
Because “biological weapons development” sounds a d v a n c e d
Warning: our product can be used for advanced high tech work!!!11
Headphone jack
Hey, they didn’t fuck everything up!
Not very likely. Translating cpu architectures is completely different from from what wine/proton does. A compatibility layer for arm would be even more difficult and expensive, and have a performance penalty. They might plan that for further into future though, if arm pcs take off. A Mac implementation would probably need a lot of apple-specific work, and there aren’t many mac gamers out there.
Oh boy, not this bullshit again
Prefix the name with what it’s for. For example, I’ve previously got a SoundFontError from opening soundfont file.
“Error” is already used by std::error::Error. It might not be imported by the code that imports your error type, but I think it’s better to give it distinct name.
The other thing is that you might want to use more than one library. Typical imports at the top of the file might look like this:
use bingbong::{BingBong, BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, CrotchidizerError};
If both libraries named their error enums just “Error”, the collision could be worked around, but it’s an unnecessary extra step:
// Not sure how renaming affects compiler hints.
use bingbong::{BingBong, Error as BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, Error as CrotchidizerError};
or if you want to avoid renaming:
use bingbong::{BingBong, SomethingElse};
use bogos::binted::crotchidizer::{self, Crotchidizer};
/* ... */
match result {
Ok(value) => return value,
Err(bingbong::Error::MissionFailed) => panic!(),
Err(bingbong::Error::UrMom) => todo!(),
_ => unreachable!(),
}
if let Err(crotchidizer::Error::SomethingsWrong) = result2 {
// ...
}
If the screenshot had followed conventions, the message would say something like this:
could not convert error type `BingBongError` to `MyAppError`
I don’t know if this will be attempt, but I helped. Godspeed, OP
You really should avoid naming your type plain “Error”
Thanks, I hate it.
Keith has some issues, but he will still get the job done.
I’ve been using obsidian notes for a lot of things. I have a kanban board there that goes buy->bought->in progress->finished->100%
The last step is pretty useless because I never even want to 100% a game. I should remove it. The main use for the board is so when I haven’t played anything in a long time, I can look and go “oh, I had that one going” and pick it up instead of starting some other new game.
A steamos device should be very much plug and play. I don’t know how good this would be in practice, but with a few clicks, non-steamos linux can be set to boot straight into steam’s tv interface, which has the necessary ui for power off, system updates, etc.