Conversation

Notices

1. Embed this notice
   Rev. Onan Canobite, SubGenius (onan@dobbs.town)'s status on Tuesday, 16-Aug-2022 08:49:41 JST Rev. Onan Canobite, SubGenius

   in reply to

   • Elda King

   @eldaking One of the goals of urbit is to write a core system that never changes. Once the central part is done (and they seem close) it will not change again. There will be layers over it, and those layers will change and come and go, but that core will be solid. This will of course have its costs and benefits, just like some of the existing longer-term protocols have costs and benefits for not changing.

   • nash's schizo daughter :ancapchanlol: likes this.
   • Embed this notice
     Elda King (eldaking@weirder.earth)'s status on Tuesday, 16-Aug-2022 08:49:48 JST Elda King

     in reply to

     I'm sick of updating software to meet the demands of other software updates.

     I'm sick of constantly changing software to keep compatibility with other ever changing software.

     I'm sick of updating _hardware_ to keep compatibility with the same software that used to work.

     TeriRi likes this.
   • Embed this notice
     Elda King (eldaking@weirder.earth)'s status on Tuesday, 16-Aug-2022 08:49:49 JST Elda King

     Is your software complete? Stop adding features - only bugfixes, and don't break compatibility. It should keep working forever.

     Is it still incomplete? Then you must have a plan to make it feature-complete in the near future. Reduce the scope if necessary - make a sequel later! But get a finished, stable version out first.

     Either you are responsible for maintaining every version you release, or you are responsible for perfect backwards compatibility.

     Doughnut Lollipop 【記録係】:blobfoxgooglymlem: likes this.