I sincerely hope we never add YAML to the stdlib, as that would increase the amount of YAML in the world.
> Also, it is slightly unfair to have the expectation that the community should > support a significant format through independent OSS work. Can you explain this? I don't follow. -Caleb On Fri, Sep 23, 2016 at 10:53 AM, Zachary Gershman <zgersh...@pivotal.io> wrote: > Hey All, > > I wanted to get feedback here first before I move this over to the > golang-dev mailing list (or maybe we even just start a change-set). YAML as > a spec is not the greatest and some would even describe it as "gross" but > most if not all config files are written in some form of YAML (see > kubernetes as a prime example). YAML was not included in the stdlib and > luckily for all of us the awesome go-yaml emerged as the de facto standard > for a majority of developers. > > Now, inclusion into the stdlib must pass a high bar and not everything can / > should be included but I believe that when you have over 1300 packages > depending on an outside library, you should at least have the discussion > openly about whether it should be moved into the stdlib. > > Also, it is slightly unfair to have the expectation that the community > should support a significant format through independent OSS work. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
