Thread overview
The future of the DOOR, DASFOR and SSON projects
Jul 31
Doigt
Aug 01
Kapendev
Aug 01
Doigt
July 31

As some of you are aware, I maintain some niche libraries that have barely any following, but just in case someone is using any of my packages, I would like to emit the following warnings:

  1. I will drop support for DASFOR and SSON. Those packages will no longer be maintained, effective immediately. If you wish to take over those repos, it can be arranged.
  2. I am working on a replacement for SSON. I don't know when it will be ready.
  3. DOOR will no longer stay on raylib-d 4.0.2. Moving forward, I will try to keep up with latter raylib-d releases. The reason I was holding out was because the initial plan was to swap the backend from raylib-d to draylib, but that is no longer going to happen. The backend is going to keep being raylib-d. That also marks the end of my involvement with draylib as I have left the project this morning (in good terms).
August 01

On Thursday, 31 July 2025 at 14:24:21 UTC, Doigt wrote:

>

As some of you are aware, I maintain some niche libraries that have barely any following, but just in case someone is using any of my packages, I would like to emit the following warnings:

  1. I will drop support for DASFOR and SSON. Those packages will no longer be maintained, effective immediately. If you wish to take over those repos, it can be arranged.
  2. I am working on a replacement for SSON. I don't know when it will be ready.

Didn't know SSON was a thing. Looks interesting.

August 01

On Friday, 1 August 2025 at 04:07:01 UTC, Kapendev wrote:

>

On Thursday, 31 July 2025 at 14:24:21 UTC, Doigt wrote:

>

As some of you are aware, I maintain some niche libraries that have barely any following, but just in case someone is using any of my packages, I would like to emit the following warnings:

  1. I will drop support for DASFOR and SSON. Those packages will no longer be maintained, effective immediately. If you wish to take over those repos, it can be arranged.
  2. I am working on a replacement for SSON. I don't know when it will be ready.

Didn't know SSON was a thing. Looks interesting.

Unfortunately, SSON's code wasn't written to scale up. I want to add new features to it, but the code is unwieldy. Rather than lose my time trying make it work, I'm throwing it in the trash and starting over.