Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
_halgari
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
_halgari
11y ago
let's not forget crazy stuff like going into debug mode and then evaling random clojure code in the context of the debugger
62.
▲
by
_halgari
11y ago
It really only rears its ugly head with user-defined macros that define locals/vars. Thankfully this sort of thing is pretty rare, and when I do use them I get some extra highlighting, so it's not a big deal.
63.
▲
by
_halgari
11y ago
After Emacs/Cider/whatever crashed/locked up on me for the 20th time I finally gave up and moved to Cursive over a year ago. I've never looked back, it's fast, does what I need it to, and I still discover features a
64.
▲
by
_halgari
11y ago
Core.async uses code rewriting to turn blocks of code into state machines. From there puts and takes from channels become state transitions. It works almost exactly like async/await in C# or Yield based generators in other languages. T
65.
▲
by
_halgari
11y ago
The library is fundamentally flawed, as the first bug report shows: https://github.com/liebke/avout/issues/1
66.
▲
by
_halgari
11y ago
I tried once or twice, but each version seemed to be less and less intuitive. The last version I tried even removed all the menus, you'd boot it up and just get a blank screen. I finally switched to Cursive Clojure, stuff just worked o
67.
▲
by
_halgari
11y ago
Right, this is basically a validation library
68.
▲
by
_halgari
11y ago
Like this? https://github.com/clojure/tools.emitter.jvm
69.
▲
by
_halgari
11y ago
Clojure is pretty big in some places. The list here: http://clojure.org/Companies includes Staples Sparx, Walmart Labs, Groupon, and several other well known names.
70.
▲
by
_halgari
11y ago
Eh, IMO (let [x (+ 1 2) y (+ x 3)] (* x y)) Is always less verbose than: (let ((x (+ 1 2)) (y (+ x 3))) (* x y)) I program in Clojure every day, and that latter example makes me say "a
71.
▲
by
_halgari
11y ago
That's mostly because such lisps are overly verbose. The same code in Clojure: (let [hello (fn [] (println "Hello World"))] (hello)) Or assuming hello is a global in your dart example:
72.
▲
by
_halgari
11y ago
Support for ClojureScript recently got a lot better in Cursive Clojure. I recommend giving it a shot.
73.
▲
by
_halgari
11y ago
It's pretty trivial to fix the default locations that Pixie looks for files. Create an issue on our github page and I'll help you get it working.
74.
▲
by
_halgari
11y ago
There's something pretty wrong with that example. Times from my RPi2: time ./pixie-vm ./examples/hello-world.pxi Hello, World! real 0m1.167s user 0m1.160s sys 0m0.000s
75.
▲
by
_halgari
11y ago
The jit works, it's just that RPython's support for cross compilation is weak, and it requires a fair amount of memory to compile. The gist of it all is that compiling pixie with a JIT for ARM requires an ARM machine with at least
76.
▲
by
_halgari
11y ago
(author of Pixie here) It's mostly in syntax and the naming of functions. Our current though process is that we'll default to Clojure syntax/semantics where possible, but if the language will be faster or more flexible withou
77.
▲
by
_halgari
11y ago
It's funny to see this stuff go full-circle. My parents left the city in the early 90's to move to a small WI farm in the middle of nowhere (15min to get to a town of 5000 people). I can see the appeal of a simpler life. But the f
78.
▲
by
_halgari
11y ago
The best description of concurrency vs parallelism I've heard is from "Clojure for the Brave and True" where it's described via a Lady Gaga song, pure genius: http://www.braveclojure.com/concurrency/
79.
▲
by
_halgari
12y ago
Sadly I can't get too interested in a machine like this. What I want in a work machine is the following: 1) 16GB RAM (or more) 2) High density display 3) SSD drive 4) Quad core or better CPU 5) Small and thin 6) Discrete NVIDIA GPU (no
80.
▲
by
_halgari
12y ago
You know, I forget now. It was a trivia question at Clojure/Conj 2012.
81.
▲
by
_halgari
12y ago
Few people know that Clojure was not the first lisp worked on by Rich Hickey (I think Clojure was the 5th?). This was the last one he wrote before he started work on Clojure.
82.
▲
by
_halgari
12y ago
This (among a few other reasons) is why Jesus went on a rant against the religious leaders of the day in Matthew chapter 23. One of the practices at the time was for Pharisees to give all their possessions to the temple (of which they were
83.
▲
by
_halgari
12y ago
The great point made in the README is that we can't generate feature expressions. With feature macros we can have macros that generate cross-platform code. That's big in my mind. That hasn't been a problem with reader macros
84.
▲
by
_halgari
12y ago
a clean and simple approach to the problem, +1
85.
▲
by
_halgari
12y ago
I'm not sure why this got down-voted, but I thought the same thing while reading the article. If you store the game state as a giant hash-map (as I would in Clojure), then problems of "is-a" and "has-a" don't r
86.
▲
by
_halgari
12y ago
The two JITs are completely different. LLVM uses method level inlining, and doesn't do too well with removal of GC malloc calls, or at least it doesn't do this by default. RPython's JITs however, are tracing jits. They trace
87.
▲
by
_halgari
12y ago
I completely agree with this article. I was surprised how fast I was able to implement the guts of pixie ( http://github.com/pixie-lang/pixie ) using RPython I had a repl, with a JIT and a GC done in about 40 hours of wo
88.
▲
by
_halgari
12y ago
I love clojure, let me make this clear. But there are certain aspects of the language that don't apply if you are writing a VM from scratch in RPython. If I could make multimethods dispatching on types as fast as protocols, what is the
89.
▲
by
_halgari
12y ago
CLOS has been on my list to research for some time now, and I haven't made a decision on it yet. The goal would be to get the JIT to remove the method lookup completely, and that might get a bit tricky depending on how complex the look
90.
▲
by
_halgari
12y ago
Author of pixie here. The project is still pretty young (about a month old), so I'll use that to explain away the lack of binaries, documentation, examples, etc. I've been more focused on adding features than getting stuff ready f
More ›