Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bakkdoor
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
bakkdoor
5y ago
It's completely down now.
2.
▲
Profiling JIT-ted Ruby code with OProfile on Rubinius
(rubini.us)
1 points
by
bakkdoor
14y ago
|
0 comments
3.
▲
by
bakkdoor
14y ago
On a german keyboard \ is not just "a single keystroke". What a pain -_-
4.
▲
Fancy Update: OptionParser, FDoc and a built-in debugger
(bakkdoor.net)
1 points
by
bakkdoor
14y ago
|
0 comments
5.
▲
by
bakkdoor
14y ago
"In the case of an acquisition of G-WAN's Copyrights, the new owner would be the best promotional player of parallelized architectures, and therefore a desirable partner for Intel, AMD, ARM, IBM and Oracle. This fact alone should sustain th
6.
▲
by
bakkdoor
14y ago
Gotta love their "insurance": http://gwan.ch/insurance o_O
7.
▲
by
bakkdoor
14y ago
this is insane.
8.
▲
Why you should never use hash functions for message authentication
(blog.jcoglan.com)
171 points
by
bakkdoor
14y ago
|
101 comments
9.
▲
by
bakkdoor
15y ago
I just added conditions & restarts today to Fancy ( http://fancy-lang.org/ ). It's currently in a branch but it works =).
10.
▲
by
bakkdoor
15y ago
Yes.
11.
▲
by
bakkdoor
15y ago
The current implementation of futures uses a thread pool. I'm planning on changing this a bit to behave more like Io's actor model.
12.
▲
by
bakkdoor
15y ago
Hi, I'm the author of Fancy. The erlang-style actor message passing hasn't been implemented yet. I'm workin on that though. Rubinius has a built-in Channel type, (similar to go) and an Actor library built on top of it. Once I get some of th
13.
▲
Why Use Rubinius
(rubini.us)
73 points
by
bakkdoor
16y ago
|
20 comments
14.
▲
by
bakkdoor
16y ago
Yeah, I'll probably write up some of the stuff I've been doing with Fancy soon.
15.
▲
by
bakkdoor
16y ago
Btw, here's a list of current features I forgot to link to in the post: https://github.com/bakkdoor/fancy/blob/master/doc/features.m...
16.
▲
by
bakkdoor
16y ago
You mean symbol literals? Ruby uses :foo but that would mix up with the keyword message syntax. So I took Lisp's syntax: 'foo =) Also, since you'll want to have syntax for message names as well, they need to be able to have colons in them,
17.
▲
by
bakkdoor
16y ago
it's super effective!