serialdev

Is there an equivalent modelling approach for earthquake prediction? A data repository for it widely shared on the same line as the top comment would work

You will not believe what it is all you need!

This is exactly my thought, check the video I posted on twitter @serialdev , I was thinking of the usual loop unrolling , caching , vectorize , if with a managed Lang compile, check intrinsics and then even explore SIMD. I'm honestly impressed by ChatGPT

I see the appeal. But I gotta say to constraint yourself to only California or Rotterdam is kind of missing that hacker vibe that cares about results and content. Not just hype.

Anything opensourced from it?

Wow! thanks for pointing out there is an Elisp Shen implementation!

Specifically when learning and applying compiler development, advancing to more complex use-cases (code optimization, parallel compilation), programming language theory etc? Do you still use BNF Grammars with Parser Generators, or do you use Parsing combinators? Are you using a specified IR like LLVM's or if not why is that your choice? How do you deal with targetting multiple Architectures?

I've applied, this looks very exciting! Does the backend team, work with the underlying Information retrieval engine too?

One difference is flow control. When you call a function, all the arguments are evaluated before being passed into the function. If you want to delay evaluation, you have to wrap the argument values in a function. When you call a macro, the text forms get passed with no evaluation. Say Clojure forgot to ship with the boolean "or". "or" should evaluate its arguments one at a time (to allow for short circuiting) and return the first non-false value. You could do this with functions, but you have the source-level overhead of manually wrapping everything, and performance overhead of defining and passing an anonymous function for each argument. With a macro, at compile time you just translate the "or" macro into a simpler form that uses "if". This is how Clojure actually implements "or":

    (defmacro or
      "Evaluates exprs one at a time, from left to right. If a form
      returns a logical true value, or returns that value and doesn't
      evaluate any of the other expressions, otherwise it returns the
      value of the last expression. (or) returns nil."
      {:added "1.0"}
      ([] nil)
      ([x] x)
      ([x & next]
          `(let [or# ~x]
             (if or# or# (or ~@next)))))

Also check this http://lists.warhead.org.uk/pipermail/iwe/2005-July/000130.h...

I'm curious if any of you have tried it against another commercial graph db like AllegroGraph?

A bit out of topic but I remember you mentioned you were working on a lisp book and asked what we would wanna see on it. Well for me, I'm super curious about compiler development, and I think, in the topic of this thread, maybe a chapter on writing a recursive descent parser for JS? building a transpiler? or using lisp as a intermediary with LLVM IR? somewhere where either DSL || "Code is data" and the true advantages of lisp shine through, and I would love that from an experienced lisper. Also if you could go into some use cases for tunable compilers that are seldom elaborated when that is mentioned as a huge lisp advantage! Thanks for giving the community your time in advance!

This really makes me excited, there is no reason why we cannot implement a thorough type-system like qi and shen on top of common-lisp for massive teams, the repl experience is still unparalleled, and I for one would love more libraries popping up, so maybe more people can make a business case for it. Machine learning in python is nice, but I would definitely enjoy common lisp for it too!

Well for me, I'm super curious about compiler development, and I think, in the topic of this thread, maybe a chapter on writing a recursive descent parser for JS? building a transpiler? or using lisp as a intermediary with LLVM IR? somewhere where either DSL || "Code is data" and the true advantages of lisp shine through, and I would love that from an experienced lisper. Also if you could go into some use cases for tunable compilers that is seldom elaborated when that is mentioned as a huge lisp advantage! Thanks for giving the community your time in advance!

Please do, there is sadly not enough stuff related to lisp, specially valuable stuff from people that were working during the AI boom. I for one would more than welcome any thorough project/info from your perspective