Re:YAML: probably not so great after all (2017)
by saghm on Wednesday June 20, 2018 @03:37PM
(#17358948)
The barrier here would be whether there's support in enough implementations to feel safe using it in the wild, which I'm guessing will take a while at the very least.
[ Parent
| on HN ]
Re:YAML: probably not so great after all (2017)
by tajen on Wednesday June 20, 2018 @05:32PM
(#17359993)
What’s incredible here is that we’re not at the beginning of programming, when we built temporary languages that ended up becoming forgotten. Web may be a final form of IT, Angular may be the « right », the final, the perfect way to build applications even in 50 years, just like HTML has become the final way to build websites for the last 25 years, JSON may make legacy, and my grandson might even struggle with parsers that still use JSON instead of this new tech called JSON5...
Re:YAML: probably not so great after all (2017)
by webXL on Friday June 22, 2018 @08:39AM
(#17373474)
The popularity of transpilers might help overcome that barrier. IDE's and task runners can watch for file modifications and run a simple program to convert to the old format.
But I'm curious what you mean by "in the wild"? If you're using (producing) it, something needs to consume it, and you would probably have control over both in whatever project you were using it for.