September 26, 2021

On Wednesday, 22 September 2021 at 10:19:18 UTC, Ki Rill wrote:

>

Out of curiosity, which one do you use in your dub projects and why do you prefer one over another?

For example, I use json. Simply because when I see sdl, I think of SDL2 graphics library.

What's your reason?

I use dub.json because it is well-established and easier for people to get familiar with. I don't want to force people to learn yet another markup language to read our package definition.
Well, that's not true... I would prefer to use yet another markup language (YAML) over JSON, because it's well-established, supports comments, and is a superset of JSON.

September 26, 2021

On 9/26/21 7:58 PM, Mathias LANG wrote:

>

Well, that's not true... I would prefer to use yet another markup language (YAML) over JSON, because it's well-established, supports comments, and is a superset of JSON.

YAML stands for "YAML Ain't Markup Language". Yeah, I was surprised too.

-Steve

September 27, 2021

On Sunday, 26 September 2021 at 23:58:23 UTC, Mathias LANG wrote:

>

On Wednesday, 22 September 2021 at 10:19:18 UTC, Ki Rill wrote:

>

Out of curiosity, which one do you use in your dub projects and why do you prefer one over another?

For example, I use json. Simply because when I see sdl, I think of SDL2 graphics library.

What's your reason?

I use dub.json because it is well-established and easier for people to get familiar with. I don't want to force people to learn yet another markup language to read our package definition.
Well, that's not true... I would prefer to use yet another markup language (YAML) over JSON, because it's well-established, supports comments, and is a superset of JSON.

You prefer YAML even over JSON5?

September 27, 2021

On Wednesday, 22 September 2021 at 10:19:18 UTC, Ki Rill wrote:

>

Out of curiosity, which one do you use in your dub projects and why do you prefer one over another?

For example, I use json. Simply because when I see sdl, I think of SDL2 graphics library.

What's your reason?

  • JSON for projects
  • SDL for embedded recipes, e.g script, because it's usally small (name + 1 or two dependencies) and looks less shocking than the JSON equivvalent in a comment on top of the module.
September 27, 2021

On Monday, 27 September 2021 at 00:30:52 UTC, Steven Schveighoffer wrote:

>

On 9/26/21 7:58 PM, Mathias LANG wrote:

>

Well, that's not true... I would prefer to use yet another markup language (YAML) over JSON, because it's well-established, supports comments, and is a superset of JSON.

YAML stands for "YAML Ain't Markup Language". Yeah, I was surprised too.

-Steve

I thought it stood for "Yet Another Markup Language"?

September 27, 2021
On Monday, 27 September 2021 at 17:52:03 UTC, Meta wrote:
> I thought it stood for "Yet Another Markup Language"?

It used to but they changed it.
September 27, 2021

On Wednesday, 22 September 2021 at 10:19:18 UTC, Ki Rill wrote:

>

Out of curiosity, which one do you use in your dub projects and why do you prefer one over another?

For example, I use json. Simply because when I see sdl, I think of SDL2 graphics library.

What's your reason?

I prefer SDL per se, but dub2nix currently requires JSON so I often end up using that. On the other hand I could use SDL as source format and transpile with dub when needed.

October 01, 2021

On Wednesday, 22 September 2021 at 14:57:09 UTC, Ki Rill wrote:

>

What do you think of Rust's toml format?

It is inconsistent in its own rules and cannot be used as a drop-in replacement for JSON and other regular formats
So, meh

October 01, 2021

On Thursday, 23 September 2021 at 08:10:29 UTC, SealabJaster wrote:

>

SDL. It's cleaner and easier to read, and I have no use cases where external languages need to read a dub.json file.

second that

October 04, 2021

On Monday, 27 September 2021 at 17:52:03 UTC, Meta wrote:

>

On Monday, 27 September 2021 at 00:30:52 UTC, Steven Schveighoffer wrote:

>

On 9/26/21 7:58 PM, Mathias LANG wrote:

>

Well, that's not true... I would prefer to use yet another markup language (YAML) over JSON, because it's well-established, supports comments, and is a superset of JSON.

YAML stands for "YAML Ain't Markup Language". Yeah, I was surprised too.

-Steve

I thought it stood for "Yet Another Markup Language"?

https://en.wikipedia.org/wiki/YAML#History_and_name

Originally YAML was said to mean Yet Another Markup Language, because it was released in an era that saw a proliferation of markup languages for presentation and connectivity (HTML, XML, SGML, etc). Its initial name was intended as a tongue-in-cheek reference to the technology landscape, referencing its purpose as a markup language with the yet another construct, but it was then repurposed as YAML Ain't Markup Language, a recursive acronym, to distinguish its purpose as data-oriented, rather than document markup.