johnm

15 ms·

121.
by johnm 16y ago
Do note clearly that V8's garbage collector is fairly slow (think old Java GC) so having more instances of node with smaller heaps is a good idea anyways.
122.
by johnm 16y ago
Depending on your workload, 1 node per 2 cores is a better rule of thumb. Also, split the networking across multiple NICs.
123.
Redo: a replacement for make based on ideas by djb(github.com)
7 points by johnm 16y ago|0 comments
124.
by johnm 16y ago
What kind of interns? Engineering or something else?
125.
Selling Open Source(blog.robrhyne.com)
5 points by johnm 16y ago|0 comments
126.
Zombie.js -- headless full-stack testing using node.js(zombie.labnotes.org)
110 points by johnm 16y ago|14 comments
127.
by johnm 16y ago
No, it's the interactions between all of the boatload of features of the language that causes the explosion of complexity.
128.
by johnm 16y ago
Scala is to Java as C++ is to C.
129.
Networking Named Content [pdf](conferences.sigcomm.org)
1 points by johnm 16y ago|0 comments
130.
by johnm 16y ago
FWIW, if you change "unstructured" to "semi-structured" then Norm's argument works much better.
131.
by johnm 16y ago
'When Rinpoche told my wife that he was being billed as “the happiest man in the world,” he laughed as though that were the funniest joke he’d ever heard.' Well, at least he gets it.
132.
by johnm 16y ago
It's not that simplistic. It's important to go after a mix of companies (of different sizes, strength) so that you can set precedence, get quick settlements (i.e., funding to help playing chicken with the deep pockets), etc.
133.
by johnm 16y ago
Um, er, the trolls go after the small fry, too.
134.
by johnm 16y ago
Use versions like /v1/ . If there's no version... * If there request is plain html then deliver a human readable documentation page (that still has hyperlinks for discoverability. * If the request is asking for whatever your application typ
135.
by johnm 16y ago
You end up with a "culture" whether or not you worry about it. Of course, what you end up with if you don't worry about it might not help you actually succeed.
136.
by johnm 16y ago
Indeed. Most people use "complex" when they really mean "complicated".
137.
by johnm 17y ago
What are the threat models that you care about (in some sort of rough rank order)?
138.
by johnm 17y ago
So much good advice that's high-level so here's a real simple one... Trim your nails.
139.
by johnm 17y ago
Less than you want and more than you think.
140.
by johnm 17y ago
markmail, krugle, imdb
141.
by johnm 17y ago
Nuture nature.
142.
by johnm 17y ago
This sounds perfect for a native XML "database". Check out e.g., MarkLogic Server. That's what we built http://markmail.org/ on top of.
143.
by johnm 17y ago
Convenient how there's no memory architecture & bandwidth numbers. :-(
144.
by johnm 17y ago
So much better than so much of the discussion around Tornado, that's for sure. Definitely would like to see two more takes: * long-poll setup (lots of idle connections with sporadic bursty activity) * thundering herd (max sustainable active
145.
by johnm 17y ago
Yes, most of the full talks are being recorded and will be posted.
146.
by johnm 17y ago
Yes, they've said that everything is an object. But, the whole question of interop with Java is still in flux.
147.
by johnm 17y ago
One goal of the summit is for implementors (of languages and/or runtimes) to have a chance to talk through issues so it fits in with the conference just fine. The hype in the article is the problem.
148.
by johnm 17y ago
Article fail. It's not "delivered" -- it's a language in the process of being designed.
149.
by johnm 17y ago
Indeed. These types of interviews are much more about finding people who "think outside the box... just like me!" than about finding people who can do the job.
150.
by johnm 17y ago
The MarkLogic server is a native XML database. It's designed and written from the ground up to do XML. That's why it's so much better/faster than the competition. Storage-wise, it's often the case that the MLS DB for a project is actually t

More ›