Comment on what happened to kbin?

• Chozo@fedia.io ⁨5⁩ ⁨months⁩ ago

  I believe that currently, Mbin isn't making any drastic changes, and relying mostly on Kbin's existing code as its base. As far as I'm aware, the Mbin team are mostly just doing maintenance-level development; fixing things as they break and making optimizations, but not so much in the way of developing new features. Mbin is currently just basically a copy of Kbin, without much distinguishing the two.

  Since Kbin doesn't seem to be moving much at all, I think it might be a good idea for Mbin to start flexing their own muscles a bit, and making it into its own separate project. Otherwise, having a copy of a stale project just leaves you with two stale projects.

  source

  • originalucifer@moist.catsweat.com ⁨5⁩ ⁨months⁩ ago

    youre not wrong, they spent a lot of time refactoring things, and still are.

    that said, the list of changes in the last several versions is very long, and the code base is no longer trivially similar. looking through the waiting prs, there are a lot of interesting bits like extending microblog AP connectivity (tag handling).

    the mbin guys have been pumping out releases steadily since the fork, including implementing managed documentation and version numbering. it has well exceeded kbin at this stage.

    theyre prepping for a 1.7 release soon. when was the last kbin update? to me, theres only one stale project here.

    source

    • Chozo@fedia.io ⁨5⁩ ⁨months⁩ ago

      Thanks for the insight! I'm not super familiar with how the development cycle goes, so my thoughts are coming from the standpoint of a user experiencing both platforms. I'm sure that a lot of the back-end stuff has probably had a lot of improvements, but the end-user experience between Kbin and Mbin are still largely identical, I feel.

      I was gonna load up Kbin to try to do a live comparison but, uh... Yeah, who knows when that'll be possible again lol

      source