scriby

8 ms·

31.
by scriby 15y ago
Don't like callback hell? Use fibers. https://github.com/scriby/asyncblock (My pet project, a flow control library built on fibers that gives you all the benefits of async programming without the callbacks)
32.
by scriby 15y ago
Yes. At least in my own apps. Model instantiation being a bottle neck practically implies that you generate models in a tight loop and do nothing else with them, such as persisting them.
33.
by scriby 15y ago
"Performance cost of Ruby ORM model instantiation" may not have been the best title :)
34.
by scriby 15y ago
Developers hire other developers that think like themselves. Technically oriented developers hire other technically oriented developers. A mediocre developer won't be able to distinguish who knows their stuff or not. But at least getting te
35.
by scriby 15y ago
I worry that this sort of article could be misinterpreted easily, even with the disclaimer. It's talking about optimizing something that takes less than 1% of the vast majority of an application's cycles. Which doesn't really mean anything.
36.
by scriby 15y ago
User experience > cute technical solution
37.
by scriby 15y ago
That makes sense. I've been doing node js too long where you have to do this stuff by hand :0
38.
by scriby 15y ago
This looks wide open to csrf attacks. Another site can post a form on behalf of a user automatically, and the cookies for job poacher will be sent. Meaning that a malicious site can take actions on behalf of a logged in user. Perhaps their
39.
by scriby 15y ago
I think in the real world there are a variety of cases that benefit from parallel operatio... -Anything dealing with disk I/O like copying or reading files -Sending / receiving from S3 or other file repository -Making a request to external
40.
by scriby 15y ago
I'm saying the framework doesn't have support for parallel tasks within a single request. For example, the case of kicking off two database queries in parallel, then doing something when both are finished. I understand that each request exe
41.
by scriby 15y ago
This appears only to support one-at-a-time synchronous control flow. Giving up parallel tasks is a funny proposition in node, as it's one of its greatest strengths. So this framework still seems limited in the potential uses, but maybe it w
42.
by scriby 15y ago
I have to disagree with this. There's plenty of ways to be creative and still be disciplined. I find myself spending a lot of cycles reducing solutions to their most simple form -- removing everything unnecessary until just what's required
43.
by scriby 15y ago
My team at work uses Webstorm. It's a bit of a memory hog, but it works pretty well. The integrated debugger is great, and you get immediate feedback if your JS doesn't parse. The main weakness is the autocomplete could be a little smarter,
44.
Selecting a javascript flow control solution(github.com)
2 points by scriby 15y ago|0 comments
45.
by scriby 15y ago
I wrote a module based on fibers to help with these sort of problems. Take a look at https://github.com/scriby/asyncblock
46.
Vote for an official MongoDB driver for NodeJS(jira.mongodb.org)
1 points by scriby 15y ago|1 comments