Hacker News Reader

Comment by unshavedyak | Hacker News Reader

If you get value out of Blender they could use your support: https://fund.blender.org/

Even just a coffee a month will help immensely. Please consider supporting :)

Always support open source when you can, even if you use proprietary software instead of Blender.

Supporting open source creates competition for your paid alternative, so they're forced to give you a better product or a better deal.

Can you imagine if everyone paying monthly subscription for any type of software took 10% of their budget and donated to the alternatives? I'd bet that any FOSS project could reach parity to their proprietary counterpart in three years.

The whole point is subscription software is you don’t have 10% left of your budget to finance anything else.

You can also/alternatively subscribe to Blender Studio:

https://studio.blender.org/

You get access to training, assets, source and production logs like the recent Dog Walk update while also supporting Blender:

https://studio.blender.org/projects/dogwalk/production-logs/

I could tip them even without using it, the value of such a successful creative project is a pleasure in itself.

This is the only project I support year in year out. What they did is amazing. Simply amazing.

Especially software like Blender.

It's easily one of the most well-made FOSS projects out there!

I maintain a Blender fork at my company and Blender quite literally is my paycheck, but I disagree vehemently that it is a well-made FOSS project lol.

So .. can you give reasons?

Seconded. I don't know much about the code, but on a usability level it sometimes feels even more polished and pleasing to handle than many big proprietary offerings. I would go so far as to say it's one of the best executed desktop programs of the current era.

Just to share one datapoint - I have not looked at the internals myself, but having talked to a couple of devs who has spent a great deal of time working with Blender at a code level, one takeaway seemed to be that there was a lot of code duplication caused by each dev doing their own thing and not having an overall architect to rationalize some parts of the code.

A particular example that was mentioned was the importers that were each done standalone rather than built on a common framework. This was a couple of years ago and of course things may have changed since then.

Just to note that the developers were still extremely positive about working with and in the code, but it does seem plausible that there would be issues like this in a codebase where many devs focus on a small piece of the overall puzzle.

Reply on news.ycombinator.com