3 ms·
Agreed. If we're getting the point where you're saying "it's like writing your configuration in [insert Domain Specific Language Here]" then I'd prefer to simpl
by jwoq9118 3y ago
Agreed. If we're getting the point where you're saying "it's like writing your configuration in [insert Domain Specific Language Here]" then I'd prefer to simply use that language. I understand the point Pkl is making in that "configuration won't work across DSLs so here's one language for all of them" but I don't know that that's enough motivation for people to adopt it.
However, I haven't built anything cool like this so what do I know. I'm just procrastinating on the my personal project and browsing hacker news.
- mekster 3y agoAt one time I just gave up on using any config formats and instead went back to the good old simple "use the programming language as the config file too" approach. It's certainly not cross language capable but when your editor knows exactly what's there and what's not with auto completion from the config file, that was a superior experience than caring about cross language issues that may not even be a problem depending on the project. If you must, you can easily make an identical copy of the config in the build process to convert it to another language.
- hot_gril 3y agoYep, I've always got a config.js. But that's a luxury compiled languages won't have.
- skinner927 3y agoShip your config as a .so/.dll ! :P
- hot_gril 3y agoThis might actually be done pretty often.