>>54
That is a problem for using it today but I don't see how it's going to kill it in the end. JavaScript didn't exist when I started programming, yet I enjoy using it today.
I meant that when they're finished coming up with crackpot ideas people it'll be too little too late.
Junctions autothread and will dispatch individually in parallel where appropriate. What you say about them makes it obvious you don't know how they work underneath. I don't think they're very important (I don't blame you for not caring or knowing much about them), but the implementation is impressive.
I had a look at them before writing the post. The data structure as itself is kind of boring. The autothreading
is good, of course. There are similar efforts in the Haskell world (DPH). I wouldn't be surprised if there was some overlap there.
multiple implementations
Nothing wrong with that.
We'll see, I suppose. C and JS had the advantage of having inertia already. C was already popular before it had many implementations. JavaScript rode on the back of browsers which were already popular -- it's not like people had a choice to use it. Python, too, has had CPython for a long time. I don't know how long (and I need to get back to work) but I'm pretty sure it was (and still is) the main implementation for a while.
You didn't address the case of Common Lisp, a very old language, which has a standard spec, but which has the shittest implementations ever (though SBCL is getting fairly acceptable these days).
CPAN incentivizes conformity among implementations anyway. (One thing Perl taught the world: community as technology.)
That's a good point -- if it does. How does it do that? Hackage has helped the Haskell community bring its efforts to one place (as I expect Quicklisp will do for CL) but everyone pretty much targets GHC and if it works on Hugs or whatever else then that's nice. I'm with PG that a single implementation that is the default choice is better than an array of choices.
There's a means of loading Perl 5 modules
Doesn't sound great but I'll take your word for it.
Perl 6 has no traction or inertia, no one's using it yet, so how it will overcome the challenges above is a matter of "we'll see", I think.