ryah

7 ms·

1.
by ryah 14y ago
A recent article in nytimes discussed research that estimates the cost of some government regulations on businesses. It's done by first noticing that company size follows a power-law distribution and then measuring deviations. I wonder if y
2.
Introduction to libuv [video](blog.nodejs.org)
21 points by ryah 14y ago|0 comments
3.
by ryah 14y ago
Kudos should go to Bert Belder and Ben Noordhuis of Cloud9 who built much of libuv and Igor Zinkovsky of Microsoft has contributed a lot of important work as well. As well many other contributors.
4.
by ryah 14y ago
Yep, serialized message passing between threads is slower - you didn't have to go through all that work. But it doesn't matter because that's not the bottleneck for real websites. Also Node starts up in 35ms and doesn't require all those pa
5.
by ryah 14y ago
Node is popular because it allows normal people to do high concurrency servers. It's not the fastest or leanest or even very well put together - but it makes good trade offs in terms of cognitive overhead, simplicity of implementation, and
6.
by ryah 14y ago
it's all serialization - but that's not a bottleneck for most web servers. i'd love to hear your context-switching free multicore solution. this is the sanest and most pragmatic way server a web server from multiple threads
7.
by ryah 14y ago
Trouble? Node.js has linear speedup over multiple cores for web servers. See http://nodejs.org/docs/v0.8.4/api/cluster.html for more info.
8.
by ryah 14y ago
isaac likes semver - so probably that
9.
by ryah 14y ago
Node follows a even/odd version scheme where even releases are stable and odd releases are unstable. v0.9.0 is just the first release of the unstable v0.9 series. The versioning scheme is unfortunate because it confuses people. After Node 1
10.
by ryah 14y ago
"not a good fit" You're speaking of HTTP: the protocol on which a great deal of world's computing infrastructure is being set on top of. The protocol which we are communicating with each other over right now. HTTP on TCP is extremely succes
11.
by ryah 16y ago
docs are wrong, it defaults to utf8
12.
by ryah 17y ago
build and/or packaging systems
13.
by ryah 17y ago
You should read my reply again (or maybe for the first time) and comprehend. I did not say nor imply that I think Erlang's processes are OS processes. Sorry for not using quotes ('process') if that's what has confused you so deeply.
14.
by ryah 17y ago
Something that's different, at least from POE, EventMachine, Twisted is that it is attempting non-blocking purity. You can snub your nose at this but it turns out to be very important. It ends up abstracting away a problem in a way that Eve
15.
by ryah 17y ago
clearly you're unfamiliar with http.
16.
by ryah 17y ago
> Sure - speed++, but at what cost? it only has to be written once. i think it's an important enough problem to warrant such code - definitely could use a few more macros though
17.
by ryah 17y ago
I want a build system with an external API.
18.
by ryah 17y ago
> which is just unfounded bashing. i'm always surprised to hear things like this. it's certainly not unfounded - it's just so obvious and universally accepted that it doesn't require explanation - one would think.
19.
by ryah 17y ago
This is the top story on hacker news?
20.
by ryah 17y ago
> I'm mostly curious so that I can try to avoid any such pitfalls in any server software I might write. If you start a thread for each connection, you're doing it wrong.
21.
by ryah 17y ago
That has to do a lot with Ruby's awful thread implementation. You could possibly port the app again to Ruby EventMachine and see even better performance. The point is - for 99% of people it's not the language, it's the I/O
22.
by ryah 17y ago
> Are Node people going to reimplement event-driven MySQL client from scratch or what? No. MySQL does not provide an API that is usable with an event-loop, so it will need to be run in a separate internal thread. It will notify the main
23.
by ryah 17y ago
Web site performance problems usually don't have much to do with the raw executing speed of the language they're written in. The problems derive from poor understanding of how to handle concurrent connections. If your app is written in C, b