refset

42 ms·

271.
by refset 3y ago
It runs on L̶o̶t̶u̶s̶S̶c̶r̶i̶p̶t̶ JavaScript. Speaking of, Mitch Kapor's 1984 memo is turning 40 this year: > With the formal commencement of the "Notes" project upon us, it seemed appropriate to set down a few brief notio
272.
by refset 3y ago
Definitely sarcasm, it's a running gag - see the 2021 and 2022 posts also :)
273.
by refset 3y ago
> Anything loosely connected to AI + LLMs received the bulk of the attention (rightly so, as it is a new chapter in computing) Beyond LLMs and vector search, the scope for applying AI / machine learning _within_ databases is enormou
274.
by refset 3y ago
> building and managing an active-active system is extremely complicated Could Postgres yet evolve to become a Spanner-like multi-writer system?
275.
by refset 3y ago
Compression is, ultimately, AI. https://news.ycombinator.com/item?id=38399753 https://news.ycombinator.com/item?id=31923231
276.
by refset 3y ago
Take a look at the kidvis function in hn.js
277.
by refset 3y ago
I'm curious about the usage of CockroachDB at Nubank, given it's not mentioned as a "paved road" (or otherwise) in the post alongside Kafka/Datomic/Spark, but is described here: https://www.cockroach
278.
ClickHouse Is in the House(medium.com)
5 points by refset 3y ago|0 comments
279.
by refset 3y ago
Absolutely, there's no beating the RUM Conjecture.
280.
by refset 3y ago
"normalize until it hurts, denormalize until it works" is evergreen advice for scaling both reads and writes. Synchronously enforcing referential integrity and other forms of normalized constraints is what gets expensive. Pat Hell
281.
by refset 3y ago
> Datomic [...] has temporal support Note it only supports "transaction time" (or "system time" per SQL:2011) but not "valid time" (~"event time") which is needed for a bitemporal data model. [1] [
282.
by refset 3y ago
I am eager to hear how it will affect their latency numbers: > Engineering is about trade-offs, and we’ve made a significant one with WarpStream: latency. The current implementation has a P99 of ~400ms for Produce requests because we nev
283.
Playing Advent of Code with Squint (Clojure)(blog.michielborkent.nl)
1 points by refset 3y ago|0 comments
284.
by refset 3y ago
For practical implications see Truffle & Graal: > Truffle works by taking your interpreter and generating a compiler by partial evaluation. So I believe they have written a JVM bytecode interpreter and Truffle makes the JIT. > I&#
285.
The Composable Codex: A New Frontier(voltrondata.com)
2 points by refset 3y ago|0 comments
286.
HPTS Comes Full Circle [pdf](hpts.ws)
1 points by refset 3y ago|0 comments
287.
by refset 3y ago
https://yakread.com
288.
Writing a Cloudflare worker with squint and bun(blog.michielborkent.nl)
2 points by refset 3y ago|0 comments
289.
by refset 3y ago
I was fortunate enough to watch Steve present some of these demos live last night at the Future of Coding meetup in London where the whole room was buzzing - the potential here feels immense. Especially when adding a more rigorous FSM/
290.
Make real, the story so far(tldraw.substack.com)
6 points by refset 3y ago|1 comments
291.
by refset 3y ago
The Wordle clone is less exciting but you can scroll down to see the source code and JS output more easily: https://squint-cljs.github.io/squint/?src=https://gist.githu...
292.
by refset 3y ago
This is really neat. Reminiscent of how drawio.com can embed the source inside exported PNGs (see also https://github.com/Fusion/pngsource ) I would love to see this approach extended to add some animation too.
293.
by refset 3y ago
Views seem like the ideal solution in theory, but SQL implementations of views are often problematic in practice due to planning complexity & overhead. In theory they should also be a good mechanism for handling writes (see "update
294.
by refset 3y ago
"retroactive events" is probably the thing to look for, e.g. https://www.infoq.com/news/2018/02/retroactive-future-event-...
295.
by refset 3y ago
Exactly, the n+1 problem is really about query optimization, latency just makes it more pronounced.
296.
by refset 3y ago
I really like Kent Beck's recent re-framing of this overly technical topic in terms of "Eventual Business Consistency": https://tidyfirst.substack.com/p/eventual-business-consisten... > In a nutshell,
297.
by refset 3y ago
A lot of "feature store" systems seem to make the case for time travel these days, e.g. https://docs.featurebase.com/docs/concepts/time-quantums/
298.
by refset 3y ago
I believe people interested in the latter are almost always interested in the former also, at least in the context of transactional systems (and particularly anything subject to complex regulatory requirements). Analytical systems are a dif
299.
by refset 3y ago
Agreed, this is accurate. I work on XTDB and was able to speak with Richard Snodgrass (author of the paper) a couple of years ago. During our conversation we discussed how his research was primarily focused on handling valid-time, with tran
300.
by refset 3y ago
The readme mentions a dependency on Bouncy Castle - note that BC already contains several Java-based PQC signature schemes, see https://doc.primekey.com/bouncycastle/interoperability#Inter... and https://git

More ›