tef posted:

'we don't write cgi-scripts any more'

tef posted:

Janin posted:

speak for yourself

The Reaganomicon posted:

Reminds me of Javascript's if([0]&&[0]==false)

Munkeymon posted:

What would you expect the logical and of two arrays to be?

Munkeymon posted:

What would you expect the logical and of two arrays to be?

tef posted:

I gave half a talk on php last night to a local techie startup group - the first half was a php apologist - my talk wasn't so flattering: 'php: a great way to write cgi scripts' and 'we don't write cgi-scripts any more'

anyway Otto came up with this slide and I figured I'd post it here

Xenogenesis posted:

OT: I present beautiful handwritten SQL for a small Rails app:

code:

      query = %Q{
        SELECT DISTINCT ON (s.user_id, s.chart_id) s.*
          FROM scores AS s
          JOIN charts AS c
            ON (c.id = s.chart_id)
            #{chart ?
            "WHERE c.id = ?" :
            "WHERE c.key_id = ?
              AND c.game_id = ?"
            }
        AND s.id IN (
          SELECT s2.id
          FROM scores AS s2
          LEFT JOIN scores AS s3
            ON (s2.chart_id = s3.chart_id
                AND s2.user_id = s3.user_id
                AND s2.judgement < s3.judgement)
          WHERE s2.chart_id = s.chart_id
            AND s3.judgement IS NULL
          ORDER BY s2.judgement, s2.score DESC
          #{"LIMIT ?" unless limit.nil?})
        ORDER BY s.user_id, s.chart_id, s.judgement, s.score DESC
      }

NotShadowStar posted:

Holy balls I noticed that 0 == "" and 0 == null in PHP. Also "string" == 0 in PHP.

This is literally the worst thing created. At least Perl has some hosed up logic behind it's typeless crazytown. img-php.png indeed.

The Reaganomicon posted:

I would expect it to be consistent. a&&b is true iff both a and b are true. [0]&&[0] is false, thus [0] must be false. But if([0]) is true.



As an aside, I understand where this comes from, but holy poo poo Boole is spinnin' in he grave.

king_kilr posted:

I'd expect an array, in a boolean context, to evaluate as bool(array.length). Javascript has this lovely thing where one item arrays are equivalent to array[0].

NotShadowStar posted:

Holy balls I noticed that 0 == "" and 0 == null in PHP. Also "string" == 0 in PHP.

This is literally the worst thing created. At least Perl has some hosed up logic behind it's typeless crazytown. img-php.png indeed.

McGlockenshire posted:

code:

[mcg@mcg-workstation ~]$ php --interactive
Interactive shell

php > var_export( "string" == 0 ); // Strings are numeric zero.
true
php > var_export( (bool)"string" ); // Strings are boolean true.
true
php > var_export( true == 0 ); // Boolean true is not zreo.
false
php > echo PHP_VERSION;
5.3.3

I hate PHP so, so much.

Munkeymon posted:

Also:

code:

[0] == [0] //false

Hammerite posted:

The whole "omg PHP type-juggling" thing is a bit of a dead horse isn't it? Yeah it's not always terribly consistent, it's meant to allow you to Get poo poo Done quickly. It's not necessarily optimised for that, but it doesn't do too badly. It does give you ways to compare things carefully when you need to do so.

tef posted:

You are claiming to be a painter but all you do is cover walls in your own faeces because you can't get the paint cans open.

Hammerite posted:

If you want to slate PHP, I can think of at least 10 things that are more worthy of criticism than type-juggling.

Hammerite posted:

If you want to slate PHP, I can think of at least 10 things that are more worthy of criticism than type-juggling.

tef posted:

php handles writing cgi scripts but doesn't handle any of the features of a modern web application

quote:

Also, PHP (as far as I know) can't be used to write CGI pages; it depends on an Apache/nginx/whatever module that runs the scripts themselves. I suppose you could write a CGI page using the PHP interpreter, but that's even worse than just plain ol' php

Otto Skorzeny posted:

How'd the talk go btw tef? Also I will read the dns thing you wrote up when I get the chance, probably this weekend (doing interview prep for a Real Engineering(tm) opportunity atm)

Janin posted:

that's the second time you've dissed cgi, and I'mma let you continue, but PHP is the worst horror of all time

Finally, CGI can do everything a modern "web application" (I hate that loving marketing phrase) can; its only disadvantage is performance, and that's solved easily by using FastCGI

Nevett posted:

Not sure why this is confusing. Surely its just creating two separate arrays and comparing them by reference.

quote:

Javascript has this lovely thing where one item arrays are equivalent to array[0].

nielsm posted:

From 2 pages ago, but I had to comment on this.


Seriously.

What is that subquery supposed to be doing at all? The join in it being a no-op doesn't exactly help.

Join on (blah and foo < s3.judgement).
Where s3.judgement is null.

NotShadowStar posted:

Holy balls I noticed that 0 == "" and 0 == null in PHP. Also "string" == 0 in PHP.

This is literally the worst thing created. At least Perl has some hosed up logic behind it's typeless crazytown. img-php.png indeed.

HappyHippo posted:

So transitivity is apparently not a property of the == operator.

quote:

We have equality operators. Unfortunately they do type coercion, and they do type coercion before they compare things for equality, and that coercion can cause false positives, which is a bad thing. So I recommend to always use the triple equal operator instead, which is unfortunate, because it’s uglier, but you have to. The reason for that is… Try to find the pattern in here. There’s no transitivity at all. Transitivity says that if A and B are equal, and B and C are equal, then A and C should be equal, but they’re not. Again, we’ve got these mathematical absurdities going on where transitivity doesn’t hold, and it should. My expectation is that all of these should produce false, because in every case what’s on the left side is different than what’s on the right side. With the triple equal operator, it does the right thing; you actually get false in all the cases. So I recommend that you always, always use the triple equal operator. There might be times when you think you want the type coercion, but you should only do that if you actually understand what the type coercion will do, and I challenge anybody looking at this to guess what the conventions are.

Easy Mac posted:

Sounds like php is terrible and should never be used. What is the ultimate language to use for the web.

Mr. Wynand posted:

LISP MOTHERFUCKER THE ANSWER IS ALWAYS LISP

Xenogenesis posted:

Hahaha, you wish that join was useless.

nielsm posted:

Also PHP is fine to use as long as you know why it sucks. Its design still makes more sense than mIRC Script.

nielsm posted:

Also PHP is fine to use as long as you know why it sucks. Its design still makes more sense than mIRC Script.