Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PHP 5.5

github.com

Post reply on HN
Print view View original

51–60 of 112 posts

Re: PHP 5.5

#51

Post by bpicolo »

TheAnimus wrote: post #41
kmage wrote: post #37

Earlier quoted context omitted.

> I think PHP really does need to try and clean up its image. Sorry, but you obviously have not been taking notice over the past year or two. PHP really has been cleaning up its image. Go have a look at PHP-FIG, composer and packagist for starters. Yes, there are problems. Yes, some/most may think that there are better solutions. But to think that PHP has not been "cleaning up its image" is just wrong.

>Sorry, but you obviously have not been taking notice over the past year or two. I'll admit, I haven't really, because I'll turn it round, why would I? We've seen Erlang start to be used quite a lot, Scala is becoming very interesting, and F# is appearing suitably mainstreme. What features would make me think "hmm, I should check out what they are doing in PHP"? Looking now I still see a cluttered array of APIs, some…

My biggest problem with PHP is that I was never able to find a good framework for it. After I found Laravel I started liking it a lot more.

Re: PHP 5.5

#52

Post by RossM »

mgkimsal wrote: post #42
skrebbel wrote: post #21

Earlier quoted context omitted.

Yes. Removing stuff from a programming language has virtually no benefit and a huge real economic cost. That, of course, is under the assumption that the programming language has users. I could see them deprecating some stuff, and adding yet another E_EVEN_STRICTER level that tosses ugly notifications when deprecated things are done. That would be nice.

IIRC E_DEPRECATED notices are triggered when deprecated stuff is referenced. http://php.net/manual/en/errorfunc.constants.php E_DEPRECATED - Run-time notices. Enable this to receive warnings about code that will not work in future versions. (Since PHP 5.3.0)

Indeed; in fact this update issues an E_DEPRECATED warning when you attempt to connect to a MySQL database using the old MySQL extension.

Re: PHP 5.5

#53

Post by doppel »

dave1010uk wrote: post #6
thejosh wrote: post #3

Biggest change? - Drop Windows XP and 2003 support

Most interesting things for me: * PHP is getting the yield keyword (i.e. generators and coroutines), which many other languages have had for a while. * A sensible and simple built-in password hashing API * Error when using the deprecated mysql extension, which should hopefully get more people moving to PDO (e.g. WordPress: http://core.trac.wordpress.org/ticket/21663 )

For the last one, won't people just move to the mysqli_* function group instead? It's almost identical API-wise.

Re: PHP 5.5

#54

Post by RossM »

dkhenry wrote: post #49

And what I still don't see is anything saying they are taking their performance problems seriously. Still nothing saying they are fixing their documentation. Nothing addressing their hodgepodge of legacy code and mixed methods of implementing features. Its like their upset that people have moved on, but instead of providing a better core for people to build products on they keep adding chrome to the fringes of the la…

Out of interest, what do you find wrong with the documentation? I've always found it pretty comprehensive and relatively easy to navigate.

Re: PHP 5.5

#55

Post by juice13 »

dkhenry wrote: post #49

And what I still don't see is anything saying they are taking their performance problems seriously. Still nothing saying they are fixing their documentation. Nothing addressing their hodgepodge of legacy code and mixed methods of implementing features. Its like their upset that people have moved on, but instead of providing a better core for people to build products on they keep adding chrome to the fringes of the la…

5.3 and 5.4 had significant performance increases. 5.5 has integrated opcode cache. IMO, PHP has one of the best documentations of any programming language. Many bad bits have been deprecated in recent versions and there are PSR recommendations which make it easier to write decent interoperable code. PHP is growing up.

However, if you don't like it, nobody's forcing you to use it. Just walk away.

Re: PHP 5.5

#56

Post by dcc1 »

juice13 wrote: post #55
dkhenry wrote: post #49

And what I still don't see is anything saying they are taking their performance problems seriously. Still nothing saying they are fixing their documentation. Nothing addressing their hodgepodge of legacy code and mixed methods of implementing features. Its like their upset that people have moved on, but instead of providing a better core for people to build products on they keep adding chrome to the fringes of the la…

5.3 and 5.4 had significant performance increases. 5.5 has integrated opcode cache. IMO, PHP has one of the best documentations of any programming language. Many bad bits have been deprecated in recent versions and there are PSR recommendations which make it easier to write decent interoperable code. PHP is growing up. However, if you don't like it, nobody's forcing you to use it. Just walk away.

This ^

I find the people doing the moaning about PHP are the noobs who are regurgitating what they read or heard elsewhere in order to appear smart, Having moved to PHP 10 years ago after C and Java and .NET development I am happy for having changed direction and have made a bootload of money and saved alot of time thanks to PHP over the years.

Re: PHP 5.5

#57

Post by anentropic »

BaconJuice wrote: post #50
coldtea wrote: post #44

Earlier quoted context omitted.

> I don't think this is a solution for everyone. No, but it's very much a solution for any HN developer in a Western country. He knows what to do (hence "HN") and the money are insignificant. I got a 512MB SSD VPS for $5/month from a major player. Similar plans exist all around. If $60/year is a "cost to you" and you are a developer in the US/Western Europe, then you're doing it wrong.

Mind sharing this $5 vps please? I'd like one.

Digital Ocean

Re: PHP 5.5

#58

Post by fotcorn »

BaconJuice wrote: post #50
coldtea wrote: post #44

Earlier quoted context omitted.

> I don't think this is a solution for everyone. No, but it's very much a solution for any HN developer in a Western country. He knows what to do (hence "HN") and the money are insignificant. I got a 512MB SSD VPS for $5/month from a major player. Similar plans exist all around. If $60/year is a "cost to you" and you are a developer in the US/Western Europe, then you're doing it wrong.

Mind sharing this $5 vps please? I'd like one.

It looks like Digital Ocean: https://www.digitalocean.com/pricing

Re: PHP 5.5

#59

Post by wildmXranat »

BaconJuice wrote: post #50
coldtea wrote: post #44

Earlier quoted context omitted.

> I don't think this is a solution for everyone. No, but it's very much a solution for any HN developer in a Western country. He knows what to do (hence "HN") and the money are insignificant. I got a 512MB SSD VPS for $5/month from a major player. Similar plans exist all around. If $60/year is a "cost to you" and you are a developer in the US/Western Europe, then you're doing it wrong.

Mind sharing this $5 vps please? I'd like one.

https://www.digitalocean.com/ is one .

Re: PHP 5.5

#60

Post by Zergy »

RossM wrote: post #54
dkhenry wrote: post #49

And what I still don't see is anything saying they are taking their performance problems seriously. Still nothing saying they are fixing their documentation. Nothing addressing their hodgepodge of legacy code and mixed methods of implementing features. Its like their upset that people have moved on, but instead of providing a better core for people to build products on they keep adding chrome to the fringes of the la…

Out of interest, what do you find wrong with the documentation? I've always found it pretty comprehensive and relatively easy to navigate.

I personally found it very incomplete. The comunit makes up for it but quite often there were large gaps exspecially regarding edge cases and details on how functions would behave if they failed. The comments did a really good job of filling in these gaps but the documentation alone was often inadiquate to understand how the code would behave.
Post reply on HN