3 ms·
I will never get the rationale behind creating a new proprietary language solely to protect people from 'full blown' programming. Or, in some cases, being able
by contravariant 7y ago
I will never get the rationale behind creating a new proprietary language solely to protect people from 'full blown' programming. Or, in some cases, being able to read/manipulate config files with standard tools.
- verdverm 7y agoDark Lang is doing the same, we almost did, but are using Cuelang for our take on this now
- contravariant 7y agoCuelang looks interesting, but also seems like a language with a very specific use case. I don't understand Dark Lang's reasoning for using a custom language when they could have made an IDE.
- verdverm 7y agoWhat very specific use case? I have found Cue to be versatile and usable anywhere yaml / json / config is used or needs to be validated. I'm mainly focused on code generation with Cue as the input. https://github.com/hofstadter-io/hof https://github.com/hofstadter-io/hof
- contravariant 7y agoI'd consider a situation where you've got a human readable (?) data format that needs to be validated a rather specific niche for a domain specific language. All I'm aware of in that area is XSD and DTD for XML (and maybe some recent efforts to make schemas for JSON but those aren't too flexible). I'm happy someone is trying to fill that niche though, I'll remember cue for when I run into such a scenario.