00:49 <discocaml> <creepertv_1> btw how common is it for professionals here to actually just use purely an interactive sandbox to write ocaml code?

01:08 <discocaml> <yawaramin> what is 'purely an interactive sandbox'? you mean like a webapp like https://try.ocamlpro.com/ ?

12:25 <discocaml> <goose_plus_plus> Hey everyone! I am a co-organizer of the fun-ocaml (https://fun-ocaml.com/) conference and this year we are running a little bit low on a good submissions for the talks so far. Does someone has the good idea for a talk / workshop and will be able to physically present in Warsaw, Poland this September?

12:25 <discocaml> <goose_plus_plus>

12:25 <discocaml> <goose_plus_plus> Feel free to DM me, ask any question, or just drop your submission to https://cfp.fun-ocaml.com/fun-ocaml-2025/cfp

12:25 <discocaml> <goose_plus_plus>

12:25 <discocaml> <goose_plus_plus> 🫡 OCaml

14:10 <discocaml> <goreng> do I need to know about:

14:10 <discocaml> <goreng> Figma, Ubuntu, C programming language, Kubernetes, Inhertance, Nodejs, Go

14:10 <discocaml> <goreng>

14:10 <discocaml> <goreng> if I want to go there?

18:02 <discocaml> <creepertv_1> the basic ocaml sandbox you use in terminal that you get with opam

18:05 <discocaml> <yawaramin> right, so that is just the normal and recommended OCaml development workflow, eg `opam switch my-switch; eval $(opam env)`, then do development work. think of it like a Python virtual environment

18:07 <dh`> what else would you use?

18:08 <dh`> I know some beginners imagine that pros have spifflicated setups, like the difference between a workbench in your garage and a real machine shop

18:08 <dh`> but such things don't exist

18:11 <discocaml> <yawaramin> also i think there is some misunderstanding here because the wording 'ocaml sandbox you use in terminal' feels like they have some specific workflow in mind that may not be the reality

18:30 <Anarchos> yes sandbox means you launch commands unable to harm the host. Which is clearly not the case with opam switches

18:53 <discocaml> <nmote> there is a contingent from Semgrep that is considering submitting. I’m thinking about presenting about my work to upgrade to OCaml 5 which came with some GC tuning challenges. I wrote about it here https://semgrep.dev/blog/2025/upgrading-semgrep-from-ocaml-4-to-ocaml-5

18:53 <discocaml> <nmote>

18:53 <discocaml> <nmote> I have been in touch with some of the core maintainers and KC suggested trying OxCaml which includes some GC pacing improvements that the core team believes may address the issues that Semgrep encountered. I’d be able to discuss some of that follow up work as well. does that sound to you like a good fit for the conference?

18:55 <discocaml> <yawaramin> Anarchos: there is a sandbox on some platforms. see https://opam.ocaml.org/doc/Manual.html#opamfield-build-env

18:56 <discocaml> <yawaramin> or rather, https://opam.ocaml.org/doc/FAQ.html#Why-does-opam-require-bwrap

22:02 <companion_cube> Better gc pacing sounds nice

22:29 <discocaml> <shalokshalom> Can't this be inserted by default, it make it clearer for everyone, without the additional syntax load?

22:54 <discocaml> <._null._> What do you mean with "inserted by default" ?