Live data from Hacker News

Ask HN: FOSS Projects Worth Donating To?

news.ycombinator.com

11–20 of 41 posts

Re: Ask HN: FOSS Projects Worth Donating To?

#16
I think KDE is absolutely worth donating to. Sure they make a bit more than some other projects, but no where close to gnome, and not nearly enough for the good they've done to the world. They are finishing a year end fundraiser [0].

[0] https://kde.org/fundraisers/yearend2022/

Re: Ask HN: FOSS Projects Worth Donating To?

#17

Gimp has not been well supported considering it's near central position in the ecosystem. (Haters—not interested in entitled comments, thanks.)

No entitlement from my part but GIMP has been sitting on a LOT of money for a lot of years[1]. They do nothing with donations because they don't have the legal structure in place (their explanation).

What they really need is a new leader. That's the only thing that would really help the project at this point.

1. https://www.reddit.com/r/GIMP/comments/qowcy7/1300000_in_bit...

Re: Ask HN: FOSS Projects Worth Donating To?

#18
post #3

I support those, and I believe they deserve more: - SerenityOS [0], they do get some donations, but nothing close to the Linux Foundation, Wikipedia, or Mozilla. - MikroORM [1] if you'd like to support an ORM for TypeScript in the backend, again some donations, but nothing close to SerenityOS! [0]: https://github.com/SerenityOS/serenity [1]: https://github.com/mikro-orm/mikro-orm

Out of interest, What drew you to MikroORM and beyond that, to support it? Say over Prisma or TypeORM as the big alternates.

Re: Ask HN: FOSS Projects Worth Donating To?

#20
post #18
post #3

I support those, and I believe they deserve more: - SerenityOS [0], they do get some donations, but nothing close to the Linux Foundation, Wikipedia, or Mozilla. - MikroORM [1] if you'd like to support an ORM for TypeScript in the backend, again some donations, but nothing close to SerenityOS! [0]: https://github.com/SerenityOS/serenity [1]: https://github.com/mikro-orm/mikro-orm

Out of interest, What drew you to MikroORM and beyond that, to support it? Say over Prisma or TypeORM as the big alternates.

I used TypeORM and ended up regretting it because of bugs and regressions. I felt that it was unsalvageable. Prisma is from a company so I did not consider it. I found MikroORM and got very interested with.

Relations can be resolved directly from an object (ie. user.org.load()) reducing the dependencies for a service (ie. just need an OrgService, not UserService). Making mutations is a matter of simply changing a property. Normally, updates are flushed manually using em.flush(), but I have a hook to do it at the end of every requests.

Its request storage means that a lot of queries get deduplicated, which happens a lot on fat codebases:

    // in FooWarehouseProcessorExcelExportManager
    // performs a SELECT
    const org = await user.org.load()

    // logs 'ACME'
    console.log(org.displayName)
    org.displayName = 'ACME Corp Inc.'

    // later in BarStorageMiddlewareS3UploadSession
    // no SELECT! fetched from the request cache
    const org = await user.org.load()

    // logs 'ACME Corp Inc.'
    console.log(org.displayName)

    // at the end of the request, in PostgreSQL
    begin
    # other mutations
    update org where id = 'blah' set displayName = 'ACME Corp Inc.'
    commit
Finally, the maintainer is very responsive and generally great to interact with. It's probably the library that improved my work the most for the past two years.
Post reply on HN