Why we develop EloqDB mainly in C++
eloqdata.com
Why we develop EloqDB mainly in C++
1–10 of 94 posts
Re: Why we develop EloqDB mainly in C++
#2[dead]
Re: Why we develop EloqDB mainly in C++
#3> In particular, the most harsh arguments against using C++, i.e. memory unsafeness, can be significantly mitigated when developing with a certain modern subset of the C++ language.
So the quest for the one true “modern subset” of C++ continues.
How do developers continue believing in this after a decade of the standards committee proving over and over again that they’re not interested in this and won’t contribute toward it?
Re: Why we develop EloqDB mainly in C++
#4These articles can always be surmised down to "because we wanted to". Rarely is there some real reason.
Re: Why we develop EloqDB mainly in C++
#5These articles can always be surmised down to "because we wanted to". Rarely is there some real reason.
As Richard Restak postulates in his book “The Naked Brain”[0]: the limbic system provides a gut feeling (usually from comfort) and we rationalise our way backwards from that without being able to really pinpoint “why”; usually the “why” is secondary and only added as justification for the feeling post-decision.
[0]: https://www.amazon.com/Naked-Brain-Emerging-Neurosociety-Cha...
Re: Why we develop EloqDB mainly in C++
#6> In particular, the most harsh arguments against using C++, i.e. memory unsafeness, can be significantly mitigated when developing with a certain modern subset of the C++ language. So the quest for the one true “modern subset” of C++ continues. How do developers continue believing in this after a decade of the standards committee proving over and over again that they’re not interested in this and won’t contribute to…
Mitigate having bad legs by walking on your hands
Re: Why we develop EloqDB mainly in C++
#7I don't know if the stuff about the JVM is even true. I grant that Redpanda is written in C++, but it isn't clear that its performance advantages over Kafka are due to that rather than to the fact that Kafka was implemented in a performance-oblivious way by people who did not know anything about software efficiency. This doesn't reflect on the JVM. You can write a high performing system in Java and the modern JDK is a state-of-the-art toolchain that provides features that many C++ projects struggle with.
Re: Why we develop EloqDB mainly in C++
#8One thing I like about Rust is that it prevents you from doing stupid things on the compiler level. I write a little bit of C/C++ and Rust. If you don't do C++ on a daily basis, you will silently introduce problems in the code that are very hard to spot. You just need to have a very good mental model of how to write good C++. It requires constant exercising.
For Rust, you just have to fight the compiler. This is especially useful when you have people on your team with some experience who also want to contribute, but you don't want to constantly point them in the right direction.
I actually have no idea how big teams work on large C++ codebases. Usually, you need to have a good idea of how the whole thing works. You can change one part of the code, and it will introduce bugs in the whole project because of how the memory is handled. Isolated changes are hard. And historically, a lot of C++ codebases lack good test coverage.
Re: Why we develop EloqDB mainly in C++
#9These articles can always be surmised down to "because we wanted to". Rarely is there some real reason.
The "I drive an H-pattern manual transmission" of programming language discussions.