yarosh

5 ms·

1.
by yarosh 2y ago
1. I do believe that Rust type system needs to be reworked, so all the drama around it is needlessly bloated. We have RustBelt, RustHornBelt and myriads ways of converting HIR/THIR/MIR to CoQ, for better or worse, but no MLIR supp
2.
by yarosh 4y ago
1. SBT was never fun 2. I don't believe that scala-native was a good idea in the first place, because of all the java-interop boilerplate already present. C/JVM interop design conflicts are very hard to abstract properly. It would
3.
by yarosh 4y ago
1. If there are no good arguments in the collective - there's no retrospective and it's primarily a management and psychological issue. No one is able to fully self-reflect and it breaks the existing delegation / escalation c
4.
by yarosh 4y ago
> "i want to write infrastructure as code from day 1" is not only stupid , its a waste of resources I tend to disagree. Depends on the scale... and after you've scaled and grown DevSecOps absence becomes a source of detrac
5.
by yarosh 4y ago
tldr; it wraps Terraform providers poorly and can fail building proper infra diffs from time to time... https://github.com/pulumi/pulumi-aws-native is nowhere near GA state, just scroll through the issues... and the re
6.
by yarosh 4y ago
1. both pulumi and crossplane just wraps the Terraform providers as is on many occasions, and quite poorly. There are a lot of pending issues with the dependency graphs, state refresh and proper state diffs. Although a lot of the most troub
7.
by yarosh 4y ago
As an Ops, who literally replaced Patroni with a Terraform CTS module, in about a week... can say that it would be nearly impossible to do in a non Pizza size team due to communication and confirmation biases, alongside the respective anti-
8.
by yarosh 4y ago
A bit of ranting... As for me 1, HashiCorp is forcing enterprise upsales whenever possible, even if it'll hurt Adoption Rates and overall Development Experience 2. Existing TF design issues are ignored, which is causing people some sta
9.
by yarosh 4y ago
Yes, of course. I don't really like neither crossplane nor pulumi due to the lack of providers. And to my personal opinion they would've better spent some resources to contribute to the target providers instead of embedding or dir
10.
by yarosh 4y ago
Yes, a lot can be automated with CUE and it would work similarly to tfcdk, which could potentially solve a lot of multistage deployment issues by manually managing multiple dependent terraform states. Having unified terraform state on the o
11.
by yarosh 4y ago
Really tired of overcoming the existing design limitations of terraform. I think that this is a global issue that had been neglected for far too long, and too many people had been struggling with this due to pointless hashicorp excuses, of
12.
`Depends_on` in Terraform Providers(discuss.hashicorp.com)
2 points by yarosh 4y ago|5 comments