Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
olegp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
43 ms
·
391.
▲
by
olegp
14y ago
Last I heard Rhino master was about 10x slower on average, not 50. For most real world applications it doesn't make much of a difference, since you spend most of the time waiting on I/O. Here are some benchmarks I put together comparing V8
392.
▲
by
olegp
14y ago
I've implemented the inverse of this with Common Node ( http://olegp.github.com/common-node/ ). Common Node lets you run synchronous looking code compatible with RingoJS (server side JavaScript on the JVM) on Node.
393.
▲
by
olegp
14y ago
Yes
394.
▲
Why haven't web apps taken off yet?
(docs.google.com)
2 points
by
olegp
14y ago
|
3 comments
395.
▲
GMail is down
(twitter.com)
1 points
by
olegp
15y ago
|
1 comments
396.
▲
by
olegp
15y ago
You can get the best of both worlds: a synchronous programming model combined with the low memory memory usage of Node by using fibers. The trust issues relating to cooperative multitasking that you mention are still valid, but I haven't ru
397.
▲
by
olegp
15y ago
Nice. I had a go at implementing the same thing: https://github.com/olegp/tokenize Here's the discussion that got me thinking about it: http://news.ycombinator.com/item?id=3534921
398.
▲
by
olegp
15y ago
If you prefer a synchronous style (using fibers), I ported Stick from RingoJS: https://github.com/olegp/stick
399.
▲
The digital detective: Mikko Hypponen's war on malware is escalating
(wired.co.uk)
40 points
by
olegp
15y ago
|
9 comments
400.
▲
Linus Torvalds: The King of Geeks (And Dad of 3)
(wired.com)
251 points
by
olegp
15y ago
|
82 comments
401.
▲
AWS is down
(twitter.com)
7 points
by
olegp
15y ago
|
2 comments
402.
▲
by
olegp
15y ago
Debugging is a lot easier since you get meaningful stack traces. Performance is slightly lower due to context switching - check out the Common Node benchmarks I mention in another comment.
403.
▲
by
olegp
15y ago
I've run benchmarks comparing plain Node to Common Node (my library that uses fibers) and the version with fibers uses marginally more memory and on average has 75% of the throughput of the purely asynchronous code. You can find the benchma
404.
▲
by
olegp
15y ago
Alex, nice to see you working with fibers. I've recently ported Stick from RingoJS to Common Node. It seems to be similar to Ace (also using fibers etc.): https://github.com/olegp/stick In fact, some of the libraries I've made to work wit
405.
▲
by
olegp
15y ago
You end up with less code that's easier to maintain, in my experience. Check out this presentation I gave on the topic: http://www.slideshare.net/olegp/server-side-javascript-going...
406.
▲
by
olegp
15y ago
I've just ported Stick from RingoJS to Node, which does the same thing but lets you write code in a synchronous manner: https://github.com/olegp/stick
407.
▲
by
olegp
15y ago
They work in user-space and are portable, so I don't see the problem. Also, even if one opposes the idea of co-routines due to the problem of not knowing which function will yield, there's no denying that they provide one of the best curren
408.
▲
by
olegp
15y ago
I've found the traditional synchronous approach I am familiar with from Ringo ( http://ringojs.org ) a better fit for general purpose server side work, so I've made it possible on Node with the help of node-fibers. Common Node ( https://git
409.
▲
by
olegp
15y ago
If you prefer vanilla JS and are only working with Node, you should check out https://github.com/laverdet/node-fibers . I use it in my https://github.com/olegp/common-node package to address the same issues as those tackled by Stratified
410.
▲
by
olegp
15y ago
Have you considered making or supporting a slimmed down open source version of Parse? That way developers could self host and extend as necessary. Having the option to self host would probably increase adoption of your core offering.
411.
▲
by
olegp
15y ago
If you're only using CoffeeScript on the server, then you should check out node-fibers to achieve the same effect. Here's an example of using my Common Node library (that implements a number of sync APIs using fibers - http://olegp.github.
412.
▲
by
olegp
15y ago
Node has coroutine support via the fibers package: https://github.com/laverdet/node-fibers . For some benchmarks, check out my Common Node project's README: https://github.com/olegp/common-node
413.
▲
by
olegp
15y ago
I found all existing configuration management systems to be overly complicated and not modular enough. So, I've decided to try and reinvent the wheel with Bootstrap: https://github.com/olegp/bootstrap Any feedback or comments would be rea
414.
▲
by
olegp
15y ago
Funnily enough I just released Bootstrap ( https://github.com/olegp/bootstrap ) yesterday which addresses these very same issues I had with Puppet. I'm initially focusing on Ubuntu Server LTS on AWS EC2. As a result, it's all Bash and very
415.
▲
by
olegp
15y ago
Coroutines are available in Node via the fibers package ( https://github.com/laverdet/node-fibers ). For benchmarks comparing performance to purely asynchronous webapps, check out the README to my Common Node project ( https://github.com/ol
416.
▲
by
olegp
15y ago
On a related note, I'm working on a synchronous narwhal-mongodb compatible driver that would work with common-node ( http://olegp.github.com/common-node/ ), Would anyone be interested in helping out?
417.
▲
by
olegp
15y ago
What I meant was that if you use the email registered for amazon.com when signing up to AWS they don't create a separate account for you or suggest that you use a different e-mail to create a new account.
418.
▲
by
olegp
15y ago
I do find it odd that they encourage you to use the same account to sign into Amazon the store and AWS. That seems a bit like asking for a Subway loyalty card to buy a gun.
419.
▲
Hackers could have taken over AWS
(theregister.co.uk)
56 points
by
olegp
15y ago
|
19 comments
420.
▲
by
olegp
15y ago
Chrome extension.
More ›