frodwith

> Do you mind if I include your language on the experiments list?

Not at all! Thanks for the advice, and I'll take you up on the invitation to come chat before too long.

Hi, author of jaque here. I've been working on some other things for a little while, but I'll be getting back to jaque soon. It's quite out of date and needs to be brought up to 1.0 and cleaned up a bit before I start grousing about the stack issues I was running into on the mailing list, but when I last was working on it I was running into issues with Graal when trying to increase the java stack size. Deep but bounded head recursion is quite common in nock, and I seem to recall I needed about 8 megs of stack space (I just passed -Xss 8m or something on the command line) and Graal slowed waaaay down. That's where I left it.

I've recently realized that most of the enjoyment I derive from building things comes from the process (figuring out neat / new ways to do things, debugging, thinking). Shipping is a necessary tedium for me. Maybe people like me have more fun fiddling with the minutiae of our tools than actually "doing cool things".

No value judgment there, just an observation.

"There is no equivalent in any other language."

I don't know, LWP is pretty easy to use.

You'd probably need a lot more oomph to render even moderate resolutions of compressed video.

I didn't, but that's really good news :)

Chrome's killer feature for me is still process separation. Slow pages kill my entire browsing experience in firefox, and when I have 20+ tabs open, that can be really annoying.

My point isn't that there aren't competent replacements. Obviously the BSDs in general have different userlands, as does Solaris, and so forth. But those things -are- the userland on a Linux system.

If the point is supposed to be "why insist on calling it GNU/Linux when xx% of it isn't even produced by GNU?", it's an ill-made point. Most of the userland (and certainly what we could call the "core" userland, especially in terms of development tools) is GNU software. The system would be pretty unusable libc, gcc, ld, make, etc.

Dunno about you, but I know it because I did those things and now I'm fat. >_>

He tosses a few others languages out on very similar grounds. I confess to not finishing the article out of disgust after he did this several times.

In that case, use an ssh-agent and agent forwarding. Then you only need your private key on the box you're actually sitting at.

"It turns out that..."

You're either trolling or you haven't paid any real attention to the perl community. Your comments are simply inaccurate, which is probably why they were downvoted (not out of some weird fanboyism).

I'm really beginning to hate this terminology (virality). It just sounds retarded.

Right, because the SUCKERS like me who spend far less than they earn and keep their money in a savings account with the highest interest rate they can find (at essentially NO risk) were hurt so badly last time the economy crashed. Right?

I wrote a little libevent-based webserver (bush-league stuff) that embeds V8 to do its request handling over a weekend not too long ago. You could start doing this today with very little effort.

First class continuations in Javascript would be a godsend.

At least for me, usability isn't the point of free software. I want my free software to be usable, yes, and usability should be a goal for the development teams, but the overriding benefit of free software is that it is free. It puts the power back in my hands as an end user. Even if I don't have the technical skills to make use of that freedom, the freedom is important. This is something that "closed-source" applications don't have. If Microsoft made Office free tomorrow and it were easier to use than OpenOffice (it is, though that isn't saying much), I'd use it. But Microsoft Office has vendor lock-in problems and platform compatibility issues, and I'm not free to make it better. If people value usability over freedom, that is their choice. I don't begrudge them the headaches of a different sort that they are incurring.

Classic case of overengineering the problem. I'd venture that it's a common enough class of mistake for those who have recently learned the hip/new/cool way of doing a thing. Thing = scaling a webservice in this example.

I have wondered lately if living in the weird information landscape of modern communication isn't sucking the joy out of my life to some degree. I think next time I am unemployed, I'm going to take a few months and similarly pull the plug, just to see what it feels like.