Interesting to see how a language that is barely out of the egg is already supplanting one that has been around for decades because of the 'bus-factor'.
If you're wondering why FP hasn't caught on in the mainstream I think this is one of the hints: if it's hard to find programmers then the language/ecosystem may have unique and desirable traits but people will still switch just to gain easy access to developers. And that switch wasn't exactly free in this case (they already did a bunch of stuff in Erlang).
That said, olegdb does not seem to be the most seriously run software project, https://olegdb.org/faq.html is not going to inspire confidence in anybody in a position to decide whether to use it or a competitor.
I helped build a new team of elixir programmers up to about 8 people in 6 months all in a third tier tech city. Most of that hiring was done before Elixir hit 1.0.
I don't buy the bus factor argument.
In fact, it's quite the contrary. If you want good programmers, "limiting" yourself to something like erlang or elixir (vs a "popular" language like go) works in your favor.
The best engineers know why to choose erlang or elixir over go and will come to you. It works as a filter and makes hiring easier.
Seeking the most popular language is the method of PHBs who want to see programmers as a commodity and want to get the cheapest labor pool from which to work with.
You increase your value by going tup the spectrum into more esoteric and better languages.
That's good and all but you miss a point: Go isn't (still) a popular language (either quoted or not and in the context of Java or C++ being popular languages with vast pools of programmers), it's just slightly more popular than Erlang.
OlegDB is a s̶i̶n̶g̶l̶e̶-̶t̶h̶r̶e̶a̶d̶e̶d̶,̶ ̶n̶o̶n̶-̶c̶o̶n̶c̶u̶r̶r̶e̶n̶t̶,̶ ̶t̶r̶a̶n̶s̶a̶c̶t̶i̶o̶n̶l̶e̶s̶s̶ NoSQL d̶a̶t̶a̶b̶a̶s̶e̶ datastore written by bitter SQL-lovers in a futile attempt to hop on the schemaless trend before everyone realizes it was a bad move. It is primarily a C library with a Go frontend for communication.
Comments
Interesting to see how a language that is barely out of the egg is already supplanting one that has been around for decades because of the 'bus-factor'.
If you're wondering why FP hasn't caught on in the mainstream I think this is one of the hints: if it's hard to find programmers then the language/ecosystem may have unique and desirable traits but people will still switch just to gain easy access to developers. And that switch wasn't exactly free in this case (they already did a bunch of stuff in Erlang).
That said, olegdb does not seem to be the most seriously run software project, https://olegdb.org/faq.html is not going to inspire confidence in anybody in a position to decide whether to use it or a competitor.
I helped build a new team of elixir programmers up to about 8 people in 6 months all in a third tier tech city. Most of that hiring was done before Elixir hit 1.0.
I don't buy the bus factor argument.
In fact, it's quite the contrary. If you want good programmers, "limiting" yourself to something like erlang or elixir (vs a "popular" language like go) works in your favor.
The best engineers know why to choose erlang or elixir over go and will come to you. It works as a filter and makes hiring easier.
Seeking the most popular language is the method of PHBs who want to see programmers as a commodity and want to get the cheapest labor pool from which to work with.
You increase your value by going tup the spectrum into more esoteric and better languages.
That's good and all but you miss a point: Go isn't (still) a popular language (either quoted or not and in the context of Java or C++ being popular languages with vast pools of programmers), it's just slightly more popular than Erlang.
It's actually pretty hard to recruit people for a mayonnaise-influenced database project.
From their github:
[1] https://github.com/infoforcefeed/OlegDB/blob/a220ae8bc178d02...