refset

16 ms·

181.
by refset 2y ago
> Trust is the decision to forgo attentiveness > If you can’t trust, you have to pay attention in order to verify – and verifying is expensive > We’d like to believe that goodness brings us together, but that’s not what the da
182.
How shall we live? (2023)(mark-burgess-oslo-mb.medium.com)
2 points by refset 2y ago|2 comments
183.
by refset 2y ago
3) Basilisp ( https://github.com/basilisp-lang/basilisp , "A Clojure-compatible(-ish) Lisp dialect targeting Python 3.8+")
184.
by refset 2y ago
> What is the relation between "start with why" and "databases are becoming a commodity"? My assumption is that the author is painting out a longer-term vision both for Confluent and its audience. It probably makes mo
185.
Clojure: Managing throughput with virtual threads(andersmurphy.com)
165 points by refset 2y ago|15 comments
186.
by refset 2y ago
H2 offers quite a comprehensive solution for dealing with this: > [H2] provides a way to enforce usage of parameters when passing user input to the database. This is done by disabling embedded literals in SQL statements. To do this, exec
187.
The Sisyphean struggle and the new era of data infrastructure(jack-vanlightly.com)
17 points by refset 2y ago|3 comments
188.
by refset 2y ago
It's great how the very first SQL query in that paper is still completely valid and runs on countless implementations: > SELECT NAME FROM EMP WHERE DEPT = 'TOY'
189.
by refset 2y ago
This is how I see things also. Clojure is extremely practical and naturally attracts people that want to ship products. The "Figma OSS Alternative" post that's also on the HN homepage right now doesn't mention Clojure an
190.
Pareto-Optimal Compression (2021)(insanity.industries)
2 points by refset 2y ago|0 comments
191.
by refset 2y ago
Codapi looks very slick! It's great that you kept everything generic enough to support many different backend use cases. Coincidentally my colleagues recently built a custom version of almost this exact same interactive UX for writing
192.
2.5x better performance: Rama vs. MongoDB and Cassandra(blog.redplanetlabs.com)
10 points by refset 2y ago|0 comments
193.
by refset 2y ago
Considering the functionality on offer the service does look particularly easy to work with, even though there's still a notion of a stateful cluster with per-node sizing & pricing. Perhaps the MemoryDB team will offer something mo
194.
by refset 2y ago
Anything that helps turn RESP into more of a commodity protocol seems like a good thing in the long run. It seems to be simple enough that workloads can legitimately migrate around and users can vote with their wallets for whoever operates
195.
by refset 2y ago
If nothing else, MemoryDB demonstrates that Valkey could be extended with much richer durability/HA guarantees.
196.
by refset 2y ago
Relevant context & reading: > for most of the history of sql we did not know how to translate it to relational algebra, and now that we do know most databases still don't do it. https://www.scattered-thoughts.net&#x2F
197.
by refset 2y ago
How about as a motivational aid and means of verifying that your code has compiled: https://squint-cljs.github.io/squint/
198.
Storage Models and Data Layout (2023) [pdf](15721.courses.cs.cmu.edu)
3 points by refset 2y ago|0 comments
199.
by refset 2y ago
For analytical queries note that you really have to learn how to express the queries efficiently with Postgres - unfortunately the optimizer is still missing lots of tricks found in more sophisticated engines [0][1][2]. JIT compilation alon
200.
Neon Serverless Postgres is generally available(neon.tech)
324 points by refset 2y ago|217 comments
201.
by refset 2y ago
Shameless plug, but XTDB v2 is being built for low-latency bitemporal queries over columnar storage and might be applicable: https://docs.xtdb.com/quickstart/query-the-past.html We've not been developing v2 with M
202.
by refset 2y ago
> Von Neumann was still deeply involved in hydrogen bomb development beyond simply developing the prerequisite plutonium implosion bomb This. https://en.wikipedia.org/wiki/John_von_Neumann > In 1955, von Neumann
203.
by refset 3y ago
Looks nice! I would suggest to pointing users to a small demo csv file and query that can be quickly loaded/pasted to see it working. Or even have a "Load example CSV and query" button.
204.
by refset 3y ago
I stumbled on this after realising that Mark Burgess, who created CFEngine, is also the author of this other recent HN post on "Using Promise Theory to solve the distributed consensus problem" [0] (from the same blog). [0] https:
205.
CFEngine's Star Trek and AI Origins (2023)(mark-burgess-oslo-mb.medium.com)
63 points by refset 3y ago|19 comments
206.
FAQs about Promise Theory(markburgess.org)
2 points by refset 3y ago|0 comments
207.
by refset 3y ago
The actual ISO standard falls well short of being useful/sufficient to anyone who isn't an incumbent player. It's effectively a moat and therefore a direct impediment to competition from teams who have novel technical ideas b
208.
by refset 3y ago
> a join is a communication between components Makes me wonder just how far people have pushed Foreign Data Wrappers in practice.
209.
by refset 3y ago
Which is fine when everything is handcrafted and human-scale, but as soon as you start going down the path of machine generated SQL (both the generation and analysis thereof) the tax is non-trivial.
210.
by refset 3y ago
Handcrafting JSON is undoubtedly always a pain, but the idea with XTQL is rather that it can be easily generated from any regular programming language. > I would actively avoid utilizing any query language where I have to count brackets

More ›