Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
Scrawl-canvas
Responsive, interactive and more accessible HTML5 canvas elements. Scrawl-canvas is a JavaScript library designed to make using the HTML5 canvas element easier, and more fun
-
-
Well there's a few services to help[0], and I see many Github projects with a link in the readme asking for donations and such.
But then the project is basically `donationware` and the income is unreliable.
I think we need more /reliable/ streams of income instead of digital panhandling.
https://github.com/willmcgugan/rich
> Rich is a Python library for rich text and beautiful formatting in the terminal.
> The Rich API makes it easy to add color and style to terminal output. Rich can also render pretty tables, progress bars, markdown, syntax highlighted source code, tracebacks, and more — out of the box.
Seems Rich is not just displaying pretty text, it seems to almost be a full blown UI library that can render components and more.
Since the API surface is that big, it's possible for bugs to slip through, and those have to be fixed by someone.
Then once companies and other people start depending on this library, they start being dependent on fixes to also be made to it as new platforms appear, new terminals get written and so on.
Either the companies/people can start contributing their fixes directly upstream, or the can fund one person who can do it for them, and for other users of the library.
Although most of us know what happens in situations like this: no one except the original author actually fixes stuff, until the author looses interests and moves on.
I've just dedicated the best part of 2.5 years to working on my open source project[1] almost full-time. During that time I've managed to rewrite the entire library from scratch, discover a new purpose for its existence and (very selfishly) have a lot of fun with the library, pushing its boundaries and re-evaluating its 'API' as I discovered/explored the world of generative art.
Sadly my personal funds have run out and I've not been successful finding sponsors etc. But the work has helped me land a new/exciting full-time job so I've wasted nothing through my endeavour. I wish Will McGugan all the best at the start of his adventure, and hope he has as much fun as I've had over the next year or two!
I gotta admit, I like the open core model. When it's done right, it seems like a reasonable way to monetize while still getting development done and encouraging a community and ecosystem. I've been looking at how Ghost[0] set things up[1] and it seems to be working very well. The company is non-profit and has certain restrictions in place to ensure that they don't become evil. Still, it won't work for everything and it can't work for smaller libraries.
I like the idea (and even asked for something similar at some previous jobs), but it can be easily gamed. I could for instance just send the funds to myself or to a friend.
I am currently favoring the https://gitcoin.co model: individuals make donations to the projects they want to support, companies contribute to the fund only to match the individual donations, and quadratic voting rules determine how much each project ends up receiving in the end. Quadratic voting works to ensure that no single whales benefit from the matching funds and that the distribution is more even.
I've also have been contributing some of the BAT I receive from Brave to creators that are registered and I'd like to support (hi @geerlingguy!). It seems that if more people did that we could put some of the money from the ad industry into good use.