The only thing any test proves is, which compiler produces more efficient assembly code.
Specifically, it's LLVM vs all the other C++ compilers.
C++ compilers like GCC generate more optimized asm for some things. Other things LLVM does better than GCC, but so does C++ compiled with LLVM.
C++ is a fantastic language, but it's become far too complicated with people using like 10% of the features, but everyone uses a slightly different 10%, and no one can really know more than 20%... cpp2 is trying to address this, but in the meantime you have new entrants looking to take over the real-time space (rust, zig, etc.)
The honest no BS answer is: it depends... more specifically, you need to do your own benchmarks specifically on the bottlenecks you expect your project to face.
We then build on top of that a whole new way to navigate historical posts, so that you can actually look and interact with a stock chart by pulling up news & discussion from any time in the history of the stock.
Here's a scenario:
You're interested in stock AAA, but you notice on the chart that it fell 30% 2 years ago, and hasn't begun recovering yet. But today you read that they are embarking on a big turn around plan. So you click on the time period on the chart 2 years ago to find out what the cause of the drop was.
You find out it was a critical supplier that went bankrupt, and they have only now found a replacement.
Now you can decide whether to buy their stock or not, and you are informed about the context.
Stocktwits is to twitter what fnchart is to Reddit.
Stock twits is basically: Stock Chart + Twitter.
fnchart is basically: Stock Chart + Reddit.
We then build on top of that a whole new way to navigate historical posts, so that you can actually look and interact with a stock chart by pulling up news & discussion from any time in the history of the stock.
Here's a scenario:
You're interested in stock AAA, but you notice on the chart that it fell 30% 2 years ago, and hasn't begun recovering yet. But today you read that they are embarking on a big turn around plan. So you click on the time period on the chart 2 years ago to find out what the cause of the drop was. You find out it was a critical supplier that went bankrupt, and they have only now found a replacement.
Now you can decide whether to buy their stock or not, and you are informed about the context.
1. Tried and true: advertising, selling live data feeds, and premium chart features.
2. Innovative, but still familiar: We are continually looking to build on our Sentiment Discovery Dashboard, and give users premium analytics access into what the trends are in the market. The goal is to add LLM that would train on our massive amounts of user discussion, that would then feed into even better Sentiment Discovery, thereby creating a self-feeding improvement cycle.
We are a team of 5 (4 coders and 1 graphics designer).
This has been an absolute labour of love for all of us on the project.
We have always believed that most people completely miss the context behind movement of stock prices. We wanted to build this platform to not only put stock price movement in context, but also to provide far richer depth of information.
We also hope that financial journalists take advantage of our platform to discover story ideas, and to be able to use our direct messaging to reach out to experts directly, to get further details on a possible lead.
In the future we will also allow users to see levels of engagement on various posts, so a journalist can get a sense of how popular a topic is before committing to write a full story on it.
For me it was usenet and IRC... I still remember discovering usenet and the incredible resources on comp.lang.c++.moderated... those were the good ol' days where reputation was based on people recognizing you and not based on some score / number of followers...
Specifically, it's LLVM vs all the other C++ compilers.
C++ compilers like GCC generate more optimized asm for some things. Other things LLVM does better than GCC, but so does C++ compiled with LLVM.
C++ is a fantastic language, but it's become far too complicated with people using like 10% of the features, but everyone uses a slightly different 10%, and no one can really know more than 20%... cpp2 is trying to address this, but in the meantime you have new entrants looking to take over the real-time space (rust, zig, etc.)
The honest no BS answer is: it depends... more specifically, you need to do your own benchmarks specifically on the bottlenecks you expect your project to face.