Ask HN: FOSS Projects Worth Donating To?
11–20 of 41 posts
Re: Ask HN: FOSS Projects Worth Donating To?
#12Re: Ask HN: FOSS Projects Worth Donating To?
#13It’s a FOSS maps app for iOS/Android that uses OpenStreetMaps data. Offline support & minimal battery usage make it ideal for walks/hikes/travelling.
Re: Ask HN: FOSS Projects Worth Donating To?
#14Re: Ask HN: FOSS Projects Worth Donating To?
#15Re: Ask HN: FOSS Projects Worth Donating To?
#16Re: Ask HN: FOSS Projects Worth Donating To?
#17Gimp has not been well supported considering it's near central position in the ecosystem. (Haters—not interested in entitled comments, thanks.)
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?
#18I 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
Re: Ask HN: FOSS Projects Worth Donating To?
#19Re: Ask HN: FOSS Projects Worth Donating To?
#20I 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.
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.