heyoooo its not battle tested language right? there could memory leak or core level breaks etc... so, why should i switch?

you've got some great points! we're still working on performance measurements to share where the language is it. we do monitor for memory leaks pretty aggressively, and as of now, we don't have them when we run our stack! in terms of core-level breaks: the core semantics "should" work! e.g. @aaronv (BAML) last night ported

sasso

from rust -> BAML. we've written entire backend apps purely in baml. etc but its still early and we're still building it, so things can fail. as for why you should switch, i wouldn't advocate for that today for you! different teams have different levels of risk tolerance and BAML is still an early technology. for you and your team, it may make more sense to wait until other teams have first tested BAML for X months / years. But there are some very interesting things about BAML: in particular the tracing and observability capabilities. instead of annotating functions explicitly, we auto instrument all baml code. so you get traces and profiles automatically.