Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chromatic
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
91.
▲
by
chromatic
11y ago
Hm. Your opinions don't match my recollections. Aaaaaand without the technical or political fallout of "let's make a VM for ALL the dynamic languages!" I remember Larry being really keen on that idea. The quote went so
92.
▲
by
chromatic
11y ago
While it may be technically true that "Perl 6.0 released!" is an accurate headline if you define "Perl 6.0" as "the test suite for the 6.0 language version", I suspect that almost everyone reading that headline
93.
▲
by
chromatic
11y ago
Don't have to wait for MoarVM - the folks at MoarVM didn't wait for Parrot to solve their problems (or they'd still be waiting). This historical revisionism continues to be tiresome.
94.
▲
by
chromatic
11y ago
How are we to trust that Rakudo won't go the way of Pugs, or that MoarVM won't go the way of Parrot, leaving us in a lurch? Some people will tell you to trust them. I, on the other hand, base my expectations on the history of th
95.
▲
Denormaliza Data at Business Boundaries
(outspeaking.com)
1 points
by
chromatic
11y ago
|
0 comments
96.
▲
by
chromatic
11y ago
Users.
97.
▲
by
chromatic
12y ago
For another dollop of irony the leading current P6 attacker was once the leading P6 booster around 2010. When he was pro P6 he didn't accept suggestions that it was slower than dog slow. (It was.) Now he's anti P6 he doesn't
98.
▲
by
chromatic
12y ago
I remember that conversation. The lead developer of the project had C# and Java experience and had already written his prototypes there.
99.
▲
by
chromatic
12y ago
Please stop pretending that starting a project to build a better Perl somehow killed the camel. It's easy to look at the rate of change and the timeline of releases of Perl after 2000. It's easy for me to argue that the announce
100.
▲
by
chromatic
12y ago
So what if Perl 6 people stalled on giving the okay for Parrot to migrate some implementation details to Parrot? My problem is that this gets argued both ways. This thread is far too nested anyhow, but here's my complaint. Yes, Parro
101.
▲
by
chromatic
12y ago
Yes, that's the link I mispasted. Thank you. What whiteknight didn't say was he'd spent over a year volunteering to port 6model to Parrot and had been repeatedly rebuffed. (He's a much nicer person than I am.) You can fi
102.
▲
by
chromatic
12y ago
I wrote my experiences with Parrot in specific: http://www.modernperlbooks.com/mt/2013/02/goodnight-parrot.h... I did not write but agree with this view of the Parrot Foundation: http://whiteknight
103.
▲
by
chromatic
12y ago
I believe some of the "historical baggage" lumped on Parrot and, by extension, its developers came from deliberate design and project decisions of the Rakudo developers. I'm happy to lay out what I believe the Parrot team did
104.
▲
by
chromatic
12y ago
After the first Rakudo Star release, I personally volunteered to spend my Parrot time fixing bugs which affected Rakudo, improving the performance of Rakudo, and adding features for Rakudo, in that order. I offered several suggestions (incl
105.
▲
by
chromatic
12y ago
Perl 6 hasn't even had its "Show HN: flappy bird/blog platform/etc" flavor-of-the-month phase yet, and you still claim its too late for the language? After almost 15 years in development, surely that lack should i
106.
▲
by
chromatic
12y ago
I just wanted to touch upon how Perl 6 offers many of these things. Sure, but in the world where I write software, my teams need code with a working ecosystem of documentation, tooling, libraries, trained or trainable developers, deployme
107.
▲
by
chromatic
12y ago
Mostly that MoarVM developers could learn from all of Parrot's successes and mistakes, while not carrying any of the historical baggage. I think you're being uncharitable. It's clear enough in retrospect that plenty of Raku
108.
▲
by
chromatic
12y ago
you go to code with the developer resources you have, not the developer resources you might want or wish to have at a later time Ha! My experience with Rakudo was "you go to the developer resources you have, tell them not to change a
109.
▲
by
chromatic
12y ago
But that's too late now.... Come now; that was the excuse given five and ten years ago. the "Perl" brand is still very strong Some would argue (including the post to which you're replying) that the brand is much less
110.
▲
by
chromatic
12y ago
I've already written about that at length several times here and elsewhere.
111.
▲
by
chromatic
12y ago
You say potato, I say "Parrot was designed to implement the semantics of both Perl 5 and Rakudo in the same process." You say "It's better to build a specialized VM", I say "Emscripten, Clojure, Niecza, Truffle
112.
▲
by
chromatic
12y ago
If I'm writing a code base that will likely have a >5 year life ... then don't write it in a language with negligible documentation, negligible tooling, barely-there library support, nearly zero users, and a roadmap based on
113.
▲
by
chromatic
12y ago
I'm interested in why you removed "stagnate and die" from that quote. I have strong opinions that people in situations similar to mine had no intent of contributing to "stagnation" or "death". Quite the
114.
▲
by
chromatic
12y ago
Have you been checking it out at all again, or are you considering it? No. I have my doubts about yet another announcement and nothing I've seen since I stopped contributing suggests that the project will provide anything I need that
115.
▲
by
chromatic
12y ago
This original announcement, which said "18 to 24 months, with a prerelease targeted for [July 2001]"? http://use.perl.org/use.perl.org/articled5d3.html?sid=00/07/...
116.
▲
by
chromatic
12y ago
some people would rather ... complain from the peanut gallery than they would help it move forward. That's not entirely fair. Some of us doubters spent a lot of time, energy, and resources trying to help it move forward before decidi
117.
▲
by
chromatic
12y ago
Modern scripting languages with... parametric polymorphism, built-in parallelism/concurrency, grammars, constraint-based multiple dispatch, etc.? Not everyone thinks that ticking off a list of feature checkboxes satisfies the most im
118.
▲
by
chromatic
12y ago
I think even PHP is more sane here. I'm not sure how an appeal to PHP as lowest-common-denominator of language sanity argues against understanding the return values of functions you call.
119.
▲
by
chromatic
12y ago
they've never committed to a deadline Baloney.
120.
▲
by
chromatic
12y ago
Except maybe that's actually a thing in perl, to use this behaviour as a feature, I don't know. Yes, that's common. List processing via variadic arity functions is an explicit feature of Perl.
More ›