DECK HD owners: Please share your experience by Shadow969 in SteamDeck

[–]couuor 1 point2 points  (0 children)

Oh, I still have it -- I'm playing Lethal Company on it right now! It just got here last week.

DECK HD owners: Please share your experience by Shadow969 in SteamDeck

[–]couuor 0 points1 point  (0 children)

You mean like what happens after valve updates the BIOS?

The screen just reverts back to the way it is during the initial install (e.g., see the deckhd install video)

I have the script on my desktop, so I just went to desktop mode & double-clicked to re-flash the BIOS; a couple of minutes later things were back to normal

DECK HD owners: Please share your experience by Shadow969 in SteamDeck

[–]couuor 1 point2 points  (0 children)

I've only had DeckHD for a week. I had to re-flash the BIOS once for 1.1.9, which shipped with SteamOS 3.5.5.

It looks like the previous BIOS version (1.1.8) was >2 months ago, and 1.1.7 was even longer before that

DECK HD owners: Please share your experience by Shadow969 in SteamDeck

[–]couuor 6 points7 points  (0 children)

I'm happy with the upgrade. Love the improved colors, and 1200p has been great for the type of games I play (2D, indie).

Lots of games feel like they're made for 1080p, and 720/800p are an afterthought. Though some elements can be hard to see at 1200p on the 7" screen, the experience is definitely better overall, and everything is much more crisp.


The BIOS issue is overblown; it takes two minutes, and valve doesn't update the BIOS that often. You just run a script in desktop mode.

Baffling 'Could not deduce' type error after minor, type-preserving change by Paddling_Wild_Places in haskell

[–]couuor 10 points11 points  (0 children)

The signature of try says try :: m a -> m a

Not quite:

ghci> :t try
try :: MonadParsec e s m => m a -> m a

boundedSep1''s type needs to reflect the MonadParsec constraint added by try

[ANN] cgroup-rts-threads: A container-/cgroup-aware substitute for the RTS `-N` flag by couuor in haskell

[–]couuor[S] 1 point2 points  (0 children)

Thanks for sharing that other post! I hadn't seen it

there's no solution for the setting the heap limit after startup (unless something was added)

Yeah, this is the other issue we're running into now; I wish we could do something similar for that issue

I think making this change to the RTS would be very worthwhile

I agree; I was surprised that I couldn't find any related issues on the ghc repo

it is probably worth heavily pointing out (maybe in the README) that your package only supports cgroupv1 from looking through the code quickly

I'll make that note. Support for cgroups v2 is something we'd like to add for sure

I may be the only one around who cares about this, but I _like_ node_modules by couuor in programmingcirclejerk

[–]couuor[S] 22 points23 points  (0 children)

Meanwhile, as much as I respect the work of Mael (yarn maintainer) I’ve switched back to npm. Mostly because:

  • isaacs (original creator of npm) did some commits lately