Re^2: Perl 6 release dates - two years later
by Elian (Parson) on Oct 21, 2004 at 15:23 UTC
|
...because Perl 6 should have been released...
Let me put on my cranky implementor hat here. The only people who can legitimately say that perl 6 should be doing anything, or be released at any time, are the ones who've actively done work on it. (So I can say should. And will)
If you've not done anything or, worse, been actively involved on perl6-language (a festering swamp that holds, no joke, a high place in the list of things that have delayed perl 6 (second only to the various lord of the rings DVDs)), you're just watching. People watching don't get shoulds. "Would be nice", "looks like opportunity X", "pity I've gotta move on to something else", sure. But not should. Should is for the people doing things, not the people watching.
| [reply] |
|
Also note, as I'm being cranky, that if you have contributed to the development in non-development ways (that is, contributed money to the perl foundation for perl 6 development, done sysadmin or other infrastructure support for perl 6) you've definitely got good reason to ask "What the hell's going on?" (Though that is, certainly, a different thing to ask)
| [reply] |
|
| [reply] |
|
Let me put on my cranky implementor hat here.
Not a good idea, probably. The cranky hat doesn't look well with my ";)".
The "should" referred to my previous estimate, not to any reality. To clarify it further: in order for me to "win" my own "contest", it "should" have been released over a year ago.
I agree with most of what you say, am semi-active on perl6-language (oops, sorry), and donated to the fund (and plan on doing so again, repeatedly once every year, if I can afford it). I actively discuss Perl 6 on several fora and in general am very positive. I agree with the "released when ready" idea and prefer years of waiting to having a horribly implemented language. I may not agree with every decision made (things bothering me are unicodenon-ASCII operators, confusing use of the colon, overuse of the new french quoty qw, \d**{} and arbitrary limits like do-while), but I think Perl 6 is a really cool language. I do not mind that it is not released yet for I understand that quality takes time, and that implementation with an unfinished design leads to chaos.
Please, get rid of the cranky hat and re-read my post. This time, pay more attention to the ";)" and read the entire thread in the appropriate context: fun speculation. Or buy me a cranky head too, so that I can start a troll/flame war. It would be about something else, though, because debate is HARD when you actually agree with one another.
| [reply] |
Re^2: Perl 6 release dates - two years later
by Anonymous Monk on Oct 21, 2004 at 16:00 UTC
|
Next time, can you please close those tr and td tags?
The tags are closed, but I presume you mean the elements aren't closed. However, closing those elements is not needed. From the HTML 4.01 spec:
<!ELEMENT TR - O (TH|TD)+ -- table row -->
<!ELEMENT (TH|TD) - O (%flow;)* -- table header cell, table dat
+a cell-->
If I liked to type in more keystrokes than necessary, I'd be programming in Java instead of Perl. If you have broken software that can't deal elements that aren't closed, complain to your vendor. | [reply] [d/l] |
|
The XHTML spec says they have to be closed (or use an empty tag, like <td />, but I generally only use that for tags like <hr /> that don't have any data associated with them). Properly balanced tags make things much easier to parse.
"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.
| [reply] [d/l] [select] |
|
$ HEAD 'http://www.perlmonks.org/index.pl?node_id=401092'
200 OK
Connection: close
Date: Thu, 21 Oct 2004 22:42:03 GMT
Server: Apache/1.3.27
Content-Type: text/html; charset=ISO-8859-1
Client-Date: Thu, 21 Oct 2004 22:42:07 GMT
Client-Peer: 209.197.123.153:80
Client-Response-Num: 1
Note the Content-Type. It says text/html, not text/xhtml.
| [reply] [d/l] |
|
|
|
| [reply] |