Dhall Configuration Language VS Apache Thrift

Agda doesn't need that restriction, as far as I know. And neither does Dhall. See https://dhall-lang.org/ Neither language is Turing complete. - Source: Hacker News / 3 months ago

Kubernetes config is a decent example. I had ChatGPT generate a representative silly example -- the content doesn't matter so much as the structure: https://gist.github.com/cstrahan/528b00cd5c3a22e3d8f057bb1a75ea61 Now consider 100s (if not 1000s) of such files. I haven't given Pkl an in depth look yet, but I can say that the Industry Standard™ of "simple YAML" + string substitution (with delicate, error prone... - Source: Hacker News / 3 months ago

Fail to see how this is any different than Dhall (https://dhall-lang.org/) other than it produces plists too. - Source: Hacker News / 3 months ago

Well, Dhall provides something between JSON and a Turing complete language that can make a lot of configuration much quicker to write, if you can hack the functional syntax. http://dhall-lang.org/. - Source: Hacker News / 3 months ago

What are your thoughts on: - https://dhall-lang.org/. - Source: Hacker News / 3 months ago

While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 2 months ago

Services in general communicate via Thrift (and in some cases HTTP). Source: about 1 year ago

Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: about 1 year ago

RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago