Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LumoSQL

lumosql.org

Post reply on HN
Print view View original

31–40 of 90 posts

Re: LumoSQL

#31

Post by lights0123 »

noduerme wrote: post #20
nicoburns wrote: post #16

Earlier quoted context omitted.

"client" doesn't mean web. Mobile apps, desktop apps, etc are all client-side apps that can run regular SQLite. Think of apps Spotify, WhatsApp, AirBnB, Uber, etc. Not to mention mail clients, web browsers, etc. Probably 90% of non-web clients are using SQLite.

I'm not sure about this, I may be exaggerating, but aren't all four apps you mentioned (Spotify, WhatsApp, AirBnB, Uber) built on Electron? So they'd be using SQLite in the Node portion as their storage. That's their "server side", not client side. For that portion (the locally-run mobile backend - the middleware) I guess it would make more sense... so I see what you're saying. [Edit: Of all 4 things - Maybe only Spo…

I would consider the entirety of one of those Electron apps to be a client since their main purpose is to interface with an external server—even if a small part of them internally is itself a server.

Re: LumoSQL

#32

Post by arkh »

noduerme wrote: post #7

Possibly the wrong place to ask this, but: I've played with SQLite when it was still available in-browser, and I felt that was on the brink of being a game-changer. If it was still supported in-browser and we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world. It's a lovely tech, but I never built anything serious around it. At this point, as a front-end web technology…

> what are people using SQLite for?

Managing profiles and inventory in a solo game where crafting results are random and I don't like limited inventories.

Re: LumoSQL

#33

Post by eddd-ddde »

Lio wrote: post #2

I'd say the most interesting thing on that site is the Not-Forking idea[1]. 1. https://lumosql.org/src/not-forking/doc/trunk/README.md

I got to the end of that without really understanding what this is solving, what it does, or how.

How do you handle changing upstream files locally without forking? Do you just, keep changes in a separate configuration format that is applied lazily at built time?

I've never had issues with maintaining a fork anyways.

Re: LumoSQL

#34

Post by arkh »

noduerme wrote: post #28
hruk wrote: post #22

Earlier quoted context omitted.

FWIW, I've been running a system with roughly 100K users, about 25 qps on average, with a single SQLite file for several years. No issues with data.

That's... pretty amazing. It sounds crazy to me, I'm obsessive about hourly backups, but do you use something like Litestream to keep copies?

From some months ago: https://news.ycombinator.com/item?id=43076785

> searchcode.com’s SQLite database is probably one of the largest in the world, at least for a public facing website. It’s actual size is 6.4 TB.

Re: LumoSQL

#35

Post by criddell »

jurip wrote: post #17
noduerme wrote: post #7

Possibly the wrong place to ask this, but: I've played with SQLite when it was still available in-browser, and I felt that was on the brink of being a game-changer. If it was still supported in-browser and we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world. It's a lovely tech, but I never built anything serious around it. At this point, as a front-end web technology…

One thing that's always brought up in these discussions, because it's worth bringing up, is the file format of the macOS image editor Acorn: https://flyingmeat.com/acorn/docs/technotes/ACTN002.html Personally I use it a bunch in mobile and desktop apps.

SQLite is bundled with Windows as well.

> All supported versions of Windows support SQLite, so your app does not have to package SQLite libraries. Instead, your app can use the version of SQLite that comes installed with Windows.

https://learn.microsoft.com/en-us/windows/apps/develop/data-...

Re: LumoSQL

#36

Post by dist-epoch »

noduerme wrote: post #7

Possibly the wrong place to ask this, but: I've played with SQLite when it was still available in-browser, and I felt that was on the brink of being a game-changer. If it was still supported in-browser and we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world. It's a lovely tech, but I never built anything serious around it. At this point, as a front-end web technology…

> single shot Mysql DB for testing, which is easy to spin up and easy to detach from any given back-end instance

you're doing something wrong if that is easier than using sqlite

> What's the advantage over spinning up a tiny MySQL instance in a cloud somewhere

one advantage is your thing will work without needing network access

Re: LumoSQL

#37

Post by Arwill »

aredox wrote: post #4
Lio wrote: post #2

I'd say the most interesting thing on that site is the Not-Forking idea[1]. 1. https://lumosql.org/src/not-forking/doc/trunk/README.md

I was going to say that. We really need a way to customise software at the source code level without forking.

You mean like #define + #ifdef?

Re: LumoSQL

#38

Post by 90s_dev »

Lio wrote: post #2

I'd say the most interesting thing on that site is the Not-Forking idea[1]. 1. https://lumosql.org/src/not-forking/doc/trunk/README.md

I'm confused, is this just patch and apply patch?

Re: LumoSQL

#39

Post by RUnconcerned »

noduerme wrote: post #26
chris_st wrote: post #14

Earlier quoted context omitted.

Two things: 1. There's almost certainly a port of Sqlite3 to WASM that would be more than glad to run in your browser. 2. I'd really love to know what applications fit in the "we had replication from the browser, peer-to-peer, I think we'd be living in a much more useful world" situation. We've had GunDB, IPFS, etc. that live in the browser for decades (and projects like Urbit), and the killer app just... doesn't see…

Heh. Well, #2, brilliant question. But no, I'm not thinking of anything as sexy as totally distributed filesystems. 15 years ago when I was into crypto and ran a bitcoin casino I would have had much bigger ideas for fully distributed DBs (which surely would have tanked and caused me ruin). Currently, I deal with a lot of site-specific software installations that run their own MySQL servers, some of which have unexpec…

Your best answer for "a much more useful world" is... easier development of crypto gambling? That sounds like an actively worse world to live in to me, to be honest.

Re: LumoSQL

#40

Post by maxloh »

SQLite itself is open source, but the last time I checked, its test suite remains proprietary.

How does a "fork" like this be tested if everything stays working and compatible to upstream after the change?

Post reply on HN