hlship

7 ms·

1.
by hlship 2y ago
I've been working in Clojure now for about 12 years. Maybe 12+ years of Java prior to that. I've created some great apps, and great libraries (in both Clojure and Java). I often describe Clojure as "the least worst programmi
2.
by hlship 2y ago
The cli/deps.edn tooling is different from Leiningen, and far, far less complicated IMO. I've written a good number of Leiningen plugins and it was always brutal to get anything to work properly, especially in combination with
3.
by hlship 2y ago
~ > time bb -e '(println "Hello World")' Hello World bb -e '(println "Hello World")' 0.01s user 0.03s system 18% cpu 0.212 total bb is Babashka: a pre-compiled (using Graal), interpreted, scriptin
4.
by hlship 2y ago
It's based on unification, like a Prolog. It does backtracking, like a Prolog. It has something akin to Prolog "cuts". It's equally not Markdown. What it is, is the sensibilities of Prolog (for parsing words into player
5.
by hlship 2y ago
That was my frustration as well; and it comes up in discussions. Simple to medium complex things are easy in Inform7, but when you start hitting the edges, you find out that its expressive English-like syntax is in the uncanny valley and ex
6.
by hlship 2y ago
https://github.com/hlship/sanddancer-dialog
7.
by hlship 2y ago
So close to describing the Dialog IF language it’s almost prescient. https://linusakesson.net/dialog/index.php Dialog is a Prolog dialect: it’s like Markdown and Prolog had a baby.
8.
by hlship 2y ago
I’ve been building some friendly CLI and web tools around the terrific Dialog interactive fiction language. https://github.com/hlship/dialog-tool Learning Svelte for the web UI part.
9.
by hlship 2y ago
Clojure's slow, deliberate development pace confuses people. The core team takes backwards compatibility very seriously. What you see with each new Clojure release is generally improved performance, better Java interop, and a smatter
10.
by hlship 2y ago
Nubank purchased Cognitect (the consulting company behind Clojure) in 2020, as well as Platformatec (employers of Jose Valim); the latter was for access to Platformatec's project management expertise (see https://building.nu
11.
by hlship 2y ago
In traditional databases, only the database engine has a scalable view of the data - that’s why you send SQL to it and stream back the response data set. With Datomic, the peer has the same level of read access as the transactor; it’s like
12.
Pros/Cons of the "drive by" code fix?
2 points by hlship 2y ago|0 comments
13.
by hlship 3y ago
It's actually quite a bit more than REBL; the description downplays something quite significant ... it can run as a client against a running Clojure in a separate process. Although that sounds simple ("it's just data")
14.
by hlship 3y ago
That's not a very helpful, or accurate, comment.
15.
by hlship 3y ago
Babashka has unlocked so much power for me. Clojure and the JVM simply aren't set up for rapid start up, Babashka is instant. Bash scripting is alien, ugly, and hazard prone for me - Babashka makes it totally familiar, since it&#x2
16.
by hlship 3y ago
In such a system, how does a reader find the root node? I'd be concerned about a) readers seeing a partial write to disk (or page buffer) during an update or b) a crash while the writer writes to disk. I could imagine using two files,
17.
by hlship 3y ago
We had drying issues with our Miele that was addressed by using the rinse agent. Now generally dry results.
18.
by hlship 3y ago
Yes, and it caches results on the file system, so results persist between executions AFAIK. That comes in handy for one of my notebooks that has to slurp up Splunk data for 20 minutes.
19.
by hlship 3y ago
I've been using Clerk quite a bit lately and found it quite useful. Although I'm normally in a REPL loop, having control over the output ends up being very useful, and the ability to paginate long results, or graph them, it's
20.
by hlship 3y ago
Reverse engineering: Some of the things that Clojure generates are valid bytecode for which there is no Java source code equivalent. Reusing the pieces: In general, Clojure works so well because it is all of a piece, with many decisions and
21.
by hlship 3y ago
Although it is true that "time traveling" queries are relatively rare for production needs, the basic architecture supports things that many applications really need: - It is possible to make queries against the database PLUS addi
22.
by hlship 3y ago
That would be very ugly source, as Datomic is written in Clojure and AOT compiled to Java bytecode. Due to the architecture of Clojure (especially, the use of macros) it is not exactly possible to work backwards from JVM bytecode to anythi
23.
by hlship 3y ago
In a traditional database such as Postgres, queries are routed through a database server that handles both queries and updates, and is quite close to the storage. Reading excess data while executing a query is less of an issue as only the r
24.
by hlship 3y ago
It’s quite apples and oranges.
25.
by hlship 3y ago
Like any database, Datomic often needs to perform queries by reading data from its indexes. In fact, in Datomic, all data is stored in indexes - there aren't rows with indexes pointing to the rows, just indexes. Datomic uses any of a
26.
by hlship 4y ago
I wonder what the real story is here. When I left Walmart last June, the Portland office was already 100% remote, with no intention of reopening the office (it had been WeWork space before the pandemic). My team had been 100% remote since i
27.
by hlship 4y ago
Not quite a beginner book, but you should check out https://www.amazon.com/Mazes-Programmers-Twisty-Little-Passa... .
28.
by hlship 4y ago
https://starburns.audio/podcasts/humans-who-make-games/
29.
by hlship 4y ago
I'm also a fan, and also lamenting that it hasn't continued. The conversations are really long, and often funny, and interesting.
30.
by hlship 4y ago
How did we manage to post that same observation almost simultaneously?

More ›