biorach

You have completely misunderstood the author's point - a misunderstanding that would have been easily avoided by reading just a little bit more of the 23 pages of detailed exposition which is very clearly not the outcome of a 'lack of effort'

> Stopped reading right after that. > Why is this so high up on HN?

Your question would have been answered if you'd just read a little more

The data race is exactly the kind of subtle bug that even very experienced programmers would make in this circumstance.

The patches that Linus posted are relatively small and self contained and from reading the thread it seems came from a series of in depth conversations with Claude and were carefully reviewed by Linus.

So what we're seeing here is a tricky concurrency bug that even an expert would make. You can't use it as an example of slop

Looks like Linus doesn't agree with you

> rust will drop the string l before q

Why?

what quirks did you bump into with sqlite3?

It's not asserting corruption. they were the voluntary caretakers of a system designed to ensure their prosperity and they provided their time and energy so that the system would continue to do so.

How much work is involved with mantaining a linker in deep maintenance mode?

The tapestry is not considered French

It's long been clear that there were fundamental implementation choices that mattered between async runtimes, but _nine_ design dimensions? Damn.

I think async is deceptive in that it seems like a self-contained and relatively straightforward aspect of a language. But there are many design choices to be made and they all have wide implications.

Plus I think the implications of many of these dimensions are not fully understood and that collectively we are still trying to understand how they are playing out in implementations. Add to this the subtle nature of some of the implications plus the combinations...

I think a good comparison is lexical vs dynamic scope in programming languages. This is a design dimension that was argued over for a decade or two in the early years of programming language design. It was only as time went by, and experience gained by working with concrete implementations that it became clear that lexical scoping should be the default choice and dynamic scoping should be restricted to various niches.

No. Because concurrency vs parallelism

> What is "await" if not a synonym for "suspend"?!?

it's a question of whether the runtime is guaranteed to suspend at an await point or if it may choose not to

> async/await is one product of a long line of thought that says "threads are too hard for programmers to get right".

what? no! concurrency vs parallelism etc etc

At last someone took the time to pore over all the tedious crap that I have been trying and failing to keep straight in my head since forever.

Please no. Africa has suffered enough.

This migration predates the arrival of Celtic speakers by many thousands of years.

I did not.

Having spent considerable amounts of time undoing the effects of overconfident junior programmers who decided to be interesting and novel on small business code bases, I guess if we're going to replace juniors with AI we may as well ask for the full experience.

It's extremely unlikely that there is anything interesting or novel in the optimisation of a small SaaS SQL

> Regardless, saying it would be too much effort for Apple

That's not what they said. Please don't misrepresent

> is laughabe

And this disparaging language about commenters is not OK. Please stop.

> not locking you out is not a big heroic move you're trying to picture here.

The person you're replying to didn't say that. Please don't misrepresent and please keep it respectful

Kind of hard to hang a globe on a wall in a satisfactory manner.

> I'd run Linux on the hardware if it wasn't a hack.

It's a hack in a good way and this is a really bad reason to not run Linux.

That's Steve Cooney. It was Dolly got the one in a lifetime opportunity.

No one worth listening to is claiming that there will be a COVID-style pandemic. The concern here is the very high mortality rate. Granted the transmission rate is low, but in countries where facilities and health-care workers are scarce this disease is still capable of being a real problem.

You might think. The UK would be the most prominent example and in fact has been a much more predictable and consistent trading and negotiating partner than the USA

oh! damn! I did not notice that. That does answer my question.

looks like the bug fixes are in individual commits here: https://github.com/sqlite/sqlite/compare/master...antithesis...

I'd be interested in seeing what the SQLite people have to say about them if/when they are submitted upstream

this is a deliberate mischaracterisation of the content of the article

I don't see a need to be dismissive. There is a lot of evidence that there is a relationship betwwen sleep and learning. The hypothesis advanced by the OP is worth evaluating on its merits rather than being dismissed as a fale equivalence.

> Using Sol or Fable for implementing is like having your Principal Staff Engineer with 30 year tenure routinely write CRUD functions for a REST API.

A Principal Staff Engineer who costs $2400 a year and never feels any work is beneath them? Hell yeah.

OK OK, usage limits

I think you're being very harsh. I read it as a side project of a scientist meant to entertain as much as educate. Holding it to the same standards as the Event Horizon project seems pedantic and excessive.