_halgari

9 ms·

31.
by _halgari 10y ago
CLJS has been self hosted for about a year now. It's cool, but its really not needed. Google Closure on the other hand is amazing. I've seen speed improvements of 10x when switching to advanced compilation mode. Its not just dead
32.
by _halgari 10y ago
If you enable source maps you can set breakpoints in your cljs code. And IIRC browsers are testing support for non JS reply right now.
33.
by _halgari 10y ago
React is about the only real framework in the ClojureScript community, via frameworks like Om.Next and Reframe. React in JS is rather clunky since you're dealing with a mutable language that prefers OOP primitives. In ClojureScript mos
34.
by _halgari 10y ago
Absolutely, I think the "perfect world" would be adopting some of the ideas Rich proposes but adding (git url + sha) as the dependency management system. Of course for that to work well you'd also need to protect yourself fro
35.
by _halgari 10y ago
Sadly then Go went and shot themselves in the foot. Originally (I assumed this hasn't changed), you specified dependencies via git URLs. Sounds great, but then they went and said every dependency always used the head of master. So now
36.
by _halgari 10y ago
Read up on Lisp Favored Erlang, there's a lot of reasons why Clojure doesn't work well on BEAM, and they're covered by the author of LFE.
37.
by _halgari 10y ago
Exactly my thoughts. Every DSL needs an escape hatch at some point. What do I do when EVE isn't fast enough or lacks some feature I need.
38.
by _halgari 10y ago
ZMQ's default behavior (and in some cases only behavior) of dropping new messages when buffers are full, made it a no-go for my client. We ended up switching away from ZMQ to a more traditional durable queue and ended up saving a ton o
39.
by _halgari 10y ago
"Elixir is blazing fast" it says, so I follow the link and notice that "blazing fast" apparently means 10x the speed of Ruby. I don't think that phrase means what they think it means.
40.
by _halgari 10y ago
You honored my rant with a reply, so I will honor it with a reply as well :) The problem is this...when software is designed it is critical to know what is being solved. I don't think the problem set or the way they will be solved has
41.
by _halgari 10y ago
At this point the Eve project is so far out in left-field it's astounding. If you start with Lighttable and move on through Aurora and Eve you see the same patter over and over. 1) say X is broken we should fix it 2) we will fix X in a
42.
by _halgari 10y ago
I tend to agree. In my opinion, if a job interview required me to brush up that much on a topic it either means: a) the company is putting to much emphasis on "non-google" programming, which doesn't match reality (real softwa
43.
by _halgari 10y ago
Install IntelliJ install cursive. Done. Have a friend who as learning to program. He got Cursive going in less than 30min
44.
by _halgari 10y ago
Something that is often very hard to understand (it took me years to do so). Is that maintaining a language is insanely hard. Everything has a cost. Let me give a good example: A few years back someone submitted a patch that improved the er
45.
by _halgari 10y ago
After some truely horrific experiences with Riak K/V, especially combined with Riak Solr, I won't touch anything from Basho with a ten foot pole. Not sure what's going on over there, but the reality of Riak in production was
46.
by _halgari 10y ago
Can you link a quote or a point in that video? What does Boeing's use of Clojure have to do with Cognitect?
47.
by _halgari 10y ago
I find it highly implausible. Most likely OP ignored the full context of the statement. I can't imagine any of my co-workers recommending Java Maps over PHMs except in very rare interop situations. Likewise, I can't remember the l
48.
by _halgari 10y ago
>> "don't use persistent data structures, use Java's" Love to see a reference for this.
49.
by _halgari 10y ago
yes, to bump a version number in a build script. the last meaningful change was 3 months ago.
50.
by _halgari 10y ago
This article is several months old, and the linked repo hasn't been updated in about two months.
51.
by _halgari 10y ago
No, it's just that things like actors and STM, and yes, even LMAX are completely overkill for many of the projects out there. Go read up on what LMAX was designed to solve, millions of messages a second. I've worked on several ver
52.
by _halgari 10y ago
Except some of us understand these concepts, see how they can be used, but yet don't understand why we would ever use them. In all these sort of articles I've never seen something that can't be done simpler with a bit of muta
53.
by _halgari 10y ago
Programmers should know their trade-offs. It's not so much that STM should be avoided, but that the use cases it was designed for don't often present themselves in production. Same with agents, core.async, metadata, etc. So I also
54.
by _halgari 10y ago
Pieter, I spoke with you back in 2013 at CodeMesh, about OSS development. I remember asking "if you default to merging PRs even if you don't agree with the, how can you assure quality control". And IIRC your answer was someth
55.
Why AlphaGo Matters(benkampha.us)
1 points by _halgari 11y ago|0 comments
56.
by _halgari 11y ago
Agreed, I'm not even convinced you need anything async here. In that sense you could probably write this with OS threads and you language of choice.
57.
by _halgari 11y ago
Big hairy core.async go blocks like shown in these articles makes me a tad uneasy (see the sync source in the second part to this article). Because they seem to be programmed in a mostly imperative style. Almost every time I see a go block
58.
by _halgari 11y ago
It's an excellent paper. The way it describes logic programs as a stream of environments is very general. I've taken the basic concepts in this paper and implemented them with Clojure lazy seqs, CSP ( https://github.com&
59.
by _halgari 11y ago
I recommend the following: 1) read up on how Om.Next handles remote calls. Not that it's the only way to do it, but it de-couples the async functionality of a remote call from the rendering loop. 2) Just code against something like Goo
60.
by _halgari 11y ago
One of the reasons that ClojureScript is so fast and efficient is that it leans heavily on the Google Closure optimizing compiler. This compiler goes beyond normal "minimzation" and goes into dead code removal, function inlining a

More ›