d1l

100% bro

If you can't tell then I'm not sure what more needs to be said. I took a look through the commit history and it was glaringly obvious to me.

To trust something like data-storage to vibe-coded nonsense is incredibly irresponsible. To promote it is even moreso. I'm just surprised you can't tell, too.

It's a nonstop slop funnel as far as I can tell. Only ashamed I've been here for more than 5 minutes.

Are you using ai for the comment replies too?!

Vibe coded trash.

that credulous hn readers will upvote this is alarming.

Beethovens 17th piano sonata is based on the tempest. I recommend Richter if you’re curious!

https://youtu.be/qeL3tAb7yV4

I’d imagine there’s an extremely long tail of features and quirks that will take time to iron out even after SQL compatibility is achieved. Looks like it’s still missing some important features like savepoints (!!!), windows and attach database.

I’d be more excited and imagine it would be more marketable if it focused instead on being simply an embedded sql db that allowed multiple writers (for example), or some other use case where SQLite falls short. DuckDB is an example- SQLite but for olap.

Fuck, my wife got a notice that she would have to increase her iCloud storage so last week began the process of ordering a backup of all her pictures so I could get them off iCloud and organized on some drives at home. We got 12 zips of the pictures along with csv's and some metadata, and I literally just finished iterating on the script to sort them into year-based folders and convert all the HEIC shit into JPG. It's running literally right now.

Guess I should've searched harder!

I still use it (shout out taviso iykyk).

https://github.com/zy/zy-fvwm/blob/master/fvwmrc/taviso.fvwm...

Someone made a full cde style desktop with fvwm: https://github.com/NsCDE/NsCDE

It’s too bad tech seems so much to take away this kind of configurability in the name of “we know better”. There’s so much to be said for software that can last so long, as opposed to the constant treadmill of forced updates.

Fuck gnome eternally for destroying gtk and fuck Wayland.

This is disingenuous and probably was written this way for HN cred and clicks. Sqlite's test suite simulates just about every kind of failure you can imagine - this document is worth reading if you have any doubts: https://www.sqlite.org/atomiccommit.html

That's even crazier - so you're using asyncio because you have a ton of slow network-bound stuff - but for your database access you are running every sqlite connection in it's own thread and just managing those threads via the asyncio event loop?

This is strange on so many levels.

SQLite does not even do network I/O.

How does sharing a connection (and transaction scope) in an asyncio environment even work? Won’t you still need a connection per asyncio context?

Does sqlite_open really take long compared to the inevitable contention for the write lock you’ll see when you have many concurrent contexts?

Does sqlite_open even register in comparison with the overhead of the python interpreter?

What is an asyncio SQLite connection anyways? Isn’t it just a regular one that gets hucked into a separate thread?

Similar thing in 2019-20 in Colorado. There is a ton of FOIA stuff released if you search.

https://en.wikipedia.org/wiki/2019–20_Colorado_drone_sightin...

24 zx6r to replace my clapped r6, which had nearly 50k miles. Love it even though the rev limit kicks in at 14k (as opposed to the 17k on the r6). Now that it’s cold I’ll be sending it off for a flash to get that raised to 14.5… Love the ninja, though. That bike only wants to go fast.

Site calculates a 40deg forward lean but the best is full tuck behind the windscreen with the throttle pinned.

If you maintain a library you’ll hear about this kind of shit early and often.

The last thing anyone needs is “visual” “designers” shitting up our useful applications.

Stick to your todo list apps and stay in your lane.

This is just yet another attempt to piggyback off the HN crowd's enthusiasm for Sqlite in order to advertise fly.io.

Man does not live by bread alone. If you want to make technology and the standard of living a god, that might be rational, just as communism may be an earlier rational attempt in the same vein. But I believe these ideas are naive. The central idea seems to be “eliminate enough of man’s animal suffering and cater to his animal wants and you’ll have paradise” but I think these schemes undervalue the human need for freedom, love, self discovery, and meaning.

A statistical review would show that you are almost certainly quite incorrect.

Also, the "they" you refer to is "us".

In that time there is relatively little figurative art of humans. Rarely seen in cave painting, etc. The nearest would be the Venus figurines but they don't typically show facial features or internal anatomical details. It's a major major find bro.

All greenlet does is allow the Python frames to managed separately from the C call stack - it is very similar to what Pypy is also doing. I don't think your characterization is at all accurate.

Our well-thumbed and torn cars book was a favorite of my brother's and mine. Half the pickle truck is missing and my kids speculate what other vehicles might have been on the missing page. There's no lesson here other than, I think, that when someone creates something good, honest, and with love, then that thing is worthwhile and praiseworthy. The love shows in every detail of his books.

This is the so self-serving and self-congratulatory! He had the nerve to cry on her doorstep, which says he didn't want to apologize, but to be forgiven and to make a show of it.

Amending past wrongs is about showing up without any regard for your own feeling and the intention to do whatever is in your power to set the wrong aright. You admit the wrong and then you listen.

I get it that to the author this is some cute meta-story about "we were both wrong!" But truly acknowledging one's fault is antithetical to this kind of fawning over oneself and infantile moralizing.

You've conveniently described python behavior but lots of C code relies on the gil implicitly and will need to add locking to be correct in a nogil world.

I'm not saying for sure this is bad! I do think it is dishonest though about the potential impact. Lots of critical libraries are written in C.

This is a fantasy, a romance. It very little resembles the reality I've seen.

Many addicts I've known and seen come from stable environments and it isbecause of their incessant drug use that they end up poor, homeless and degraded.

Of course some addicts definitely start in "crushing poverty" but many do not. It affects people from every background, every social strata.

If your hypothesis were correct than the housing and support programs would work. They don't.

Yeah I've seen the destruction that comes from removing legal/social consequences for drug abuse. Neglected and abandoned children is by far the most tragic. The community of non-addicts bears the responsibility for cleaning up the destruction, the addicts themselves cannot. That's the nature of addiction. To be clear I'm talking about the hard drugs; opiates, cocaine, meth.

I believe addiction is a disease, but treatment is elusive. Some have no desire to stop. There are also frequently other mental or emotional problems. Just feeding addiction's most obvious symptom (by continual drug use) does nothing - see this article.

I doubt whether there will ever be a neat and tidy "solution". Eventually the healthy part of society will have enough and some action will be taken, like prohibition or war on drugs, etc. Then it will wax the other way again.

Maybe taking telemetry data and rider feedback to calculate ideal suspension settings, engine mappings, etc. In other words, putting the best possible car on the particular track.

They didn't have an army of UX fuccbois back then. Now they do and this is an endless stream of makework to justify themselves.

The fact that he doesn't understand why his wal file is growing without bounds should be a warning to take his suggestions with a grain of salt. This is yet another lazy benchmark with lazy suggestions by someone who is uselessly retreading the path laid down in the SQLite documentation.

This is so lazy as to be irritating to me. Magic pragmas with no explanation, no use of the important ones if you're going for max performance (synchronous and journal mode), no discussion of statement compilation and the benefits of plan caching, no discussion of indexes or transactions... Just garbage to make a lazy point that maybe SQLite is fast.