sugar_in_your_tea

u/sugar_in_your_tea@sh.itjust.works
67 posts · 19.8k comments

Recent posts

Recent comments

It all depends on what you're looking for. I've put hundreds of hours into games and gotten way less than $1/hr, and I've also had a great experience paying significantly more.

So I don't see games in terms of $/hr, especially these days when I'm more limited by time than money. Instead, I look for unique experiences with cost being a much lower factor. Generally speaking, I spend much less than $1/hr since I buy a lot of older games, but I've spent far more ($5-10/hr) on particularly interesting games.

But yeah, generally speaking, I'm willing to pay more for indies than AAA titles because indie games are more likely to offer that unique experience.

on technically true · c/funny · 8 pts · 291d

American tourists escaping Prohibition

Wait, they banned salads along with the booze? That's too far!

on History channel after 12 AM · c/funny · 5 pts · 291d

early 2000s

Nothing good happened in that time period:

  • .com crash and the lost decade
  • 9/11 and the TSA/Patriot Act nonsense that followed
  • Bush, and the start of Iraq and Afghanistan wars
  • Dreamcast discontinued, and Sega drops out of the console market (duopoly ensues)

And of course History, Discovery, etc turning to utter crap.

on oregano bitch · c/funny · 5 pts · 291d

No, that's an ornithologist.

An orgasm is the term used to refer to relative positions in a set.

As a manager of sorts, I already know if people are doing their job: the work gets done. I'm involved enough to know how much time their work should take and see through their BS since I do similar work.

Maybe these bosses should do the same: do similar work and you'll know when they're BS-ing you.

Why? Look at how many people here say they want Steam OS, and Lemmy skews heavy toward Linux users. This is that, but OOTB.

I don't think it'll sell anywhere near as well as the Steam Deck, but it's also a less exciting form factor. I do think it'll sell a fair number of units though.

The cheapest equivalent prebuilt I can find with similar specs (RX 7600 is slightly better than the Steam Machine) is $850, and a DIY build is more like $900 (lots of corners cut), so there's probably not much margin on the prebuilt. Valve is probably saving some cash with their custom CPU, and they're probably shipping it with a Steam Controller, hence the $800 target. If component prices rise significantly before launch, I could see $1k.

Eh, I don't particularly enjoy building PCs, but I do it because it's cheaper, esp. for upgrades. I'm really not the target market for this.

That said, this is the right product for a lot of people. Many don't want to mess with their gaming system, they want it to just work. That's why consoles are popular, and the Steam Machine being a bit more expensive than a console and get access to Steam's catalog is very attractive to a lot of people, especially if it otherwise works like a console.

I see you ignored my entire comment.

No, I responded to the relevant part. I was using segfault as a metaphor, not arguing that it's actually the same mechanism underneath. If you're getting panics in production code, I consider that just as much of an emergency to fix as a segfault, and Rust helpfully gives you stack trace info with it. It's not the same idea as an exception, which could signify an unrecoverable error or an expected issue that can be recovered from.

I don’t know what is more explicit about expect

It forces you to write a message, so most temporary uses will be unwrap(). I use unwrap() all the time when prototyping for the happy path, and then do proper error handling later. This is especially true in larger projects where I can't just throw in anyhow or something and actually need to map error types and whatnot. I don't use expect() much (current hobby project has 4 uses, 3 for startup issues and 1 for hopefully impossible condition) but I think it makes sense when there's no way to continue.

But yes, unwrap() is perhaps the first thing I look for as a reviewer, which is why it's so surprising that this is the issue. At the very least, it should have been something like expect("exceeds max file size"). I personally prefer explicit panics in production code, but expect is close enough that it's personal preference.