News for hackers. Stuff that matters.
Re:Comparing the PHP 7 and Hack Type Systems by TazeTSchnitzel on Sunday April 26, 2015 @09:27PM (#9443987)
Yes, and as the person who came up with that, I was well aware of the irony. It was originally this:

  declare(strict_typehints=TRUE);
However, I changed it to the form that you see there because it was shorter. I felt that in the grand scheme of things it's not very important: declare() isn't a function, it's a language construct, and saving 5 chars from something that'll be typed very frequently is probably worth it.
Re:Comparing the PHP 7 and Hack Type Systems by mirashii on Sunday April 26, 2015 @09:50PM (#9444042)
> saving 5 chars from something that'll be typed very frequently is probably worth it.

This mindset is something that I've personally seen uniquely permeate every layer of the PHP community, more than anywhere else. I'm honestly curious, what makes communities seem to value things like typing less characters over clarity and correctness? The most important thing to me is reducing the amount of mental state needed for a human to read any line of code.

Re:Comparing the PHP 7 and Hack Type Systems by echaozh on Monday April 27, 2015 @01:18AM (#9444486)
Because PHP is for really fast development, and not for slow movers who actually think a lot. That's what I sense after joining a company using PHP.

The language itself feels like a bag of features copied over from top contenders from the TIOBE index. You can see the fastness in the core of the language design.

After all, you use PHP to perform MySQL queries in the middle of HTML tags. If you want to do this, you know some principles are merely burden for your smooth execution of the web site development, and should be throw out the window at first thought.

Re:Comparing the PHP 7 and Hack Type Systems by stephenr on Monday April 27, 2015 @02:22AM (#9444628)
Just because you can do something doesn't mean you should

The sort of approach you're describing is not suggested or used by anyone with half a clue what they're doing.

Re:Comparing the PHP 7 and Hack Type Systems by slapresta on Monday April 27, 2015 @03:12PM (#9448495)
Indeed, no one with half a clue what they're doing uses PHP.
Re:Comparing the PHP 7 and Hack Type Systems by giaour on Monday April 27, 2015 @10:33AM (#9446526)
We program so hard we don't have time to think. Or type. At least not with as many characters as a sane person would.
Re:Comparing the PHP 7 and Hack Type Systems by TazeTSchnitzel on Monday April 27, 2015 @07:34AM (#9445549)
In this case I don't think it sacrifices much clarity, and it avoids the word "typehint" which is controversial (correctness is disputed). Using TRUE wouldn't necessarily be more correct, it's fairly arbitrary.
Re:Comparing the PHP 7 and Hack Type Systems by ars on Sunday April 26, 2015 @10:52PM (#9444183)
I sort of wish you had done:

  declare(types=strict);
instead. That way other options can be added in the future.
Re:Comparing the PHP 7 and Hack Type Systems by TazeTSchnitzel on Monday April 27, 2015 @07:33AM (#9445547)
Not syntactically legal, unless it's special-cased or we unusually make a lowercase constant for that purpose. declare() takes a constant value.

Well, it could've been this:

    declare(types="strict");
Alas, we are beyond feature-freeze now. Also, I quit PHP development.
Re:Comparing the PHP 7 and Hack Type Systems by giaour on Monday April 27, 2015 @10:37AM (#9446560)
I believe there was some discussion of using the same strict declaration as javascript ('use "strict";'), but there's already an "easter egg" in PHP that causes your program to exit and prints out something like "I think you're using the wrong language."

For some reason, this Easter egg was deemed too important to displace with an actual language construct.

Re:Comparing the PHP 7 and Hack Type Systems by TazeTSchnitzel on Wednesday April 29, 2015 @01:52PM (#9460217)
Well, there's also the fact that something that changes the language behaviour really should be a pragma and not a magic import statement.
Re:Comparing the PHP 7 and Hack Type Systems by stephenr on Monday April 27, 2015 @05:16AM (#9445136)
i quite like this concept too, but both are still better than Hack's

    <?hh // strict
Strict what?
Re:Comparing the PHP 7 and Hack Type Systems by TazeTSchnitzel on Monday April 27, 2015 @07:34AM (#9445552)
Hack's is a comment, not a proper pragma, too.
Re:Comparing the PHP 7 and Hack Type Systems by stephenr on Monday April 27, 2015 @07:51AM (#9445599)
Yeah that's kinda sucky too. I assume it's because they also support their "strict" mode with regular php files?
Re:Comparing the PHP 7 and Hack Type Systems by BringTheTanks on Monday April 27, 2015 @09:19AM (#9446030)
Well, there are non-ironic alternatives:

    declare(strict_typehints=TRUE); // not ironic, not short
    declare(strict_types=1); // ironic, short
    declare(strict=true); // not ironic, even shorter
JS has one strict mode, this could've been an opportunity to introduce an umbrella mode for strict coding in general.

Also the declare syntax could've been augmented to support passing implicit boolean parameters without setting a value:

    declare(strict); // oh yeah.
So... you know. Not that it matters what you call it, but choosing ugly (and ironic) over pretty (and sane) shouldn't be taken so lightly.
Re:Comparing the PHP 7 and Hack Type Systems by giaour on Sunday April 26, 2015 @11:54PM (#9444313)
As someone who will be typing it very frequently, I wish the more verbose and obvious version had won out.