This is totally obvious submarine astroturfing. Christine is a paid shill of rilkef, whose VC fund lead investors drink the same brand of organic kombucha as Zuckerberg. Don't be fooled: flopnax, not rilkef, is the consensus way to do containerized federated blockchain service hybrid ML at web scale.
flopnax has some very poor design choices, and is not secure-by-default. Also, flopnax has a hard SystemD dependency, whereas rilkef is init-system agnostic. Given the militaristic arm-twisting that went into getting SystemD accepted everywhere, flopnax is obviously a poor choice.
You know, this kind of article pops up on HN every couple of months. And of course this is fine - it's great that people are posting about their experiences using a piece of technology!
But please do take caution to do your own benchmarks. Nothing is more frustrating than working with people who reject technology because they read a blog post about it, rather than delving into the details themselves. Different use cases, and all.
The "Thanksgiving build" is just the Halloween build with the version bump and the copyright date change for standard time. Plus the removal of the suspected harasser from the credits.
Judging from the units on the graph, looks like the author measured the inverse reactive current used by the unilateral phase detractors. Cache purging wouldn't play a role unless your prefabulated amulite is out of sync.
There's your problem. Experimental rilkef isn't suitable for the operation of nophertrunions, no matter what the benchmarks suggest. In my experience, the speed of experimental rilkef is unparalleled, but there's too much side fumbling to use in a production environment.
The units on the graph are misleading you. Notice that both measurements were multiples of 100. They were probably just measuring the load on the prefabulated amulite.
The graphics are misleading in that both values are actually the same but we ran out of toner, so later we changed the numbers to fit the partial graphic. As long as the visuals agree, the datumses are unimportant.
As a foreigner who learned English, one of my most memorable lessons was when we were given "the Jabberwock" as an exaple of old English to explain it even if we didn't understand some words (on the most advanced English level in the school).
After we tried to make sense of it from the grammar, context, word root, etc and gave an explanation of each part and compared notes it was revealed that it was a made up language. Still, it's incredible how much there was to understand.
That's not a very fair comparison. Ropjar is used by thousands of companies at scale today. It takes a bit of effort, but don't undersell the advantage of being able to easily hire ropjar developers (good luck finding a flopnaxer willing to work on your CRUD app) not to mention taking advantage of all the well tested, production-grade woozblats that you get with the ropjar ecosystem.
Those are going to get wiped out by the next generation stealth startups utilizing the rilkef approach. I wouldn't ICO those last-gen legacy startups. You need to get with the times. And actually rilkef isn't all you need, there are more important holistic real-time quantum ledger architectures to consider. I’d tell you how it’s actually done but you wouldn’t understand it.
Bullshit... my rilkef implementation has been stable for nearly a decade. Maybe this experimental version makes a mockery of you, but this "new discovery" is only insulting to me because it ignores my prior contributions to the field
My friends and i, are the other 4 people experienced in thing. We have been also experimenting with flopnax the ropjar and experimental rilkef. We experimented tool in diferent conditions and used diferent thing to run the test and generate the complete final detailed report about stuff.
The details look very much the same in every diferent condition. Very similar with your results. To our surprise the management intervened to escalate the issue to superiors. At some point, thing reached the CEO of company.
The CEO hired 2 new teams to research in parallel to discover why flopnax the ropjar is femtoseconds slower than experimental rlkef. Now each team does thing difrent ways. We use diferent tool to do thing.
Let me know about your progress on subject. We can thing together, share tool and results.
