Marcel van Lohuizen

Make GitHub Actions, and the rest of your CI/CD and workflow stack, more powerful with type safety, validation, reusability, and policy enforcement using CUE! How? Easy - check out this hands-on demo from our community member @rawkode: youtube.com/watch?v=MFtQAh…

📣 Meet the "Shift-Left" Editor. Join us next Tuesday, Nov 18, at 16:00 UTC for a hands-on demo of the new CUE LSP. Get real-time validation, error-checking and language features as you type - right inside your editor. Learn more + call in details: github.com/cue-lang/cue/d…

This paper from Tsinghua University and Shanghai Jiao Tong University received perfect scores (6, 6, 6, 6) at NeurIPS 2025! It aims to answer a key question: Does reinforcement learning really make large language models better reasoners? The authors study Reinforcement Learning with Verifiable Rewards (RLVR) and find that while it improves accuracy for small k, it doesn’t create new reasoning patterns—meaning the base model still determines the upper limit of reasoning ability. Across six RLVR variants, performance gains plateau, suggesting that current RL setups mainly refine reasoning rather than reinvent it. Interestingly, it’s distillation, not RL, that shows genuine signs of emergent reasoning. This research points to the next frontier for truly self-improving large language models. Does Reinforcement Learning Really Incentivize Reasoning Capacity in LLMs Beyond the Base Model? Paper: arxiv.org/abs/2504.13837 Page: limit-of-RLVR.github.io Our report: mp.weixin.qq.com/s/2-GDxs8j1QYh… 📬 #PapersAccepted by Jiqizhixin

📣 We have just released #cuelang v0.15.0 - introducing the CUE LSP, two new language experiments, and much, much more 🎉 github.com/cue-lang/cue/r…

Looking forward to this!

Today, I'm proud to officially announce CUE Labs! I co-founded CUE Labs with @mpvl_ to build a Configuration Control Plane, solving config chaos with CUE. Our work also provides the stewardship for the @cue_lang open source project. Read more: cue.dev/blog/announcin…

I'm proud to officially announce CUE Labs! I co-founded CUE Labs with @_myitcv to build a Configuration Control Plane, solving config chaos with CUE. Our work also provides the stewardship for the @cue_lang open source project. Read our launch post: cue.dev/blog/announcin…

🔈#KubeCon London opens in 2 days! Will you be there? Let us know: forms.gle/L62aiNHc1R8tjg… - we’ll save you a cool CUE cap. We’re bringing lots of updates & demos: If you use GitHub Actions, Azure, GitLab, Argo, or K8s, our CUE content can simplify your workflow. Can’t wait! 🚀

It was a privilege to have known and worked with Luiz. He was not only an amazing engineer, but equally warm and kind-hearted. Sad. 😢 wired.com/story/google-m…

#CueLang makes it very easy and elegant to add #monitoring to your system (in this example exposing @PrometheusIO scrape endpoints) across environments and deployments, with templating, validation, defaults and even enforcement. Good talk by @cue_lang creator @mpvl_ @cfgmgmtcamp

Great read!

In SF? Come hear @mpvl_ talk about @cue_lang in “Taming Configuration Complexity made Fun in CUE” in the Languages of Infra: Beyond YAML track at @qconsf. qconsf.com/presentation/o… #cuelang #QConSF

@davidreuss You answered your own question. :) We almost always just generate the “golden” files.

@mpvl_ oh, just found UpdateScripts in the testscript.Params 👌🏻 — will definitely give testscript a spin 🤩

A must read indeed: testscript is awesome! We use it everywhere in cue to quickly roll out comprehensive test sets that are also reusable for implementations in other languages as a bonus.

Welcome! Hugely excited to work with you all!

@bgrant0607 @_myitcv @cedricgc CUE aims to solve this conundrum by supporting default values. They are effectively a fine-grained one-level override. We found that this finds the right balance between reducing complexity while allowing flexibility.

@bgrant0607 @_myitcv @cedricgc Configuration is inherently cross-cutting, which makes using inheritance and overrides (which are basically a type of inheritance) particularly tricky.

I see the API driven view that kpt.dev supports, but we cannot disregard the actual languages used. SW dev constantly shifts left to the realm of PL, so innovating on language design impacts what we can do on a higher level (like infra config)