The hierarchical model is applicable to many problems and actually in part why moving off mainframes is challenging because IMS is so much more efficient than the relational model for applications like airline tickets.
There have been several efforts to leverage object stores in the way they did that I am aware of but it was a hard sell.
The hierarchical model really only works for many to one relationships, and it's integrity model differs and is not as DRY.
There are lessons to learn here but it requires some relearning.
When you have a shopping cart, having data local to the server handling the transaction is also a benefit.
Codd's relational model has advantages, but has held back some efforts because we are just use to dealing with the painful parts that we often don't consider other options.
https://github.com/deepseek-ai/smallpond/blob/ed112db42af4d0...
Understanding Smallpond and 3FS - https://news.ycombinator.com/item?id=43232410
also:
DuckDB goes distributed? DeepSeek's smallpond takes on Big Data - https://news.ycombinator.com/item?id=43206964 (no comments there, but some people have been recommending that article)
DuckDB can read SQLite so you can even imagine using them side by side in the same system, serving point reads and writes from SQLite and using DuckDB for stuff like aggregates and searches that SQLite is slower at.
I should probably give up on being a software engineer if it is.
None of the big US clouds support Infiniband broadly (Azure & Oracle have some support) so 3FS itself is not very useful to US companies who want to use public clouds.
Not even that, in the last years I haven't met a single doctor who would even care. Their value is now a necessary evil, they have the legal powers to recommend you to a hospital and give prescriptions. These legal powers will be much harder to change.
That's only true of surgeons :) What if your specialty is nonsurgical (internal medicine, pediatrics, psychiatry, etc)?
Regarding surgery, I expect it to be one of the easiest procedures to automate, actually (still quite hard, obviously). Because surgery is the only case where there's always advanced imaging available beforehand, and the environment is relatively fixed (OR).
I don't think I wrote that.
Doctors already use tech assistance. I just pointed out that while we've got efficient robots for applied math, we don't have those as agents in the physical world. People who do blue collar jobs are less replaceable. Well, believe it or not, but most doctors are actually blue collar workers.
It could be but treating patients also requires continuous diagnostics, result comprehension, and final assessment so this is certainly the part where AI could play the crucial role.
I don't think anyone thinking of the AI consequences on medicine is arguing that it will replace manual labor such as procedure executions or psychological support. This is obviously not possible so when I see people talking about the "AI in medicine" I read that as mostly complementing the existing work with new technology.
However it can't even be called hallucinating. Imagine the incident "postmortem":
But the AI was trained on White House press briefings
Made my day...Healthcare megacorps are buying up independent practices like crazy. All because doctors can't keep up with the bullshit IT required for insurance, state mandates, etc and that's in addition to the insanity of even renting commercial real estate for an office these days.
These megacorps set quotas and push doctors to nickel and dime like crazy. They sure as shit will spend the money to find robots that can give you a prostate exam with a robot dildo.
I'm going to laugh if DOGE eliminates the IRS, but also might be thankful
We build software that automates insurance billing for clinics.
And yes, the sentiment is correct that the burden of insurance encourages consolidation in healthcare. Wrapping that away (i.e. Stripe for healthcare financial infra) lowers the barrier to entrepreneurship.
Can you elaborate on that?
Once performance starts to matter (either due to scale or time requirements) abstractions always have tradeoffs you can't accept.
As long as compute is a meaningful percentage of spend, the trade off will matter.