"You can put lipstick on a pig but it's still a pig"
- Barack Obama on PHP in 2008
Things you should know about PHP 7
11–20 of 124 posts
Re: Things you should know about PHP 7
#12Earlier quoted context omitted.
>... and available on general cheap webhosting sometime around 2020. If we're lucky. Shared Hosting needs to die off anyway.
Why?
The security implications and unpredictable resource availability never made it feasible to run a real production site from shared hosting.
Re: Things you should know about PHP 7
#13Seeing this:
> function add( ... ): float {}
I think a much better choice would have been:
> float function add( ... ) {}
Or just:
> float add( ... ) {}
Since that's how it's done in other languages and people would feel at home with it.
Re: Things you should know about PHP 7
#14Good to see PHP slowly improving, although I haven't used it for years now. On a side note, does anyone know why Drupal 8 is apparently so absurdly slow? I know it's not entirely fair to compare against D7 as it's still technically "under development" but it just seems insane to take that much of a performance hit for nicer OOP semantics...
I'd say it's to do with having been rebuilt with Symfony components. That's not to say symfony is, by necessity, slow, but I going to guess that completeness and stability was first for such a big change before performance. But... that's just a guess.
I think it is exactly the fact that they are using Symfony components. Symfony and a lot of other PHP frameworks went head first into the non-sensical enterprise Java abstraction and IoC hell from 10-15 years ago that current Java developers are running as fast as they can from. That overhead comes at a cost.
Re: Things you should know about PHP 7
#15Earlier quoted context omitted.
> 1. Scheduled to come out in Q4 2015 ... and available on general cheap webhosting sometime around 2020. If we're lucky. Thank god our company slowly moved away from building small PHP websites that have to run on the most fucked up PHP installations from the before-time. Now it's PHP 5.6+ everywhere :-)
>... and available on general cheap webhosting sometime around 2020. If we're lucky. Shared Hosting needs to die off anyway.
Shared hosting does mean that your provider is likely keeping their platform patched and up to date, which is possibly painful for you but likely nice for everyone else.
The alternatives seem to be giving customers a VM or a dedicated server which tends to mean it's _never_ going to get any security updates since the day it was first set up.
Shared hosting is a pain, but the alternatives have the potential for even more pain.
Re: Things you should know about PHP 7
#16Seeing this: > function add( ... ): float {} I think a much better choice would have been: > float function add( ... ) {} Or just: > float add( ... ) {} Since that's how it's done in other languages and people would feel at home with it.
Haxe uses the first syntax, as does AS3. So it's not like "other languages" are universally opposed to this order.
Re: Things you should know about PHP 7
#17Good to see PHP slowly improving, although I haven't used it for years now. On a side note, does anyone know why Drupal 8 is apparently so absurdly slow? I know it's not entirely fair to compare against D7 as it's still technically "under development" but it just seems insane to take that much of a performance hit for nicer OOP semantics...
D8's a work in progress, and if there's one thing I wouldn't be too critical of a wip for, it's performance.
Frankly I don't really see drupal's place in the world anymore. It's so absurdly config-heavy, which may have made sense a decade ago but not now. Everyone will just install composer, put laravel/symfony on there, and be off to the races. The era of giant pages of drupal-managed plugins is over, and replaced by package managers + slimmer CMSes like joomla or concrete5.
Re: Things you should know about PHP 7
#18Heck, I'm kinda felling bad as a Pythonista. We're lagging badly speed wise.
Sure, there's PyPy but it's not compatible with the mainstream C-Extensions so pretty much a no-go for most of my projects. Hopefully Piston will come to rescue in the future.
Re: Things you should know about PHP 7
#19Seeing this: > function add( ... ): float {} I think a much better choice would have been: > float function add( ... ) {} Or just: > float add( ... ) {} Since that's how it's done in other languages and people would feel at home with it.
Swift?
Re: Things you should know about PHP 7
#20Good to see PHP slowly improving, although I haven't used it for years now. On a side note, does anyone know why Drupal 8 is apparently so absurdly slow? I know it's not entirely fair to compare against D7 as it's still technically "under development" but it just seems insane to take that much of a performance hit for nicer OOP semantics...
Because it hasn't begun speed improvements yet. Basically once everything is "done", everyone will optimise it to run faster.
There are lots of improvements going in to make it 'fast by default'.