In my experience, it's not really the base language that makes Whimsy difficult to understand. It's more about the scaffolding that is needed to turn the code into an application.
The code consists of a lot of different parts that need to be plugged together to make the app work. If something does not work, it's may not be at all obvious why, as there may be no error message. On Thu, 19 Mar 2020 at 08:05, Harbs <harbs.li...@gmail.com> wrote: > > Not sure why this discussion continued on board@. > > Like Justin and Danny, I have zero experience with Ruby. If it were written > in a language I would have been more comfortable in, I would have likely made > PRs in the past. I even briefly considered learning more about Ruby to make a > PR (but got quickly side-tracked). > > Not sure that this justifies porting the code, but I figured I’d add my > experience. > > Thanks, > Harbs > > > On Mar 19, 2020, at 2:07 AM, Sam Ruby <ru...@intertwingly.net> wrote: > > > > TL;DR: would porting whimsy to Node.js attract developers? > > > > To explore this question, I've created a spike: > > > > https://github.com/rubys/whimsy-board-agenda-nodejs > > > > Thoughts? > > > > - Sam Ruby > > >
