if you think dagger is a CI/CD enabler, it is, but its more – its module and function orchestration is a much more basic and first principle it embraces. The team has iterated from the CI/CD narrative to something much more powerful.
Happy to see this to continue to thrive. As a Swiss, same happy to see European OSS software to flurish. We use CUE for k8s and all kinds of structural configurations and data. Its catalyser to see things conceptually elevated from a pure YAML/JSON/other resulting data formats – YAML and friends will stay, but their generation and management is elevated to sane user experience and engineering driven principles. All the best for CUE and CUELabs!
Thank you for the kind words and for being a part of the CUE community!
You've perfectly captured the vision: "elevated... sane user experience and engineering driven principles" is exactly what we're building the Configuration Control Plane to provide, building on the capabilities of open source CUE.
We completely agree that "YAML and friends will stay." That's a core design principle of CUE: its ability to easily consume existing formats and export back to them, so upstream and downstream tools and workflows don't need to change.
I'm curious how flexible one is if proto3 is given as it is from a schema perspective, where a true schema/constrains language like CUE could be a vehicle to define schemas and then transform that to anything needed, like protobufs or even stubs serializing on the wire.
1. Be the change and make a framework that helps people create new and better toolchains for making iOS apps. It's more work, and requires taking the challenging path sometimes, but it's the better play for the long-term success of the community.
2. Use existing solutions that are locked in Apple's ecosystem, thereby railroading the community so that they too are locked in to Apple's ecosystem.
Why Apple's ecosystem worries me: Apple has shown time and time again that they will do the absolute minimum required to get people in the door before shutting it behind them. If someone else tills the soil and grows an orchard of delicious fruit that's reasonably priced and good for you, Apple will spend millions to fly in fruit trees with fruit that's almost as good and put a 'free with contract' sign up. What they don't mention is that they have no intention of watering the trees once the "competition" goes out of business.
I know ab like this lecture a lot. One quote I use from time to time from it:
"As with any good engineering effort when you want to improve something, the first thing you have to do is, measure it" – John Carmack
most probably yes. "Make Variation7 in Java as fast as our Revision 9 in Go, that should be possible as there is no magic happening here" is one of the exercises left...
