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!
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.
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...
I followed the 2 day summit and I am impressed both about what happened with angular.dart and flutter for the web and mobile. Its obivious what google thinks how web and mobile apps can be done in the future and even doing it already internaly. tracking Dart from time to time I thought, that it "somewhat died" and never got traction... it still seems so, but seeing what google is doing is encouraging. Its clear that if google thinks that webapps have to be done the angular.dart way, they will do it for the next 8 years or so; if the rest of us thinks that JS thing is the thing, googles way might be the same.
For flutter it might be different if Android gets expanded with flutter.
I used GWT a few years ago and still have a GWT app in production (which I hope never has to change until decommission).
Its not a coincidence that the mentioned GWT app should get replaced with a complete rewrite and we are at the point where we lay out the options to do that. GWT is marked clearly as "dead" for new developments within the clients infrastructure. Angular an reactjs are the recommended frameworks, even node.js and plain JS is a "allowed" option.
I do not have preferences for any plain JS or not typesafe languages personaly; but with the history of GWT, Dart or Angular.dart is a hard sell in this situation. Taking the Dart way is similar as we took GWT a few years ago, but even more a lockin into something the rest of us isn't doing (that does not mean the best is what others do, but you know what I mean eh?) because Dart is a new language and framework, from where one couldn't get away easy. The same applies to GWT; that code gets not compiled without gwt tools after you opted into GWT.
I hope Dart is making its way to (perhaps) replace Java in Android or make it into an alternative to the default.
For Dart as a Language for the web I don't know yet what happens(who knows). 2x productivity improvements for an App as mentioned in the summit talks is really great, and I think google doesn't advertise that if not true. Even more impressive is, that google choosed Dart to rebuild one of the most business critical WebApps; a thing you won't do if the technology is not rock solid.
So next for us is to recommend and prove whats the way to go for this old GWT app (that runs every day flawlessly) but is a hurt to maintain...