Skip to content
EN

Back to the catalog

A running log of announcements, projects and accomplishments.bret.io
jsonEnglish

bret.io

bret.io · English

A running log of announcements, projects and accomplishments.

json

Open the feed

https://www.bret.io/feed.json

Last post
Mar 27, 2026
Posts in 24 h · 7 days · 30 days
0 · 0 · 0
Our last check
Answering
Served from
United States
Text score at discovery
10,132
Format
json

Posts

What our queue read from this feed. Open one to read it here, or go to the site that published it.

  1. (Sold) Buy my graphics card
    Mar 27, 2026 · original
    Update : Sold! I’m selling my graphics card from my You can just build a Steam Machine blog post. GIGABYTE Radeon RX 7700 XT GAMING OC 12GB GDDR6 Graphics Card I ended up upgrading to a 9070xt for better 4k performance on the large TV, will post more details later, but in the meantime, you can buy the card on ebay!
  2. Simple TanStack Query with Preact
    Feb 7, 2026 · original
    Update About three days after writing this, TanStack released a native Preact TanStack Query adapter ! Just use that and ignore the rest. Thanks to everyone involved in that. ( @tanstack/preact-query ) Here is a simple approach to getting @tanstack/react-query working in a preact project. I’m certain I’m not the only person to arrive at this, but I also didn’t manage to find anyone suggesting this under the noise of your usual bundlerslop tutorials. I’m intentionally trying to write this at more of a beginner’s level, so if anything is confusing, feel free to ask questions. @tanstack/react-query internally imports and defines as a peerDependency react (meaning they need to be installed together in your project). When running a preact project, react generally shouldn’t be installed, so it will be missing, or auto-installed alongside @tanstack/react-query in newer versions of npm (we don’t
  3. You can just build a Steam Machine
    May 8, 2025 · original
    I built a “Steam Machine” in 2024. I’ve run it for 8 months, and I’m really happy with it! I hope that after reading this, you’ll be encouraged to build one too! Why yes, that is a 65", HDR OLED Steam Deck in my living room. I’m running the latest Steam OS 3.7 (the OS running on the Steam Deck ) on conventional AMD desktop hardware, running at equal or improved performance over Windows. We’re here! You can just build a Steam Machine now, and get a console-like experience running PC games in your living room, on Linux, with great controllers, on your 4K OLED TV (and surround sound if you have it), running in parity with your Steam Deck. The OS (SteamOS 3.7) The OS to install is SteamOS 3.7. It’s available in Valve’s “preview” update channel for the Steam Deck, but you can download the recovery image and try installing it on anything. There isn’t much more to say about this, other than yes
  4. It's Time to Install SteamOS 3.7
    May 8, 2025 · original
    I recently installed SteamOS 3.7 on my commodity AMD HTPC , and it’s working great. Here’s my procedure and notes. Installing SteamOS 3.7 (This will go stale quickly, but as of this writing, it works.) EDIT 3 : A New SteamOS Home Page has been released echoing most of the information written here. EDIT 2 : 3.7 Has been released to the stable channel . Running updates on the stable channel will get you to a working state. EDIT 1 : As of writing this, 3.7 has been promoted to BETA , so check the system version you get on the hop to Beta. If you get to 3.7, you are good to go! Prep Tips The recovery image installs SteamOS 3.5 3.7 or later. Discrete GPUs just work now. SteamOS 3.5 has limited hardware support. On desktop systems, enable integrated graphics and plug your monitor directly into the integrated HDMI or DisplayPort during installation. Some discrete GPUs I tested failed to boot St
  5. Bazzite isn't SteamOS (and that's ok!)
    May 8, 2025 · original
    I’m thrilled to see Linux becoming a more viable platform for PC gaming, and it’s awesome to see so many new Linux users joining the scene. Unlike commercial operating systems that pay people to clarify and simplify product details, open source exposes users to maximum complexity, clarification, and particularities (IT’S GNU/LINUX!!). With a new generation of users, it’s helpful to know when apples are apples and oranges are oranges. SteamOS, being a Linux distro, is no different. There are quite a few things being called “SteamOS” these days in YouTube tutorials, so I figured I could help clear things up. graph TD SteamOSDebian["🎮 SteamOS (Debian)"] SteamOSArch["🎮 SteamOS (Arch)"] SteamFork["🛠️ SteamFork"] HoloISO["🌈 HoloISO"] ChimeraOS["🔥 ChimeraOS"] Bazzite["🔧 Bazzite"] SteamOSDebian SteamOSArch |derived from| SteamFork SteamOSArch |derived from| HoloISO ChimeraOS |pulls from| S
  6. I Love Monorepos—Except When They Are Annoying
    Mar 9, 2025 · original
    I love monorepos, but monorepos can be annoying, especially in open source. They make sense in some cases, but they come with a lot of baggage and patterns I’ve noticed over the years—so I need to write about them. I’m primarily talking about JS-based “monorepos,” a.k.a. workspaces when used in open source packages, but the whole space is confused enough that I might stray a bit. Historical Context JS monorepos (or “workspaces”) emerged with tools like lerna , later influencing similar features in npm , yarn and pnpm . At their core, they allow developers to: Develop and publish multiple npm packages from a single git repository Streamline dependency management with automatic linking and consolidated lockfiles Allow for varying direct dependency versions in a single repo This approach gained popularity largely as a response to: The frustrating fragility of npm link React’s “unique” const
  7. "Don't Be Evil" Is An Excuse For Evil
    Oct 3, 2024 · original
    Google’s former and founding motto “Don’t be evil” sounds benevolent, but is it? The original Google motto. “Don’t be evil” paired with the companies premise: lets build products in a way that allows for immeasurable corporate access into people’s private lives for fun and profit, unlocking all the positive potential this data can provide. We’ll only use it for good, the Evil™️ things will just be off limits. Of course the motto changes to “Do the right thing” in 2015 when it’s very obvious it’s impossible Google to not indulge in the Evil with the potential for it sitting right there. By loosening up the motto to allow for at least some Evil, so long as its the “right thing”, Google can at least be honest with the public that “Evil” is definitely on the table. Maybe its time to demand “Can’t be evil”? Build in a way where the evil just isn’t possible. Reject the possibility of evil in w
  8. The Art of Doing Science and Engineering
    Feb 13, 2024 · original
    The art of doing science and engineering : Learning to Learn by Richard W. Hamming Richard Hamming’s “The Art of Doing Science and Engineering” is a book capturing the lessons he taught in a course he gave at the U.S. Navy Postgraduate School in Monterey, CA. He characterizes what he was trying to teach was “style” of thinking in science and engineering. Having a physics degree myself, and also finding myself periodically ruminating on the agony of professional software development and hoping to find some overlap between my professional field and Hamming’s life experience, I gave it a read. The book is filled with nuggets of wisdom and illustrates a career of move-the-needle science and engineering at Bell Labs. I didn’t personally find much value in many of the algebraic walk-through’s of various topics like information theory, but learning about how Hamming discovered error correcting
  9. async-neocities has a bin
    Jan 15, 2024 · original
    async-neocities v3.0.0 is now available and introduces a CLI. Usage: async-neocities [options] Example: async-neocities --src public --help, -h print help text --src, -s The directory to deploy to neocities (default: "public") --cleanup, -c Destructively clean up orphaned files on neocities --protect, -p String to minimatch files which will never be cleaned up --status Print auth status of current working directory --print-key Print api-key status of current working directory --clear-key Remove the currently associated API key --force-auth Force re-authorization of current working directory async-neocities (v3.0.0) When you run it, you will see something similar to this: async-neocities --src public Found siteName in config: bret API Key found for bret Starting inspecting stage... Finished inspecting stage. Starting diffing stage... Finished diffing stage. Skipping applying stage. Deploy
  10. Reorganized
    Dec 2, 2023 · original
    Behold, a mildly redesigned and reorganized landing page: It’s still not great, but it should make it easier to keep it up to date going forward. It has 3 sections: Featured Projects : important projects of note. Recent Posts : now that this site has proper blog support, I can highlight recent posts on the landing page. Open Source : interesting and notable projects that have found some use and that I still maintain. This section now includes a bunch of open source work from the past year that I’ve never had time to write about. Past projects : inactive projects that are not longer active, but still interesting enough to share. I removed a bunch of older inactive projects and links and stashed them in a project . Additionally, the edit button in the page footer now takes you to the correct page in GitHub for editing, so if you ever see a typo, feel free to send in a fix! Finally, the abo

Discovered by the rss-feed-index crawler, which checks each feed at most once a month.

Same record as JSON: https://api.agentalog.com/api/feeds/fd_bret_io_7f545419eed4a4d1. More from this site: bret.io in the Feeds tab.