lean4 unifies types and values, so that types feels so natural. you stop thinking types at all as you think about types in rust or csharp. and haskell does not have that feeling too.
Yes. It might sound counter-intuitive or even ironical but the next logical step is to make the type system more, not less expressive and to add completely dependent types. Every language already has them to the extent of Array<T, N> (or T[] & { length: N }, or a recursively defined Tuple<T, N>), but having true flow- and value-dependent types would allow for more concise and expressive code.
every app is big hierarchical state machine. from app using mechanical enginering devices to cenralized perpertual trading orderbook to networked game world state management middleware.
But if Kore starts where Kustomize ends (selectors like, inheritance like, binding like things) and covers 100% of Kustomize. But builds on top (i see CEL usage). I can be intresting to use this instead of Kustomize.
> However, the two tools are not mutually exclusive. In some cases it can make sense to use Kustomize in combination with Koreo!
Would be awesome Koreo make Kustomize no need.
I feel insane getting into project where Helm, Kustomize and Koreo used at same time(they always do this).
So if Koreo and Helm only, would be nice gradual step. One bad yaml with other bad yaml.
Honestly, Koreo can cover most of the use cases of the other tools just fine. We leverage Koreo to manage deployments of the Koreo controllers along with their service accounts and RBAC—it works quite well. We also use it with Helm in order to install, for example, ACK controllers which have existing Helm Charts.
Our design is very, very deeply inspired by Kustomize. If Kustomize or kpt are sufficient, I would strongly encourage using one of them. We developed Koreo because we have cases where we need to sequence resource creation (for instance to map values from one resource to another) and wanted to programmatically set values.
i was in previous iterations of products ms doing eee/enshittification, so very caucious to monitor them and pull earlier than they.
i do not see in text of announcment any reason to use copilot specifically anymore.
so left copilot 2 weeks ago.
tried local qwen-coder. started small but ended max fits 12 gb nvidia laptop gpu. it made my laptop sound like jet, so not this year or even next year, until bubble burst. no local for now. need pull earlier than other they from clouds so at some points.
but local was fine quality autocompletion even on 12gb.
currently ended up on vs code+continue+mistral. feels fine. i like line by line autocomplete and pressing tab several times for each line. better quality and more control.
also i use only clouds which also provide models to run locally. so i can pull when time will come.
do not have time to try other models and extensions. so many.
zig may be like that too, but not tried.
reply