We have a new episode out, with James Ramey from Codeweavers (the key company developing WINE, which is a major component of Proton)! We have talked to James many times before, he is almost like a regular guest of our podcast at this stage – but this time was a good time to catch up with him. The Steam Deck is about to be released later in this year by Valve, and we wanted to better understand the following:
- How much did Codeweavers know about the Steam Deck before its announcement?
- What does the Steam Deck mean for Proton compatibility?
- What’s the future of the Steam Deck? How big of a product will this be?
- What does the Steam Deck mean for the console market?
- How likely is it that the Steam Deck will create a whole category of Handheld SteamOS-based devices?
You can find out more about all of this in this week’s podcast below:
Download: [MP3 File] | [OGG File] | Podcast RSS Feed
Credits for the INTRO and OUTRO music: jhaeka – check out their soundtrack at: https://joshuuu.itch.io/short-loopable-background-music
Note that Codeweavers is looking to recruit for new developers with C experience who are interested to join the ranks of other WINE developers – they welcome remote employees as well so you could apply no matter where you live as long as you have the skills they are looking for! Find out more on their jobs page.
We will have a transcript later in this week, so stay tuned!
BoilingSteam lets you access our content for free, but writing articles is a constant investment. We don't use ads or sponsporship, help us make our activities sustainable by donating via Patreon or LiberaPay if you prefer it anonymous. You can follow what we do via our newsletter, our RSS feed, our Mastodon profile or our Twitter feed. We also have Peertube, Youtube and LBRY channels. If you'd like to chat, you can also find us on #boilingsteam:matrix.org. (what is Matrix?)
no audio after the intro… (~5:00 – 50:00)
Have you tried falling back to the MP3 and OGG file links?
I noticed some issues with the player too. When I closed the browser and opened it again, and then clicked to the minute mark I was previously at, there was only silence. The ogg file seems fine so far.