# Richard Jones Logbook / blog / devlog This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bevygap: Autoscaling multiplayer Bevy game servers with Edgegap & Lightyear DevFeed: [Bevygap: Autoscaling multiplayer Bevy game servers with Edgegap & Lightyear]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2024-12-09T06:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [Bevy](), [autoscaling](), [inference-endpoints](), [Docker](), [GitHub Actions](), [API](), [Latency](), [wasm]() Tags: [api](), [autoscaling](), [bevy](), [bevygap](), [docker](), [edgegap](), [game-servers](), [gamedev](), [github-actions](), [latency](), [multiplayer](), [netcode](), [rust](), [wasm]() ### AI overview This article describes adapting the Lightyear spaceships example into a server-authoritative multiplayer Bevy game and deploying its client and headless server with Docker. It explains using Edgegap to deploy game servers in suitable locations on demand and autoscale them in response to player demand, with supporting infrastructure including GitHub Actions and NATS. ### Source excerpt If i'm going to write a server-authoritative multiplayer game, it would be nice to have a decent way to deploy it. Especially to deploy servers around the world in response to player demand, to autoscale and keep latency down. ## Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy DevFeed: [Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2024-12-08T06:00:00Z Content type: tutorial Language: en Sources: [Richard Jones]() Topics: [browser](), [browser-game](), [realtime](), [Bevy](), [Rust](), [QUIC](), [WebRTC](), [HTTP](), [Streaming]() Tags: [bevy](), [bevygap](), [browser](), [gamedev](), [http-3](), [multiplayer](), [netcode](), [quic](), [realtime](), [rust](), [snapshots](), [udp](), [webrtc]() ### AI overview This article discusses building a realtime multiplayer browser game with Rust and Bevy. It explains why TCP can delay updates, considers WebRTC and WebTransport over HTTP/3 and QUIC for unreliable data channels, and introduces snapshot interpolation as a multiplayer networking model. ### Source excerpt How hard it is to build a realtime multiplayer browser game? Like asteroids, but multiplayer. Retro vibes with modern netcode 🚀. ## A blog redesign and an exploratory Rust multiplayer game project DevFeed: [A blog redesign and an exploratory Rust multiplayer game project]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2021-07-29T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [border-image](), [Media Queries](), [Rust](), [WebAssembly](), [Web Development](), [WebRTC](), [Bevy](), [render]() Tags: [bevy](), [css](), [life](), [mobile](), [mobile-web](), [render](), [rust](), [wasm](), [webassembly](), [webrtc]() ### AI overview The author describes updating the blog with responsive CSS and migrating comments to GitHub issue comments while experimenting with a browser-based multiplayer game in Rust, WebAssembly, WebRTC, and Bevy. ### Source excerpt I have dragged my blog, kicking and screaming, into the era of media-queries and responsive CSS. So now it's readable on a variety of screen sizes. My first post was roughly the same year the iPhone 3G came out I think, and the mobile web wasn't really a big deal back then. ## BigWig: A better Erlang webtool (spawnfest entry) DevFeed: [BigWig: A better Erlang webtool (spawnfest entry)]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2011-07-11T05:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Programming](), [Web](), [WebSocket](), [systems]() Tags: [appmon](), [architecture](), [erlang](), [etop](), [json](), [processes](), [programming](), [realtime](), [sasl](), [spawnfest](), [web](), [webtool]() ### AI overview The article describes BigWig, a web-based suite of Erlang tools created during Spawnfest. It presents process inspection, process information, application hierarchy exploration, SASL report browsing, and VM dashboards, using Cowboy and WebSockets; some parts were unfinished. ### Source excerpt This weekend, Steve, Hunter, Paul and I took part in Spawnfest, a 48-hour Erlang programming event. ## Erlang rebar tutorial: generating releases and upgrades DevFeed: [Erlang rebar tutorial: generating releases and upgrades]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2011-03-26T05:00:00Z Content type: tutorial Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Tutorial](), [releases](), [Development](), [make]() Tags: [appup](), [code](), [deploy](), [development](), [erlang](), [gnu-linux](), [make](), [otp](), [production](), [programming](), [project](), [rebar](), [releasehandler](), [releases](), [sasl](), [tutorial](), [upgrades]() ### AI overview A tutorial on using rebar to structure, compile, package, deploy, and upgrade Erlang applications. It demonstrates creating releases that bundle the Erlang VM, required OTP libraries, application code, and dependencies, enabling installation of new versions without downtime. ### Source excerpt During my experiments with rebar, I made a simple example app for testing upgrades and releases. This article will walk you through using rebar to create an application, lay it out properly, package and deploy it, and create and install new versions without downtime. ## Erlang/OTP releases: rebar, release\_handler, .appup, etc DevFeed: [Erlang/OTP releases: rebar, release\_handler, .appup, etc]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2010-09-18T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Erlang](), [releases](), [upgrade](), [modules]() Tags: [appup](), [deployment](), [erlang](), [hacks](), [irc](), [irccloud](), [mochiweb](), [otp](), [programming](), [release](), [releases](), [sasl](), [sysops](), [upgrade]() ### AI overview An Erlang developer describes deploying live upgrades for running OTP applications behind an in-browser IRC client. The article discusses release packaging, release_handler, .appup files, rebar, and an upgrade from R13B to R14 after encountering upgrade-related problems. ### Source excerpt I've been building something in Erlang recently, provisionally called IRCCloud.com (mention this post if you request an invite!) - it's an in-browser IRC client that stays connected for you all the time, so you never miss the conversation. You can reopen your browser later and still have all the backlog. IRC is damn useful, and James and I are building IRCCloud to give you the advantages of IRC bouncer-esque functionality, with the ease of just opening a webpage. ## Rewriting Playdar from C++ to Erlang: source-code savings and similar resource use DevFeed: [Rewriting Playdar from C++ to Erlang: source-code savings and similar resource use]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-10-21T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Erlang](), [C++](), [Code](), [cross-platform](), [Optimization]() Tags: [c](), [c-plus-plus](), [code](), [cross-platform](), [erlang](), [optimization](), [playdar](), [programming](), [rewrite]() ### AI overview The author describes rewriting Playdar from C++ to Erlang after initially developing it with Boost, Asio, and CMake. The Erlang version reached near feature parity within a week, and counting bundled third-party code while excluding Boost and Asio showed a 92% reduction in source lines. Preliminary comparisons found similar CPU and memory usage overall, with Erlang using slightly more memory at the time of writing. ### Source excerpt I've heard many anecdotes and claims about how many lines of code are saved when you write in Erlang instead of [C++/other language]. I'm happy to report that I now have first-hand experience and some data to share. ## Erlang talk at London Hackspace DevFeed: [Erlang talk at London Hackspace]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-10-08T05:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Programming](), [Functional programming](), [Processes]() Tags: [code](), [distributed-systems](), [erlang](), [functional-programming](), [hackspace](), [london](), [messages](), [mochiweb](), [playdar](), [processes](), [recursion](), [state](), [talk](), [uncategorized](), [upgrade]() ### AI overview This article recaps an introductory Erlang talk at a London Hackspace meetup. It explains Erlang's use for scalable, reliable distributed systems and demonstrates processes, message passing, recursive state management, hot code reloading, and gen_server. ### Source excerpt Last night I gave an "Intro to Erlang" talk at a London Hackspace meetup. I did a quick audience survey first: About 75% did "web programming" (ruby,python,php,etc). Around 30% admitted to regularly using C/C++/Java or desktop/mobile app development. Less than 10% had much experience with functional programming. ## Anti-RDBMS: A list of distributed key-value stores DevFeed: [Anti-RDBMS: A list of distributed key-value stores]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-01-19T06:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Databases](), [Replication](), [data](), [Algorithms](), [cloud-computing]() Tags: [algorithm](), [algorithms](), [couchdb](), [data](), [database](), [databases](), [dht](), [distributed](), [dynamo](), [erlang](), [hadoop](), [hashing](), [http](), [java](), [nosql](), [programming](), [rdbms](), [replication]() ### AI overview This article presents research notes on distributed key-value and document stores that could replace groups of relational database shards under suitable conditions. It discusses use cases, replication and partitioning concerns, related systems and background research, while noting that the material was written in January 2009 and may be outdated. ### Source excerpt Please Note: this was written January 2009 - see the comments for updates and additional information. A lot has changed since I wrote this. ## How we use IRC at Last.fm DevFeed: [How we use IRC at Last.fm]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2009-01-08T06:00:00Z Content type: article Language: en Sources: [Richard Jones]() Topics: [IRC](), [Development](), [Monitoring](), [Java](), [PHP](), [Command-line interface](), [Deployment](), [issue tracker](), [Testing]() Tags: [channel](), [commands](), [deployment](), [irc](), [issue-tracker](), [java](), [lastfm](), [monitoring](), [php](), [programming](), [server](), [tests]() ### AI overview This article explains how Last.fm uses IRC for team and company-wide communication, automated monitoring, and developer support. It describes the irccat bot, which forwards network messages to IRC, sends operational events such as commits, alerts, deployments, and test results, and exposes lookup and administrative commands through PHP handlers. ### Source excerpt Everyone that works at Last.fm is typically connected to our IRC server. We have different channels per team, as well as a company-wide channel, and a few channels dedicated to automated monitoring.