bradleymeck

5 ms·

1.
Irrefutable anecdotal evidence of Node.js sucking(youtube.com)
3 points by bradleymeck 15y ago|0 comments
2.
by bradleymeck 15y ago
So are all string based dictionaries?
3.
by bradleymeck 15y ago
Perhaps it is taking away a "feature" in some senses, but in my view it is taking the logical step not allowing concurrent access to preempt during execution. I often want the current value that has changed after the original context is c
4.
by bradleymeck 15y ago
By giving a shared in-memory resource for the current state of an object that is not mutated from other threads during a single stack build / teardown. Concurrent access in threads requires locking the object until it is in a determinate st
5.
by bradleymeck 15y ago
For me it is. However i tend to just use in-memory caches instead of a cache server, which may suffer the same issue. For standard websites, this is a non-issue for CRUD, for task/activity based sites that can have long lived tasks that per
6.
by bradleymeck 15y ago
When working with requests that share resources via web frameworks that deal with threads, the large consensus is to put the resource into an external managed resource. This external resource such as a database will manage the locking for y
7.
by bradleymeck 15y ago
Indeed not, but Erlang is Erlang, Hook.io is Hook.io, and Trolls are Trolls. More perspective on opinions would be helpful to evolving away from problems you see, and/or for the use of understanding your comment.
8.
by bradleymeck 15y ago
Hey all, just wanted to chime in about us using this at Nodejitsu. Hook.io makes it much easier to have a huge mesh network of drones for us and greatly simplified our management code for child processes on our stack. If you are looking for