Skip to main content

Progress is Progress

· 2 min read
Whirlsplash Core Team

A lot has happened since the last blog post.

What has happened#

For starters, the Go rewrite which was previously mentioned has been scraped for now. A complete rewrite has been performed once again in Rust -- the original plan.

I will soon be publishing the current (rewrite) source of Whirl within the official GitHub repository as new development branch.

Issues that remain#

There are still few issues which are present such as a known issue where the client is not properly transferred over to the Hub (RoomServer) when it is finished communicating with the Distributor (AutoServer). This issue is only apparent about 50% of the time but it is still of high priority. You can find it's corresponding GitHub issue here.

But does it work ?#

Despite these setbacks, issues, et cetera, the implementation is functional as you can see in the image below.

Client connected to server

The Distributor (AutoServer) is close to 95% functionality (compared to the official servers), where as the Hub (RoomServer) is estimated to be at ~5 - ~10% functionality.

Plan (s) going on#

In the following weeks, focus will be aimed at (priority as follows);

  1. Fixing the Distributor to Hub transfer issue

  2. Implementing more of the Hub's known features

    • No specifics, features will be implemented as I see fit and will be based mostly off of their priority in the functionality of the Hub (RoomServer).

      E.g., is "a" needed for "b" to work? is "c" important right now?

The State of Whirl

· One min read
Whirlsplash Core Team


This is outdated! Any information found in this blog post may have been changed.

This probably won't come as a surprise to anyone, however, further development on Whirl has been halted.

Rust and TCP has been quite a pain to work with and I've been exploring other language candidates. Currently, I'm in the progress of performing a complete rewrite of Whirl in Go.

What does this mean for Whirl? This will be a considerable setback in terms of when Whirl will be considered stable. My estimates place Whirl to be stable for production near Q3 of this year (2021).

Once the Go rewrite is functionally equal to that of the current Rust implementation, I will be publishing the progress on Whirl's GitHub repository.


· One min read
Whirlsplash Core Team

Welcome to the new and improved Whirlsplash guide and blog!