Odd, I got right in. I think it was maybe 5 seconds, didn’t have to do anything. Curious if that’s a bug or if there’s some automated trust or something. Cool concept though, echoes of GPG web of trust days.
Kratos is awesome, especially alongside Hydra, OathKeeper, and Keto. Super powerful combo, if not a little intimidating at first. There’s a LOT of configuration involved, but that’s to be expected if you want to host your own Auth0 replacement.
Their dynamic forms stuff is really cool too, always liked how they chose to go about that. Only complaint I really ever had is that while their docs were overall serviceable, I remember some areas were pretty lacking and I had to dig really far to find answers to some fairly common issues.
Helix has been my daily driver for a few years now, and it’s extremely familiar if you’re coming from the LazyVim setup for NeoVim. I make a few mistakes here and there if I have to use tools with just basic VI binds, but you learn to juggle them both.
The config is very well documented and it would be simple to rebind things too.
Well for one my editor doesn’t support plugins (yet)!. But I have found that learning my editor well enough removed my need for the pesky edits / boilerplate writing offerings of AI. Other than that, I don’t trust it to write anything big, and don’t need it to write anything small.
I’ve tried it a few times and it’s decent for writing unit tests but otherwise often made a mess of things. I understand there’s an art to it but I’m just not interested in putting too much effort into it. I’m always going to go through whatever it generates with a fine toothed comb, so I don’t see it saving me much time anyhow.
I have watched some very senior engineers really dive in with it though, and seemingly with a lot of success.
i think you’re right, though i think i was thinking about about this at a higher level. i more meant that the languages in the JVM ecosystem I have experience with (java, kotlin, and scala) have all given me similar unpleasant experiences building them. same tools too, though you probably wouldn’t use sbt for non-scala projects even though you could.
the main pain points for me are dependencies, packaging, and configuration. best i can tell, those pains are shared between anything that targets JVM, especially those that want to have good interop.
love the syntax, and excited to mess with it, but man i’m sad to see it’s on the JVM. if i had to guess, a lot of langs like this are on JVM because that’s a lot simpler than writing a whole backend with anywhere near the same performance or reliability, and i totally get that.
that being said, bearing in mind that i’m not a Java/JVM developer and only rarely have to use it, for the few nontrivial projects i have shipped with it the build system was by far the most challenging and frustrating. it’s so complex and has such a large surface area.
no hate at all, and the trade offs are completely reasonable, but i am hoping during my career we’ll start seeing either a massive simplification of JVM builds or a lot of innovation that would make native compilers easier to build.
(as a side note, it is nice to have langs like this for when JVM is the only option)