Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rmgraham
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
61.
▲
Automatic Node.js Clustering with Log Aggregation
(strongloop.com)
4 points
by
rmgraham
12y ago
|
2 comments
62.
▲
by
rmgraham
12y ago
Bunyan and Winston are both decent but they still do too much. If your app isn't a logger itself features like log rotation, log levels, and configurable transports don't belong in your app. Just because you delegate those feature
63.
▲
What’s Coming to Node v0.12: A Overview of New Features
(strongloop.com)
2 points
by
rmgraham
12y ago
|
0 comments
64.
▲
by
rmgraham
12y ago
Postgres almost warrants its own non-generic ORM. That would actually be kinda cool.
65.
▲
by
rmgraham
12y ago
I work from home for a startup. My daughter is in the next room, I can hear her watching Curious George. And I still teared up reading the poem, because I could have written it myself. I don't know about the author, but for me the star
66.
▲
by
rmgraham
12y ago
Is is reasonable to expect generator based flow control to catch up to vanilla callbacks on performance eventually? Even under ideal circumstances we'd be looking at the overhead of the indirection, but I wonder if the mechanics of yie
67.
▲
by
rmgraham
12y ago
Maybe I'm weird, but I think I actually prefer the Express example. When I used Rails I found the biggest learning curve was actually learning how to get around the magic when necessary, leaving me craving something more like Sinatra,
68.
▲
by
rmgraham
12y ago
You can also use this to set up a bidirectional channel, allowing for bidirectional streaming. Really handy when your client isn't a browser.
69.
▲
Using Streaming Chunked HTML to Get Node.js to Deliver More Data
(strongloop.com)
3 points
by
rmgraham
12y ago
|
1 comments
70.
▲
by
rmgraham
13y ago
Do you realize your opinions _appear_ to be based on something that is 2 years old? It's not really logical to judge whether or not something has improved over the last 2 years if you're willfully avoiding most of the changes made
71.
▲
by
rmgraham
13y ago
The cluster control is pretty cool. Reminds me of spinning up dynos on Heroku but without the extra cost.
72.
▲
by
rmgraham
13y ago
The tricky part is transferring state between hot reloads, and that's part of what Erlang was designed around. State has to be passed in and owned by the callee. And if the format that state is stored in changes, you need to handle tha
73.
▲
by
rmgraham
13y ago
I think the author was trying to say that these online campaigns make people feel like they've contributed and therefore don't need to participate in a street protest. While I do see the parallel you are pointing out, I think &quo
74.
▲
by
rmgraham
13y ago
Thread safety in this case I think would mean running multiple instances of node embedded in your app, each in their own thread and with their own event loops.
75.
▲
by
rmgraham
13y ago
Is this the C++ accessible side of vm.createContext() and vm.runInContext()? Seems like it would help with sandboxing.
76.
▲
Announcing a StrongLoop npm Registry Mirror on Rackspace
(strongloop.com)
8 points
by
rmgraham
13y ago
|
1 comments
77.
▲
by
rmgraham
13y ago
It's definitely a trade-off. What Node gives you is async when you need it at the cost of giving you async even when you don't. The pain and constraints introduced by this forced use of async sure has spawned a lot of wheels of al
78.
▲
by
rmgraham
13y ago
Was the strongloop blog post modified since you linked to it? It really doesn't match your characterization of Issac Roth at all. Quite the opposite, actually.
79.
▲
by
rmgraham
13y ago
Looks like it: http://docs.strongloop.com/#openshift-cartridge
80.
▲
by
rmgraham
13y ago
Or luvit (libuv + Lua)
81.
▲
by
rmgraham
15y ago
I think the subtext there was that maintenance of large code bases and the associated productivity is inherently a people (developers) problem, not a technical (language) problem. It's normally considered foolish to attempt to solve people
82.
▲
by
rmgraham
15y ago
A couple years ago I decided to learn Python. I took a quick look, saw Python 3 was the "latest", and started working on my app, using http://docs.python.org/py3k/ as my guide. It wasn't until a month later when I went to deploy that I di
83.
▲
by
rmgraham
15y ago
In an office environment any co-worker can be a rubber duck for you. Of course, if all you can find are people who are knowledgeable about what you're working on, you may not need a rubber duck.
84.
▲
by
rmgraham
15y ago
1. http://ccodearchive.net/info/json.html
85.
▲
by
rmgraham
15y ago
It's been a while, but I'm pretty sure all of his books point out that 9/10 attempts result in failure; the trick being to see the failure early enough to recover and move onto the next attempt before it is too late.
86.
▲
by
rmgraham
15y ago
It allows coding in C++ in a fashion similar to Node by taking advantage of the lambda syntax added in C++11. It also makes use of libuv and http-parser, which are used in Node, to offer some of the same out-of-the-box functionality.
87.
▲
by
rmgraham
15y ago
I think some people might see Lua has giving more bang for your buck because of its popularity in things like game scripting among other things.
88.
▲
by
rmgraham
15y ago
You could probably stuff Node into this category too, if your target is the type to be impressed with writing their own basic web server in 10 lines of code.
89.
▲
by
rmgraham
15y ago
The demonstration reminds me of the link shared a few weeks ago about Ruby: http://news.ycombinator.com/item?id=3343205 Programming With Nothing
90.
▲
by
rmgraham
15y ago
I think the emphasis was supposed to be on before it launches . As in before it has seen a useful spectrum of usage upon which to base a review.
More ›