Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
michaniskin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
michaniskin
12y ago
The problem with the read-everything-into-memory approach is that this is not how the JVM ecosystem works. Things written for the JVM use the classpath primarily, and things in memory secondarily if at all. We can't control the fact th
62.
▲
by
michaniskin
12y ago
Yes, in the post I didn't get too technical with the treatment of tasks; I'll elaborate a little here. First, the command line thing. You're right that the command line isn't strictly required to use boot, you can do eve
63.
▲
by
michaniskin
12y ago
Totally agree. Also, in boot we don't want to obtain a complete configuration before tasks run, because tasks can participate in the process. In boot a task can add dependencies or call other tasks, etc. This is why we need only one ab
64.
▲
by
michaniskin
12y ago
Sorry, I should have mentioned that while boot, like any JVM build tool, does begin and end with the class path, we have spent an enormous amount of time experimenting with ways to mitigate the effects. We ended up with a system that provid
65.
▲
by
michaniskin
12y ago
All JVM build tools are side-effectful from the get-go, and they really have to be. Consider the :dependencies and :source-paths keys in a Leiningen project.clj. The purpose of these is to manipulate the mutable class path. To have a JVM bu
66.
▲
by
michaniskin
12y ago
The main reason why build tools exist is to perform transformations on a file set. The vast majority of the things build tools do that are useful are side effects. These "side-effectful" functions are basically transducers; the re
67.
▲
by
michaniskin
12y ago
The post was a demonstration of exactly that: cljs incremental builds with live-reload and cljs browser repl.
68.
▲
Get Rich with Hoplon, Part 1
(hoplon.discoursehosting.net)
22 points
by
michaniskin
12y ago
|
0 comments
69.
▲
by
michaniskin
13y ago
Hoplon's reactive model is quite different from React's. We think it's more advanced :). There are no "performance issues" reported lately (there was some confusion with an old proof-of-concept demo, but any recent
70.
▲
by
michaniskin
13y ago
The "prerendering" function isn't for human consumption. It's meant to make the page spiderable by search engines. Since it's a single-page app all content is on the page so the #/home/ links aren't r
71.
▲
A usable PHP console (REPL).
(github.com)
5 points
by
michaniskin
14y ago
|
0 comments