logging_strict

joined 1 year ago
[–] logging_strict@programming.dev 2 points 3 weeks ago (1 children)

what's your secret name for the project?

the ludwicks of Void Linux ftw!

i'd actually like to do something else with my lifetime besides constantly being tossed around for no apparent benefit. i'm sure there is a good excuse. There always is.

[–] logging_strict@programming.dev 1 points 2 months ago* (last edited 2 months ago)

They want to prevent coders from dictating terms. It's about perceived control/power over coders and ensuring whatever power coders wield is dispelled thru legalese spells.

Have written lots of open source as well as packages which are not published. The amount of contributions measured in issues/PRs/funding has been the same. Absolutely none.

Lost any incentive to care about debating licenses' purity.

[–] logging_strict@programming.dev 1 points 3 months ago (1 children)

Very wise idea. And if you want to up your game, can validate the yaml against a schema.

Check out strictyaml

The author is ahead of his time. Uses validated yaml to build stories and weave those into web sites.

Unfortunately the author also does the same with strictyaml tests. Can get frustrating cause the tests are too simple.

[–] logging_strict@programming.dev 1 points 3 months ago* (last edited 3 months ago)

Curious to hear your reasoning as to why yaml is less desirable? Would think the opposite.

Surprised me with your strong opinion.

Maybe if you would allow, and have a few shot glasses handy, could take a stab at changing your mind.

But first list all your reservations concerning yaml

Relevent packages I wrote that rely on yaml

  • pytest-logging-strict

  • sphinx-external-toc-strict