https://www.boundaryml.com logo
Is there a technical reason why the
# general
n
Is there a technical reason why the rollout for 1.0 is so staggered? I have an app in prod using baml and am wondering what the pro/con of getting it on 1.0 is
v
we hold production quality to be the highest of barriers. as of today we wouldn't recommend that companies switch their existing production apps to 1.0. we're working really hard to get there so we think in about a month we will feel confident in sharing it in a more general way where you can do a switch over to 1.0 and feel the exact same sort of quality that you feel out of baml in the 1.0 release. meanwhile we're collecting a lot of feedback and advice from people that are on the sheep council to actually teach us about any improvements that we can make that our team itself is not discovering on its own.
some of the new things we're building are: better parallelization primitives, better debugging tools, better eval solutions!
m
Would you say the same recommendation applies for greenfield projects?
v
greenfield is different 🙂 its more about migrations from stable BAML
n
Okay thanks for the response.
I was planning on writing a blogpost about how I used baml in my app, but I’ll hold off until 1.0 maybe 🤔
v
you're welcome to do both as well 🙂