Skip to content

An Alternative Approach to Integrating F# and Unity #92

@bryanedds

Description

@bryanedds

Hi!

I read your post on r/fsharp and I wanted to log my feedback here for greater visibility.

You asserted that the method you experimented with yielded negative results. As a functional game developer (author of Nu Game Engine), I think the problem might be that you used the most straight-forward approach. I think the more appropriate approach would be to implement an Elmish-style MVU programming model where the Unity engine is treated as the DOM and is connected to the model via something like FSharp.Data.Adaptive.

You'd have to implement a Unity-specific DOM-differ and a declarative Entity interface a la Elm's view types, but I think such things could be prototyped in short order. Additionally, you could have a principled back-door for imperative operations on Unity via something like Nu's Commands.

I would love to advise on this approach if you're interested in pursuing it. I think it would be a great opportunity to apply the lessons you've learned and leverage my hard-earned experience in building the functional F# game engine, Nu. Our discord is here in case you'd like to get in touch - https://discord.gg/6HgMeRM

Cheers and thanks for the hard work you've done so far!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions