Support 1.0.0-rc1

[paiden]

Unfortunately I decided to completely drop TOML as a configuration format for my software projects after reading the v1.0.0rc spec.

Therefore I will not implement any further changes for the 'Nett' library and do not intend to release any new version.

I do not want to go into too much details but the primary reason for this decision are:

• I do not see the 'OM' part of TOML anymore
• My needs for a configuration file format seem to diverge largely from the needs of other TOML users and the TOML maintainers.

I'm very sad to 'forsake' people that invested into 'Nett' but I will not use my free time to support a file format that does not help me to solve my problems.

[prime167]

So sad hear that. It is a so good project. Thank you for all your hard work.

Do you have any plan to transfer the project to other mantainers?

[Splamy]

Sad to hear the stop of this libray, but I'll repect the decision.

Just out of curiosity, two questions:

after reading the v1.0.0rc spec. I do not see the 'OM' part of TOML anymore

What made you feel that way? I diffed the last 0.5.0 and 1.0.0 version and didn't find anything extraordinary except from a few deleted examples

My needs for a configuration file format seem to diverge largely from the needs of other TOML users and the TOML maintainers.

What is your config language to go now? Right now I don't see a lot of contenders except for yaml, json(c), and xml which all have their own share of problems

[paiden]

@prime167 There are no concrete plans, but I'd have no issues with transferring the project ownership to someone willing to continue it.

@Splamy Ad1.) v1.0.0 was only the final nail into the coffin that lead to this outcome. I started thinking about dropping Toml before this already. My problem is the TOML guys are discussing if leading 0 in a float exponent is allowed or not while IMO much more important stuff gets tagged with post 1.0 or is declared as 'would be a breaking change' so we don't do it. I'm sure they have their reasons to do so but I feel more and more like this

I need a super simple config format that can store key value pairs, maybe group them a little to split a config into logical sections and handling arrays and lists of things is already a bonus . That is my configuration file use case. No idea what super complex configs other people have, but I have never needed to store heterogenous arrays. Most of the time I configure timeout/retry values etc. BTW the only thing TOML does not have a datatype for (Nett had experimental support for a duration type) 😄

Ad2.) Probably JSON like many other software projects for now.

Additionally I'm experimenting with some config format ideas I came up with, while working on the TOML parser. I really want a library that has this Git like config system that can merge multiple configuration files again. It goes into the direction of simplified Eno. But not sure if that will result in something useful.

[Splamy]

Thanks a lot for your answers. My biggest gripe is probably that it's more noisy than it should be, but I don't want to switch config languages again, so I'll probably stick with it and hope someone can keep to maintain the lib just a bit.

Most of the time I configure timeout/retry values etc. BTW the only thing TOML does not have a datatype for

haha, yeah, I'm in the same boat, In the end i just wrote a custom human string->timespan parser, since it need it that often.

[donvreug]

Very sorry to read this. You've done an amazing job with this project. Thanks. Since I mainly use Nett.Coma I was wondering what you plans are for that. Migration to a new language or drop it? My config use case seems to align largely with yours and Coma satisfied most of my needs.

[perlun]

@paiden Sorry to hear you are planning to move away from maintaining this (especially given that there are no other better .NET parsers available for .toml at the moment), but at the same time - thanks for being very honest and upright about it. As a previous maintainer of rack-test and CefSharp, I know that maintaing open source projects clearly is not "free". From my experience, it works best when the software being maintained is something that is critical to your employer (so you can spend part of your regular work hours maintaining it), but more often than not, this is not the case.

As for me personally, I only started using Nett today, looking for a config library for the static site gen I ended up constructing for one of my web sites. I really dislike YAML strongly, and JSON is not much better. TOML is pretty much the only simple option that's left, or so I thought. :see_no_evil:

Let's hope someone with a big heart for TOML and Nett steps up and is willing to pick up the gauntlet. In the meantime, thanks for your efforts thus far. :+1:

[AndrewSav]

I just stumbled across this after opening three new issues. @paiden do you think you can put a notice at the top of the front page readme.md (and optionally archive the repo). Thank you for all your work on this.