Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ncruces
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
61 ms
·
931.
▲
by
ncruces
3y ago
There's one thing in there worth discussing IMO: the focus on zero values (incl. nil). That's the Go mistake, the one that causes most of the issues for the intended audience, the one that can't really be fixed. It's a s
932.
▲
by
ncruces
3y ago
Not being able to create new code at runtime is a pretty huge freepass for the compiler to implement stuff a certain way. You can bet the Go compiler and runtime leverage that assumption.
933.
▲
by
ncruces
3y ago
A stack is actually LIFO? Otherwise, yeah, if you remove elements from the middle, you either need a structure that allows it, or you amortize it by making such updates less frequent. Still not a queue.
934.
▲
by
ncruces
3y ago
Right. And apparently, the best way to reverse that situation is to ignore Mozilla (or any other player with single digit market share) at the W3C? And do what instead? Side with Apple/Microsoft as long it hurts Google?
935.
▲
by
ncruces
3y ago
1. Complain about market dominance. 2. Any 2% of the market doesn't matter. 3. …
936.
▲
by
ncruces
3y ago
Pending exists to prevent writer starvation: if there's always at least one reader, no one can ever write. You take pending before exclusive (which should always be possible because you have reserved by then), and you should check pend
937.
▲
by
ncruces
3y ago
Otherwise it wouldn't get used. I mean get this great auto complete; if you use it, your code might be AGPLed for all you know, and you're in violation, because you didn't even add a notice. Would you pay for that?
938.
▲
by
ncruces
3y ago
Taken to its conclusion, liability is then on everyone who decides to publish anything that ChatGPT “tells” them, because it might cross the threshold on plagiarism. Are the OpenAIs of the world ready to shield their customers from th
939.
▲
by
ncruces
3y ago
They still do, for the most part. Anything else may be allowed, if it makes sense for the task at hand, but it's an uphill fight.
940.
▲
by
ncruces
3y ago
They may cancel it. But if they do, the bank loses their mobile apps, of which they built one (so far) that ports nicely to iOS and Android. Then they make new ones. What else should they have used? At some point worrying that things will b
941.
▲
by
ncruces
3y ago
Well, the difference isn't that great. You wrote: “the memory associated with the old version could be freed once nothing would want to access it again.” So all it really takes is something wanting.
942.
▲
by
ncruces
3y ago
Still that's what they're called: https://en.wikipedia.org/wiki/Persistent_data_structure Precisely because previous versions remain valid (persist) under modification.
943.
▲
by
ncruces
3y ago
If you read the article though, many of the updated nodes (which are now garbage) don't see any updates to their “data” but to internal tree pointers. So lots of “data” is being copied, and garbage is being generated, only for the bene
944.
▲
by
ncruces
3y ago
100% agree. Remote VSCode over SSH is great. The resource consumption on the client doesn't bother me one bit. Any minimally decent laptop can put up with that load, on battery power, for hours. I would agree with “whatever it takes to
945.
▲
by
ncruces
3y ago
If you're interested, both SQLite's and my memdb VFSes implement safe locking. Depending on your familiarity with Go, mine maybe easier to follow, or not. https://github.com/ncruces/go-sqlite3/blob/f
946.
▲
by
ncruces
3y ago
How are bugs "fixed in one place" that way? You either accept updates of third party packages, with little to no vetting of your own, and get fixes "for free" or… you don't. There's no middle ground: the only w
947.
▲
by
ncruces
3y ago
Makes is-odd/is-even popular; many downloads; raises their (and his) profile.
948.
▲
by
ncruces
3y ago
From a cursory look at your source code… It looks like memory is also not contiguous in your implementation. You don't support concurrency at all (xLock/xUnlock/xCheckReservedLock are noops). I'm not sure how APSW handle
949.
▲
by
ncruces
3y ago
Recent SQLite builds include the memdb [1] VFS (and the associated sqlite3_serialize and sqlite3_deserialize APIs) by default. How does this compare? I'm also curious what use cases you had in mind. My SQLite wrapper reimplements the m
950.
▲
by
ncruces
3y ago
WAGI and WCGI are the WASM based spiritual successors. https://github.com/deislabs/wagi https://wasmer.io/posts/announcing-wcgi
951.
▲
by
ncruces
3y ago
I created https://rethinkraw.com that hijacks Adobe DNG Converter to provide a very limited Camera RAW that can even run on Linux. Why? Because why not.
952.
▲
by
ncruces
3y ago
You use unsafe for that bit. Still less gross than DoltHub's take on it.
953.
▲
by
ncruces
3y ago
WASM can bundle DWARF sections, which enable stack traces with line numbers, step debugging, profiling…
954.
▲
by
ncruces
3y ago
I used to do the same, without public IP from the VPS. I just used Cloudflare, and a Go package [1] to lock down access to anyone but Cloudflare (because at the time their tunnels required Argo). I now also use a VPS that's dirt cheap
955.
▲
by
ncruces
3y ago
Oh I wanted to implement a virtual table to do the same thing in Go (access a remote DB, with where clause push down). Will have a look at your code!
956.
▲
by
ncruces
3y ago
database/sql adds some overhead; in return, it gives you a connection pool, and tries not to have you worry about connections. A lot of the interesting features of SQLite are connection oriented, and compared to other databases, co
957.
▲
by
ncruces
3y ago
https://github.com/tetratelabs/wazero/pull/1853
958.
▲
by
ncruces
3y ago
Oh, great! I assumed you meant the officially supported System.Data.SQLite bindings. Do you have a link or is this internal?
959.
▲
by
ncruces
3y ago
Issue one: someone else was employed professionally to develope those bindings for you. :) Once that's done correctly and at a high quality, your life is easier. Developing those bindings is another story. But PInvoke is one of the bes
960.
▲
by
ncruces
3y ago
You need a virtual table (same as sqlite-vss) and a library that does cosine similarity indexing (Faiss here)… which I know little about. My plan was to evaluate Go for cosine similarity indexing, and if I found something promising, port th
More ›