cheers!
Edit: link directly to the diagram here -- http://www.deepstream.io/#segment-diagram
cheers!
Edit: link directly to the diagram here -- http://www.deepstream.io/#segment-diagram
Just my personal opinion.
Having said that, they of course aren't mutually exclusive, but I can see both sides of the argument.
Can you explain why opensource projects need such visual marketing? Shouldn't we choose the tools which are simply better in a technical sense, rather than the tools which have the flashiest pictures?
But I can't count the number of times I've gone to an open-source project and couldn't even figure out what it did.
And I don't consider that to be the lowest bar – any project that wants to get decent adoption should not only tell me what it does, but tell me why I should use it and not it competition. And do both of these things without me having to read the source code.
Just this week - well perhaps last - I was at the homepage of some new language – and I couldn't find any of this nor a code example. This might be a technically fantastic language but if they don't communicate that adoption is going to suffer - and when it comes to communicating pictures have a place.
Ultimately, if you combine a good technical foundation with solid communication, you have a winning combination.
Like it it not, that's how the world works. Nobody cares if you have great code and awesome tests, if you have poorly written documentation and you can't tell somebody what you do in a few sentences. Don't underestimate how difficult it is to get these last two right.
I've never heard anybody complain about the graphical communication of gnu.org, yet everybody seems to have been using the gnu C compiler for the last decades. Just an example.
Finally, have a good look at that picture: http://www.deepstream.io/#segment-diagram And be honest, what does that tell you as an engineer? And what would you take from it as a "random person"?
Is that what you call "solid communication"?