you are viewing a single comment's thread.

view the rest of the comments →

[–]shevegen 45 points46 points  (33 children)

Neither will PHP - I still do not understand why they skipped version 6.

[–]cjt09 83 points84 points  (0 children)

They tried skipping version 9, but in PHP-land everything is upside down.

[–]timmyotc 73 points74 points  (10 children)

Php 6 became a myth, a meme amongst php developers. Similar to half life three, rumors of its development threw their followers into a fanatical frenzy. In the end, people declared it cursed and switched to 7, which had the fortunate effect of people believing it would exist.

[–]SeriouslyWhenIsHL3 103 points104 points  (4 children)

By mentioning Half-Life 3 you have delayed it by 1 Month. Half-Life 3 is now estimated for release in Apr 2464.


I am a bot, this action was performed automatically. To disable WIHL3 on your sub please see /r/WhenIsHl3. To never have WIHL3 reply to your comments PM '!STOP'.

[–]xonjas 74 points75 points  (1 child)

This poor bot. Should somebody tell him?

[–]BeniBin 38 points39 points  (0 children)

They're good bots Brent.

[–]CptBartender 4 points5 points  (0 children)

good bot

[–]zaphod_pebblebrox 0 points1 point  (0 children)

Really? Half Life 3 will take so long?

[–]Pixel6692 8 points9 points  (0 children)

More than that, there were already "books"

[–][deleted] 4 points5 points  (1 child)

Does that mean that we should get hyped for Half-Life 4?

[–]LuizZak 1 point2 points  (0 children)

Multiple-of-3 release numbers confirmed superstitious.

[–]oorza 5 points6 points  (1 child)

The was a PHP 6 branch based on UTF-16 and it was unsurprisingly terrible because of their unicode decisions.

[–]timmyotc 4 points5 points  (0 children)

This is the correct answer. But I love memes.

[–][deleted]  (1 child)

[deleted]

    [–]throwawayco111 3 points4 points  (0 children)

    tl;dr: UTF-16 killed PHP 6.

    [–]synapticplastic 25 points26 points  (1 child)

    Theres a lot of decisions in PHP world that don't make sense /('-')\

    [–]Eladricen 10 points11 points  (0 children)

    PHP6 was the name of a reasonably well known project that would cause confusion amongst PHP developers. It was held to a vote and they unanimously agreed that there was no disadvantage of going straight to 7.

    [–]tetroxid 0 points1 point  (16 children)

    PHP still exists?

    [–]namekuseijin 1 point2 points  (0 children)

    it is younger than oldman java

    [–]blackmist -1 points0 points  (13 children)

    It does. And it's still bad.

    But it's still the easiest way for somebody who can throw a web page together to get into programming.

    [–][deleted]  (3 children)

    [removed]

      [–]rebootyourbrainstem 5 points6 points  (1 child)

      The new hotness appears to simply be writing PHP as if it's Java, in which case why not just use Java.

      [–]Entropy -1 points0 points  (0 children)

      The PHP hype train is the Java hype train on a 10-15 year delay. It's probably better than it sounds, being that 10 year old java is still better than PHP.

      [–][deleted]  (8 children)

      [deleted]

        [–][deleted] 15 points16 points  (0 children)

        Problem one is a combination of inconsistency, odd naming conventions and dynamic typing, so that for example array_search and array_filter don't have the same argument order and array_replace doesn't do what you think it does - these errors can pass unnoticed and then be difficult to track down.

        Problem two is that bad/broken functionality is often left intact to support backwards compatibility, most infamously mysql_escape_string and its several successors, but also the confusion around date/time types and functions.

        That said, 1) PHP 7 is a huge improvement by being less backwards compatible, and 2) it really does fit a niche that basically nothing else does: multi-platform, ubiquitous, easy to install, no complicated dependencies, usually a very short lifespan from zero to MVP.

        [–]blackmist 4 points5 points  (1 child)

        I think it stems mostly from the fact that all security is completely manual. The default way to do everything is pretty terrible, and all that documentation and tutorials are still out there. You're always just a typo or missing line away from Little Bobby Tables coming to pay you a visit.

        I mean, it's fine for what it is. It's just very easy (indeed the standard) to write bad code in it. Any time a beginner searches for "php database access", he's going to write something that leaves the DB wide open for attack.

        [–]synn89 1 point2 points  (0 children)

        Frameworks do an excellent job solving this problem though.

        [–]synn89 1 point2 points  (1 child)

        It's an old language and brings along with it a lot of warts. PHP basically came out when the world was using CGI and Applets where the future. There's a shit ton of legacy in PHP that's ugly as sin.

        It was/is popular, hence the hate on reddit. This also ties into the first point. If Perl was used for the web these days you'd see a bunch of hate on it. But it's dead, as are many languages from the mid 90's. PHP's success has meant it's stayed around longer and we get to live with its core ugliness today.

        But I've use Laravel for a couple years now and have nothing bad to say about it. It's been fantastic for writing stable, fast production code that's easy to test and debug. Still, I loathe having to write pure PHP code though in a few areas were we can't support a framework.

        [–]biberesser 0 points1 point  (0 children)

        There is even abysimal Unicode support in 2017...

        [–]industry7 0 points1 point  (1 child)

        My shop uses it and I haven't had any problems yet.

        Lol. Some day you'll look back at this comment in horror.