NGINX config language grates on me. Whyyy did they have to come up with their own config format? It is so much nicer to configure Caddy with JSON file for example. (news.ycombinator.com)

submitted 6 days ago by crmsnbleyd@sopuli.xyz to c/programmingcirclejerk@programming.dev

6 comments fedilink hide all child comments

top 6 comments

sorted by: hot top controversial new old

[-] refalo@programming.dev 9 points 6 days ago

pretty sure it's because nginx was started about ten years before the JSON standard existed

[-] model_tar_gz@lemmy.world 2 points 6 days ago

It’s not possible to write compatibility layers in software. It’s not possible to write a data structure conversion script. It’s not possible to update and refactor code to modern standards.

It’s not possible to do anything in software.

[-] MadhuGururajan@programming.dev 5 points 6 days ago

maybe you should do it, and help everybody? It's open source afterall!

[-] model_tar_gz@lemmy.world 3 points 5 days ago

I have no need to, so I won’t. But the downvotes and your response prove my point: if there was a real need to, it probably would have already been done. In this case it’s easier and completely sufficient to just learn nginx’s config than it is to refactor it, or write the conversion/compatibility layer.

I will take my downvotes in stride, thanks for the validation.

[-] nesc@lemmy.cafe 2 points 5 days ago

Json is no better when you are doing it by hand, might be worse. They came up with their own config because there was a need.

[-] raoul@lemmy.sdf.org 7 points 6 days ago

Everybody know they should do like sendmail and compile their config file 🙄

this post was submitted on 16 Feb 2025

8 points (100.0% liked)

ProgrammingCircleJerk

61 readers

6 users here now

Programming CircleJerkCommunity at request of a user.

founded 2 weeks ago

MODERATORS

FirstMajesticComet@programming.dev

crmsnbleyd@sopuli.xyz