refset

9 ms·

91.
by refset 2y ago
> there are a host of specialized optimization strategies only possible when compilation can happen during runtime That's a big part of why Jank is interesting to me, because it can properly embrace the idea of runtime JIT using L
92.
by refset 2y ago
I'm just an enthusiastic bystander so I don't know the answer. Hopefully Jeaye can chime in.
93.
by refset 2y ago
Clojure is language that was designed to be 'hosted' on many different underlying language runtimes, not just the JVM/Java. If Jank can implement clojure.core correctly (pass the tests!) and handle .cljc files then it counts
94.
by refset 2y ago
Jank should be able to produce significantly smaller binaries than Graal native images at the very least, but the potential for performance gains looks to be rather large, e.g. per "jank has been consistently beating Clojure in benchma
95.
by refset 2y ago
Fast compilation is undoubtedly more essential in the Lisp paradigm of REPL-driven, interactive programming with S-expressions than in other languages. A pre-requisite perhaps for the world to 'Stop Writing Dead Programs' [0] [0]
96.
by refset 2y ago
Jank uses Boehm GC (written in C, also used by the likes of Inkscape, Guile and Mono) - it is discussed a little in the previous blog posts, e.g. https://jank-lang.org/blog/2023-07-08-object-model/
97.
Jank development update – Moving to LLVM IR(jank-lang.org)
190 points by refset 2y ago|49 comments
98.
by refset 2y ago
Not a capital-T Teletype but it seems like it was widely used as a teleprinter and had similar mechanical constraints/requirements. The post does touch on this language ambiguity: > Teletypes (technically "teleprinters" -
99.
by refset 2y ago
Not sure whether this changes anything about your critique, but note that the IBM 2741 terminal embedded a Selectric typewriter: > Selectric-based mechanisms were also widely used as terminals for computers, replacing both Teletypes and
100.
by refset 2y ago
DataScript already supports processing n-ary relations, it's just not how the data is naturally stored when you use `d/transact!`. Even though it's all in-memory anyway (ignoring the recent addition of durable storage on th
101.
by refset 2y ago
This is a consequence of the Datomic information model which is focused on handling a single universe of triples (to facilitate natural schema growth) instead of independent n-ary relations. However unlike when building serious business app
102.
by refset 2y ago
You'd probably be interested by this approach of chaining the DataScript rules to derive the next frame if you haven't seen it already: https://frankiesardo.github.io/minikusari/#!/minikusari.tuto...
103.
by refset 2y ago
I could also believe many groups arrived at the term independently, deriving naturally from conversation along the lines of: "These are the data on which decisions are based" See also Rich Hickey's definition of "basis&q
104.
by refset 2y ago
> "data base" was a term in use predating that 1963 publication I agree, and actually reading through some of it only reinforces the feeling. I suppose the real answer could well still be CLASSIFIED, if it was even recorded i
105.
by refset 2y ago
> The origins of the term “data base” and subsequently “database” go back a long way. The first sighting of the term was its use in 1963 by the System Development Corporation who sponsored a symposium with the title “Development and Man
106.
by refset 2y ago
Good overview, although a rather important aspect of the 'resilience' that's not really covered here is the way that SQL technologies navigate and sustain performance trends. Relational databases are sticky in large part beca
107.
by refset 2y ago
As it should be :)
108.
by refset 2y ago
Not sure whether this is a Lotus Notes reference also, but it should be! (that's where the idea for CouchDB came from)
109.
by refset 2y ago
Datomic is built around a simple log of fully serial transactions. It doesn't have MVCC or other such magic to coordinate concurrent writers, and this means (1) read-only queries don't require open transactions and (2) the whole s
110.
by refset 2y ago
> convincing a query planner to do the right thing requires deep expertise in the query planner The advantage is that that can be somebody else's job though, and ideally (eventually) an AI's job.
111.
by refset 2y ago
> this is partly because most people don't consider 'temporality' as a feature a database should offer Not sure on your definition of 'people', but I think every business ultimately wants solid auditing and rep
112.
by refset 2y ago
As it happens there's a talk happening next week at PGConf NYC on time travel and system-time versioning in Postgres by the DBOS team: https://postgresql.us/events/pgconfnyc2024/schedule/session/...
113.
by refset 2y ago
> that lets you query through time (also called "Bitemporal modeling" with fancier words) Datomic is actually only 'uni-temporal', it provides a database-wide, immutable "system time" (aka "transaction
114.
by refset 2y ago
I suspect there have been a great many examples and attempts at the ORM level - this one with "bi-temporal chaining" springs to mind: https://github.com/goldmansachs/reladomo And without the ORM layer there&#
115.
by refset 2y ago
The original RDBMS vision was very explicitly for the users (both developers and analysts) to not have to be experts in their own database in order to achieve useful work, and without needing to think about procedural/3GL code from the
116.
by refset 2y ago
> If there were a Datomic for Elixir, I'd probably use it. XTDB may possibly of interest in that case - there's been some recent chatter about adding support for Ecto via Postgres compatibility: https://discuss.xtd
117.
by refset 2y ago
> In databases like XTDB, the order of :where clauses doesn't matter since the engine is able to optimize them Rich's observation was that query optimizers often get things wrong in ways that are hard to predict or control, but
118.
Table transfer protocols: improved Arrow Flight and alternative to Iceberg(engineeringideas.substack.com)
1 points by refset 2y ago|0 comments
119.
by refset 2y ago
Also in Clojure, and reactive, and relational: https://github.com/wotbrew/relic > Functional relational programming for Clojure(Script).
120.
by refset 2y ago
I was surprised that this Jepsen report has never been discussed here before, but it really captures just how problematic the history of 'safe' database isolation levels has been. Some excerpts: > For the last nine years, Post

More ›