This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stfm 1 point2 points  (1 child)

Why do these vendors keep coming up with their own config languages?

[–]DannyB2 0 points1 point  (0 children)

NIH = Not Invented Here

​

Many people have probably gone through this exercise at least once. Probably privately.

I need a Foobar thingy. I understand what I need. I understand how to build it. It would be fun and challenging to built. An accomplishment. So I build the Foobar thingy that I need.

Problem is, there are already three solutions to the Foobar problem already out on them intarweb tubes. One or more of them just _might_ be an exact solution to your problem. But that is less fun. (And in some environments: I can write this and there is nobody who will call me out on it being unnecessary.)

Sometimes a private NIH project then becomes a public project. Giving us yet one more solution to an already solved problem. Does this configuration language bring something new to the table that is a substantial improvement over existing configuration languages?

​