51–60 of 64 posts
Hi! I'm the author of the Java KDL library, https://github.com/hkolbeck/kdl4j . I'm currently overwhelmed by other things and unable to do the work to get it up to the 1.0.0 spec. I'm looking for folks willing to help me. DM me on Twitter at the same name if you're interested.
thank you for this very cool effort; what if the folks able to help are those who shun twitter? (of the strong programmers i know, each refuses to have anything to do with twitter.)
Earlier quoted context omitted.
Criticism given by those that do not align with the core goals/userbase of a project is not constructive. Giving criticism on something you don't intend to/wouldn't use is just complaining.
I disagree, there's always the chance that there is a nugget of useful knowledge in there. I'd rather go through 100s of criticisms than miss it.
Message boards are message boards. You can't take them seriously, including this one.
Quick said-contras:
Q: "Another markup/config language?" A: Yes. We actually do get (slowly) better at solving already-solved problems. Evolution of spec does happen and is important. Steady refinement and reflection on past work just is progress.
Q: "OK, but is it worth the mental clutter and cognitive load of an additional standard/dependency/format?" A: That's for the market and community to decide together. Example: Time was, Markdown was a bizarre hobby format and most work happened in XML or LaTeX or Wiki (or, gasp, Perldoc). But Markdown proved better, more sensible; so Markdown won.
Q: "Why not YAML?" A: Am I the only old here who remembers the era of YAML security bugs? Like, it was like the Sendmail Bug Era, but worse, because it was in everything. YAML, like Perl, is easy to read, but hard to reason about; and that makes it a hazard. These days, we have YAML libs and practices we regard as known-good, but I still trust it about as much as I trust \.doc(x?) or \.pdf, or some weird execv() involving ImageMagick. It's unclean. Sorry, not sorry.
KDL is solid and I'm a fan.
I have pretty much no interest in another markup language (or whatever we're calling these sorts of things today[1]) but I really want the slashdash comment style in every language I use now, that's an incredible idea. [1] apparently I didn't edit this in fast enough but wow I have even less interest in semantic arguments about what is and isn't a markup language.
Yeah tbh I don't know why syntax commenting isn't more common; when I wrote a language with s-exprs one of the earliest things I did was add a comment form to comment out an expression. And _especially_ in s-exprs it's almost trivial to add! Really don't understand why we don't see it more.
I have no idea what people are complaining about in this thread. I find projects like this genius. I love making programming languages and I hate hate hate writing parsers, yet I enjoy experimenting with different syntax. Stuff like this is very convenient because you can just import your code as document, use path language to extract data, and schema language to apply basic checks. Not only is this thing standardize…
I have no idea what people are complaining about in this thread. I find projects like this genius. I love making programming languages and I hate hate hate writing parsers, yet I enjoy experimenting with different syntax. Stuff like this is very convenient because you can just import your code as document, use path language to extract data, and schema language to apply basic checks. Not only is this thing standardize…
To me it looks amazing, and I was literally about to adopt it in one of my open source Rust-based projects, but then I realized that the Rust version (and only the Rust version) is restrictively licensed under the Parity Public License [1]. I want my open source project to be able to be used in commercial applications, and don't want any of my dependencies' licenses to restrict that. [1]: https://github.com/kdl-org/k…
Earlier quoted context omitted.
When my projects are posted publicly, I like attaboys, but I need constructive criticism. Asking pointed questions and questioning purported inconsistencies is not complaining.
Criticism given by those that do not align with the core goals/userbase of a project is not constructive. Giving criticism on something you don't intend to/wouldn't use is just complaining.
Earlier quoted context omitted.
I disagree, there's always the chance that there is a nugget of useful knowledge in there. I'd rather go through 100s of criticisms than miss it.
For some perspective, this HN thread is much, much better than the Reddit post from yesterday. Sure, there were a couple of good points hidden in the rubble, but lordy it was bad. Cruel, even. The main author has taken a break (and fair enough) so you probably won't see them around today.
The only syntactic difference I see with GraphQL is the lack of parenthesis around arguments and the existence of anonymous arguments.
I have pretty much no interest in another markup language (or whatever we're calling these sorts of things today[1]) but I really want the slashdash comment style in every language I use now, that's an incredible idea. [1] apparently I didn't edit this in fast enough but wow I have even less interest in semantic arguments about what is and isn't a markup language.