+972 52-548-6969
RavenDB has the best users
time to read 1 min | 51 words
Talk about making my job easy. Thank you Barry, and I am sorry it took me 17 minutes to get the fix out.
FUTURE POSTS
- Memory optimizations to reduce CPU costs - 10 hours from now
- AI's hidden state in the execution stack - 3 days from now
- The role of junior developers in the world of LLMs - 5 days from now
There are posts all the way to Aug 20, 2025
RECENT SERIES
-
RavenDB 7.1
(7):
11 Jul 2025 - The Gen AI release -
Production postmorterm
(2):
11 Jun 2025 - The rookie server's untimely promotion -
Webinar
(7):
05 Jun 2025 - Think inside the database -
Recording
(16):
29 May 2025 - RavenDB's Upcoming Optimizations Deep Dive -
RavenDB News
(2):
02 May 2025 - May 2025
RECENT COMMENTS
-
By Oren Eini on Replacing developers with GPUs
-
By Bertrand Le Roy on Replacing developers with GPUs
-
By Rail on Goodbye Hibernating Rhinos, Hello RavenDB LTD
-
By Oren Eini on Semantic image search in RavenDB
-
By peter on Semantic image search in RavenDB
Comments
You've got the best business model in the world, don't pay developers just have the community fix your product! You should start offering reduced licenses for people who find/fix bugs. That should iron out a few more kinks in the product.
@jon I hope you were being sarcastic. Most of these types of bugs are edge cases that don't show up outside of real world use. Oren has a great track record of fixing these bugs quickly. Even quicker if the customer provides a failing test. If I'm not mistaken a bug report is NOT a bug fix.
@Killman of course!
There should actually be a strong incentive for users to do this. If they provide you a failing test for an issue, chances are you will incorporate that into your automated runs. Thus, the likelihood that the issue that broke them specifically will re-emerge has dropped drastically.
I wouldn't presume to expect any form of free or reduced price for a non-OSS license just for submitting a bug report, even one that came in the form of a failing test. But, that would be a nice incentive to go so far as to fork the github project, fix the bug, then issue a pull request.
A free or reduced license for use in closed source project(s) would be a nice bonus for getting a pull request accepted into the core. But if you think about it, having ones name in the list of contributors of such a large project would be a real bonus for the old resume and the value of that might far exceed the cost of a free production license.
Comment preview