679 karma · joined April 27, 2014
Language/API | Call Overhead (no-op C) | Notes
Go (cgo) | ~40–60 ns | Stack switch + thread pinning
Java FFM | ~50 ns (downcall) | Similar to JNI, can be ~30 ns with isTrivial()
Java FFM (leaf) | ~30–40 ns | Optimized (isTrivial=true)
JNI | ~50–60 ns | Slightly slower than FFM
Rust (unsafe) | ~5–20 ns | Near-zero overhead
C# (P/Invoke) | ~20–50 ns | Depends on marshaling
Python (cffi) | 1000–10000 ns | Orders of magnitude slower |
I was responding to gp, maybe wrong part of the thread. << "Colonialism was great. It literally took continents out of pre history and brought them to the civilized world". If this is not justification for war, I don't know what is.
And how do they know in the absence of colonialism, but just trade, these countries couldn't/wouldn't become advanced? I can equally say colonialism is what has left many of these countries in poverty and border disputes.
* a primary transactional DB that I can write fast, with ACID guarantees and a read-after-write guarantee, and allows failover
* one (or more) secondaries that are optimized for analytics and search. This should also tell me how caught up the system is, with the primary.
If they all can talk the same language (SQL) and can replicate from primary with no additional tools/technology (postgres replcation for example), I will take it any day.
It is about operational simplicity and not needing intimately to know multiple technologies. Granted, even if this is "just" postgresql, it really is not and all customizations will have their own tuning and whatnot, but the context is all still postgresql.
Yes, this will not magically solve the CAP theorem, but for most cases we don't need to care too much
Children are celebrated. Rape is abhorred. I have no idea what you mean by IVF is rented wombs and profited by men. Are you confusing IVF to surrogacy?
It's got nothing to do with right or wrong.
Not agreeing with something maybe because of courage, cowardice, nonchalance or anything else.
It is a tool, like guns, bombs and medicine.
Having biological kids is a hard-wired instinct, and one of the very basic survival-of-the-genes things. I have no idea what you mean by kids deserving parents. There are no kids without parents to begin with.
So basically just hoping that billionaires spend and trickle down.
For production use, it will cost money one way or another.
What is the completely different approach you are suggesting?
Still not the same bells and whistles as Django, but really good otherwise. The database interactions are pretty good.
Anonymizing data is the biggest part of such a workflow. Most prevalent use case that requires production data is for debugging. I guess there is some value in branching non-prod databases for feature development.
Most security teams do not allow prod data in non prod environments, anonymized or not l.
Product is not the same as code. We code to build a product, sure, but I think the author means they are interested in designing the product to solve users problems (a.k.a UX)
Edit: Oh you mean costs in general, not in the context of section 147