andrewvc

57 ms·

481.
by andrewvc 14y ago
Interesting results. While it's not surprising to me that the pure java implementation was far and ahead better since: 1.) Java's much faster than Javascript, and 2.) Netty (which Vert.x is based on), has been doing high performance async I
482.
by andrewvc 14y ago
Same reason as perl, writing a ruby parser is hard, writing a lisp reader is easy
483.
by andrewvc 14y ago
So, I googled 'finagle java' and all the results were terrible. There was no concise description with a short example. Nothing led me to believe 'node.js' clone in anything I saw in the first few results. In fact, the first result was this:
484.
by andrewvc 14y ago
I'm really excited about this. While node-js is a great project, it still doesn't have the awesome instrumentation and tooling around it the JVM does. Additionally, real threading is damn nice, and the JVM definitely has that. Combining thi
485.
Learn Clojure's lazy-sequences through elementary automata(github.com)
2 points by andrewvc 14y ago|0 comments
486.
Engulf, A Graphical HTTP Benchmarker written in Clojure + D3.js(github.com)
7 points by andrewvc 14y ago|1 comments
487.
by andrewvc 14y ago
Santa Monica, CA Pose.com is a fast growing social network for style and fashion. We're looking for talented Ruby / Rails, Backbone.js, iOS, and Android developers. Our team is fun and small. We're 6 talented hackers and are looking to add
488.
by andrewvc 15y ago
Well, the site won't load for me, but so long as we're on the topic of clojure newbie stuff, I just put together a simple project on github to demonstrate lazy-evaluation for those new to clojure by visualizing elementary cellular automata.
489.
by andrewvc 15y ago
Closer to memcachedb than redis given the command set, but sill very cool.
490.
by andrewvc 15y ago
I've used node, and I just don't see it. You can share fragments of code, but for reasons of both security and logic not much more. In my view, the evented nature of node negates most of the pluses of one language. Additionally, javascript
491.
Noir-async: seamless async webservices for clojure(github.com)
4 points by andrewvc 15y ago|0 comments
492.
by andrewvc 15y ago
If you want to divine whole worlds of phantom meanings from innocuous phrases I'd recommend picking up PoMo lit-crit as a hobby, it's where such speculation belongs. For the record, I hardly view women as 'pleasure devices', and "picking up
493.
by andrewvc 15y ago
This is proof that all you need to get up the front page on HN is a title that matches the current zeitgeist. The article itself is terrible, making mountains out of molehills. I'm someone who'd never even be confused as a brogrammer, but s
494.
by andrewvc 15y ago
Interesting, but how is this different than Netty? I'll admit, netty's interface is annoying, but that aside, from a perf perspective does this offer anything?
495.
by andrewvc 15y ago
So, in a nutshell, we're seeing a swing back to RPC. I think that's great, bidirectional RPC is much nicer than REST. REST is great, but a good portion of the time proper rest begins to feel like square peg round hole, that's why we see end
496.
by andrewvc 15y ago
I strongly disagree. There's no such thing as baseline speed, there's only baseline speed on a given hardware config. Rails does not have a max speed of X reqs/second. It has a max speed of X reqs/second on a given hardware config. If you'r
497.
SB Hackercast #1 Clojure, Python & Ops, and Ninjas(sbhackercast.com)
18 points by andrewvc 15y ago|2 comments
498.
by andrewvc 15y ago
This is disgusting. Taking an international movement against dictatorship and comparing it to trends in the tech sector? Not only is this a poor analogy, it's outright disrespectful.
499.
by andrewvc 15y ago
I'm really pretty anti-node, but this article isn't very good. The concerns here are mixed up and not very thorough. All these points need graphs, charts, something solid to anchor them to. This is the sort of article that polarizes, but do
500.
by andrewvc 15y ago
Agreed, I was using XFS aggressively on ~20 servers with wildly varying IO loads 4-5 years ago and it was rock solid.
501.
by andrewvc 15y ago
I just switched from ViM to emacs (mostly for SLIME) after about 6 years of ViM usage, it wasn't a big deal at all, both are great.
502.
by andrewvc 15y ago
Here's the question I have. Perl5 -> Perl6 is not a natural progression. It's such a radically different language that going to say Python or Ruby is nearly as similar a change. Why's it obvious to you guys?
503.
by andrewvc 15y ago
Kodak needed to shift from film and printing accessories to hardware / software manufacture. Kodak never really managed that transition, they should have been competing with Canon, Nikon, and Adobe. They had the resources to give it a shot,
504.
by andrewvc 15y ago
This is a very expensive operation if you have a large number of keys, and can easily block redis. keys is intended for debugging a relatively small number of keys. Basically, if you're having to do this in prod, you may be fucked.
505.
by andrewvc 15y ago
Sure there are, kpeg, citrus, treetop... Probably more I don't know about.
506.
by andrewvc 15y ago
I'm really glad for this post. I'm the organizer of LA Hacker News ( http://www.meetup.com/Los-Angeles-Hacker-News/ ), and I've found that posts for upcoming metups just don't make it to the frontpage anymore. Luckily, we built up tractio
507.
by andrewvc 15y ago
Speed aside, maintaining certs for all your backend servers would suck.
508.
by andrewvc 15y ago
Cool stuff, but I'm wondering why they went with REP/REQ instead of ROUTER/DEALER. That would dramatically reduce the number of file descriptors needed (indeed, a single socket could handle any number of backends / requests). Also, the fact
509.
by andrewvc 15y ago
What's missing in the description here is that Puma is built for Rubinius and jRuby, which both have true multithreading (no GIL). I'm not sure if it's considered production ready yet though.
510.
by andrewvc 15y ago
Completely agreed. When I work on code I have a sliding scale of likelihood of re-usability in mind for a given task that determines how I write it. A piece of code that defines complex behavior for a weird list type with strange properties

More ›