phosphorco

Cool to see it going this way. Over the last two years, we've been busy reinventing contracts and financial models as the dependency graphs that they are to provide a deterministic, intermediate representation of this information in finance.

Still not sold that it'll fly in finance without that sort of observable, intermediate representation.

Well. I am very excited by this. We've built our front end in F# with Fable and our backend/engine is in Rust which compiles to WASM.

The WASM story came second, and it'd be really cool to eventually lean into something like this, particularly given the much faster compilation time.

Have followed your work on Rescript, and excited to see that this is where you've taken things.

Our whole frontend is built in elmish which is different from Native, but it can tie directly into FuncUI (Avalonia) from the elmish interface.

Mouth taping radically changed the quality of my sleep fwiw. Consistent nasal breathing is huge.

Awesome work yall. We're doing something similar for a more focused market. How long did this take to build?

We've explored this. Not everyone will have this problem, but with Blazor, you have to export almost everything about F#/.NET to WASM.

The Fable compiler team seems to have made steady progress towards a Rust compilation target which would solve this, but I'm not clear on where that works or how.

Amazing. Y'all are building a new era for notebooks - awesome launch.

Nice article. An alternate is completely unrelated to AI/GPT and rather, the basic use of a command bar/palette. Provides a lot of new ways to approach UX.

Thanks - just reading the article that you linked to above on your website. It seems like a very similar concept to state machines; can you help me wrap my head around how this might play with something like xstate or that concept?

Can you elaborate? Understand the basics but afraid I can't see around the corners of how it impacts development.

Curious how folks think this compares to Neeva? For whatever reason, didn't quite stick with that one.

Sure, but does that really matter? Second class doesn't mean they aren't investing in it... and some of the coolest use cases for F# (Fable ecosystem) falls outside of MSFT's scope entirely.

It's a small community with great libraries/support, and you can generally bet that the folks who are excited by it and want to use it are pretty strong technically.

Fable -> JS is our main use case for F#; having had to hire for this, I wouldn't say it's accurate. Most are still focused on the .NET implementation side of things. Compilation to Python is nice, I've yet to figure out why we wouldn't just use Rust rather than F# -> Rust... Rust is a great language and it feels a little silly to abstract over it.

I just have such a hard time trying to understand why DeSo hasn't caught on. Seems to solve every single one of these problems in a more elegant way. What am I missing here?

It looks similar to just writing F# via the Fable compiler, which has been iterated on for years, has an ecosystem, and now has (beta) compilation targets to Dart, Python, and Rust. Can anyone make an arg for rescript over Fable?

You'll have a much easier time doing business stuff with F# - it's OCAML inspired but has access to broader .NET ecosystem. We're using it on front end as well w/ Fable compiler. It's pretty awesome.

Would be really curious to understand the degree of vendor lock in here. Not an area I'm familiar with but seems very interesting... what alternatives exist beyond DIYing your own infrastructure?