mirror of
https://github.com/apple/pkl.git
synced 2026-09-02 17:37:16 +02:00
Why not Dhall? #57
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/pkl#57
Reference in New Issue
Block a user
Originally created by @jjant on GitHub (Feb 11, 2024).
I did read your comparison, but I still don't understand why you guys needed to create a new language, it sounds like if ease of use within the JVM is primarily what drove this, you could've made a JVM-based toolchain for Dhall instead.
@sondr3 commented on GitHub (Feb 13, 2024):
I have used Dhall quite a bit and like the idea of it much more than the actual experience of using it. It's also very alien for developers who do not come from a functional background and requires much more investment to understand how it works or how to use it well. Dhall is also only maintained as a Haskell package, both the Rust and Java bindings are unmaintained whereas Pkl comes out the gate swinging with JVM/Go/Swift support. I adore the idea behind Dhall, but would not recommend it to anyone except FP people who use Haskell or to experiment with a total programming language.
@holzensp commented on GitHub (Feb 13, 2024):
I come from a Haskell background, so I really appreciate Dhall, but I've also learned that a lot of people don't have/want that functional perspective. Dhall wasn't where it is today when development on Pkl started and Pkl focussed on meeting its users where they are.
I'm closing this Issue, because the question doesn't allow for a definition of "done," but if you feel your question isn't yet answered to satisfaction, feel free to open a Discussion thread.