Speaking of Hasura, are there any Haskellers proficient at Rust seeing obvious issues with moving graphql to a Rust idiom?
@Ambrose brought up in the Hasura thread that there is no guarantee of Graphql-Engine being successfully ported to Rust.
Via sloccount, the codebase is 200k lines Haskell and the estimated cost at 60k developer salaries is 8 million. Considering that a lot of Haskell development work is done with senior engineers, and even cutting costs based on Indian Haskellers, you’re still looking at about 16 million USD worth of developer hours.
Consider that Rust is between 150% to 300% the code length of Haskell, and that’s easily 48 million USD worth for the rewrite, and possibly 187.5 developer years.
Of course, this doesn’t say that rewriting GraphQL is impossible, and perhaps people more familiar with both Rust and Haskell might be able to clarify Hasura’s apparent project.
If this is in fact an expensively intractable problem, I’m guessing Hasura execs might end up kicking themselves for not trying, instead, a port to Linear Haskell, or paying Well-Typed or Tweag to help mature Haskell-Rust FFI and clone Sigma / SC’s Mu, except using Rust instead of C++.
If using the most current languages is a key Hasura value, wrapping Rust with Haskell would likely have given them the most avant-garde backend possible.