Hacker Newsnew | past | comments | ask | show | jobs | submit | andrewstuart's commentslogin

It’s not necessary to separate queue db from application db.

got it. is it necessary, then, to couple queue db with app db? if answer is no then we can’t make a necessity argument here, unfortunately.

Frequently you have to couple the transactional state of the queue db and the app db, colocating them is the simplest way to achieve that without resorting to distributed transactions or patterns that involve orchestrated compensation actions.

that’s setting yourself up for trouble, imo. intermediate states solve this problem, and economically. for mature production system see temporal[0]. their magic sauce is good intermediate states.

[0]: https://temporal.io/


This feels like an ad because you explained absolutely nothing.

It's one thing to explain to people what a screw driver is and you just happen to sell screw drivers to people who might need them.

It's a wholly different thing to sell the screw driver first and then let people figure out why they need it.


i’m not associated with temporal, nor does the link above have any referrer nonsense in there. i don’t profit from referring to it here. in fact it may well be a household name in the hn community. that out of the way, it’s not wrong to point to a proper resource that can explain and demonstrate my argument better than a couple of words could. temporal is open source[0] so maybe a github link would have been more palatable?

[0]: https://github.com/temporalio/temporal


solid_queue by default prefers you use a different db than app db, and will generate that out of the box (also by default with sqlite3, which, separate discussion) but makes it possible, and fairly smooth, to configure to use the same db.

Personally, I prefer the same db unless I were at a traffic scale where splitting them is necessary for load.

One advantage of same db is you can use db transaction control over enqueing jobs and app logic too, when they are dependent. But that's not the main advantage to me, I don't actually need that. I just prefer the simplicity, and as someone else said above, prefer not having to reconcile app db state with queue state if they are separate and only ONE goes down. Fewer moving parts are better in the apps I work on which are relatively small-scale, often "enterprise", etc.


The adafruit fruit jam is an extremely cool little computer.

I bought one of the first manufactured.


There’s game developers who develop games.

And there’s game developers who develop game engines thinking they are developing games.


Nothing wrong with that - Engine developers often have "defining" titles - aka tech demos they work on to push the field

Townscaper is a nice one like this; it has very few features or gameplay, just a sandbox tech demo for a very cool take on model synthesis / "wave function collapse" on an irregular grid. The game is mostly carried by the novelty of this mechanic (and also the pleasant art.)

Futzing around with analog televisions.

If you give, and expect something in return, then you are not giving, that is a transaction.

I’ve written plenty of open source and I’m glad it’s going into the great training models that help everyone out.

I love AI and pay for four services and will never program without AI again.

It pleases me that my projects might be helping out.


What are their drivers like?

Fully open source? Unlikely methinks.


Last I read was Mesa support for those Adreno GPUs is still work-in-process. Link: https://lore.kernel.org/dri-devel/20250930-kaana-gpu-support...

Would be nice if Qualcomm worked with at least 1 OEM to get at least one Linux distro supported at launch.

Hypothetically if they did I'd pre order one.


AI finds nearly 2/3rds of breast cancers!

I see you're not in the marketing department! We can do better by only considering "missed" as what wouldn't also be missed by a human: AI finds 71% of breast cancer*!

*Compared to a human.


Depending how the costs of AI detection vs doctor, that genuinely might be enough to shift the math and be a net positive. If it is cheap enough to test 10x the current tested population, which would have lower, but non-zero rates of breast cancer, then[0] AI would result in more cancer detected and therefore more aggregate lives saved.

[0]presumptively


Given that every positive case needs to be verified by a doctor anyway because the patient has breast cancer, and every negative case has to be checked because it does a worse job than traditional methods... It only costs more.

Depends on the false positive rate. Hypothetically one can 'just' tune the model so false positives are low. This will increase false negatives but those are 'free' as they don't require follow ups. So long as the decrease in cost per real positive[0] goes down there's a benefit to be had.

[0] accounting for false positives, screening costs for true negatives, etc. etc.


> This will increase false negatives but those are 'free' as they don't require follow ups.

Increase in false negative rate significantly reduces survival rate and increases cost of treatment. We have huge multiplication factor here so decreasing false negative rate is the net positive option at relatively low rates.


> Depending how the costs of AI detection vs doctor, that genuinely might be enough to shift the math and be a net positive.

Based on my very superficial medical understanding, screening is already the cheap part. But every false-positive would lead to a doctor follow up at best and a biopsy at worst. Not to mention the significant psychological effects this has on a patient.

So I would counter that the potential increase of false-positive MRI scans could be enough to tip off the scale to make screening less useful


Ballmer would turn in his grave except he’s alive and well.

You can stop worshipping growth any time you like.

Capitalism and democratic systems don't work without growth. Just look at the consequences of the economy stagnating in western Europe and what that is causing on a societal and political level.

No growth means no jobs for new grads, no growth means workers have no negotiating power with their employers, no growth means young people remain poor and cannot afford families. No growth means young people with bad economic prospects seek political alternatives, and newsflash, they far-right with their magic-grift-politics are far more appealing than the far-left with their estorectic utopian far-fetched plans.

Also no growth means a worsening wealth inequality over time.


The alternative is stagnation. And if you think that zero sum economy would favor you over corporations and billionaires, I have a bridge to sell you.

And if you think humanity is making it past ~2100, I have some carbon credits to sell you: https://www.sciencedirect.com/science/article/pii/S001632871...

Growth über Alles / the race to consume everything we can in our spherical petri dish with the same level of awareness as mindless bacteria, will be the end of human civilisation, regardless of anyone's economic beliefs.


Turns out love your neighbor was incredibly valuable advice.

Climate change is simply not an extinction threat. Despite all the fearmongering, the worst case scenarios top out at "WW2" levels of devastation and loss of life.

The only credible extinction threat to humankind so far is an ASI oopise, and that's because it's an intelligent threat.


Assuming positive real return on their investments, a zero growth (or low growth) economy means the rich will own an ever growing proportion of wealth - its simple arithmetic.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: