HN user

Ivatar

13 karma
Posts0
Comments7
View on HN
No posts found.

Doesn't seem to be familiar with factor:

  : foo ( seq -- nseq ) [ 1 + ] map ;
"This looks like ruby. It could also be lua, though. I'm not completely sure."

I would have expected a guess at forth, but I really don't think it looks like ruby...

Actually, the zIIP and zAAP processors for "accelerating" java or db2 workloads are identical to the other processors in terms of hardware; the underlying firmware just loads different microcode onto the chip to prevent it running a full Z/OS instance.

The difference is one of licensing -- IBM charges less for activating a core if you can only run java|db2|linux on it.

They may actually put an accelerator in the system at some point in the future, but for now it's just a way of using more processors without spending as much.

Coming Home to Vim 16 years ago

I tried your test, and was slightly faster at doing it vim than gedit (assuming my fingers were on the keyboard to begin with). How exactly did you do it in vim? I used the following:

y4j5jp -- yank down to 4 lines, move down to the blank line, paste after it.

I appreciate that there's an awful lot to learn before you can edit quickly in vim, and that the difference (if any) between that and gedit(or any other editor) may not be worth it.

I prefer vim for reasons other than speed, though -- the composable commands "feel" right to me, and the macro system makes short work of repetitive tasks. I'm essentially making lots of small programs to write the larger program for me.