logging_strict

joined 1 year ago
[–] logging_strict@programming.dev 3 points 6 days ago* (last edited 6 days ago)

Why the commercial license for pngquant? Maybe rewriting pngcrush IP and slapping a commercial license on it is copyright infringement. This is my impression of Rust. Take others IP, rewrite it in Rust, poof copyright magically transferred. The C99 version how much of that is from prior art?

Lets just ignore prior art and associated license terms

pngquant commercial license

written by Kornel Lesiński

ImageOptim Ltd. registered in England and Wales under company number 10288649 whose registered office is at International House, 142 Cromwell Road, London, England, SW7 4EF

First commit Sep 17th, 2009

pngcrush license

Copyright (C) 1998-2002, 2006-2016 Glenn Randers-Pehrson

glennrp at users.sf.net

Portions copyright (C) 2005 Greg Roelofs

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

pydantic underneath (pydantic-base) is written in Rust. fastapi is fast cuz of pydantic. fastapi is extremely popular. Cuz it's right there in the word, fast. No matter how crap the usability is, the word fast will always win.

If fastapi is fast then whatever is not fastapi is slow. And there is no convincing anyone otherwise so lets not even try.

Therefore lets do fast. Cuz we already agreed slow would be bad.

normal dataclasses is not fast and therefore it's bad. If it had a better marketing team this would be a different conversation.

SQLModel combines pydantic and SQLAlchemy.

At first i feel in love with the SQLModel docs. Then realized the eye wateringly beautiful docs are missing vital details, such as how to:

  1. create a Base without also creating a Model table

  2. overload __tablename__ algo from the awful default cls.__name__.lower()

  3. support multiple databases each containing the same named table

#2 is particularly nasty. SQLModel.__new__ implementation consists of multiple metaclasses. So subclasses always inherit that worthless __tablename__ implementation. And SQLAlchemy applies three decorators, so figuring out the right witchcraft to create the Descriptor is near impossible. pydantic doesn't support overriding __tablename__

Then i came along

After days of, lets be honest, hair loss and bouts of heavy drinking, posted the answer here.

Required familiarity with pydantic, sqlalchemy, and SQLModel.

[–] logging_strict@programming.dev 2 points 1 month 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 3 months ago* (last edited 3 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