Agreed. Though not strictly a counterpoint. I do enjoy novelty (and benefit from it). I just want the right amount of it
That is not a counterpoint. If you said your choices did not have any cost or risk compared to the “boring” choice, that would be a counterpoint.
Ah, I think this is actually a very interesting example. My understanding is that TigerBeetle started its development under the company Coil, and was eventually spun out to its own company. I think this post my almost be directly speaking to Coil's decision to fund an in-house, specialized, database project written in Zig.
More power to you guys for actually getting to work on such a fun project, but I wonder if that was a poor decision on Coil's part, as reflected by their eventual decision to jettison that part of their tech?
Re:How boring should your team be
by jorangreef on Saturday October 15, 2022 @02:58PM
(#33217563)
Joran from TigerBeetle here!
On the contrary, Coil's Interledger [1] project is designing for TigerBeetle, and TigerBeetle will be the core ledger database for Rafiki [2], the open implementation of Interledger.
A lot of this we built ourselves so we can do FoundationDB-style deterministic testing [3] of the entire system which would not be possible with off-the-shelf libraries because they are not deterministic.
Sometimes the boring options do not further the technical goals of your project. :)
[0] https://github.com/tigerbeetledb/tigerbeetle
[1] https://pmg.csail.mit.edu/vr/liskov12vr-abstract.html
[2] http://rocksdb.org/
[3] https://apple.github.io/foundationdb/testing.html