1. Scheduled to come out in Q4 2015
2. <=> operator, see https://wiki.php.net/rfc/combined-comparison-operator
3. Return Type Declarations & Scalar Type Hints
4. Speed improvements (25-70%)
5. Yep, speed improvements are for real.
You're welcome.
Which won't happen, I can tell you. PHP's release dates always slip by at least a month, and that's without a very unstable master branch like PHP 7 has.
If it does happen, it'll take a few micro (7.0.x) releases until it reaches stability.
> 3. Return Type Declarations & Scalar Type Hints
Also strict scalar typing:
<?php
declare(strict_types=1);
sin(false); // error
strlen(2); // error
-- disclaimer: I am a former PHP internals developer
Umm, well I saw Zeev has voted in favor of scalar type hints on the RFC?
... 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 :-)
Shared Hosting needs to die off anyway.
You could say the exact same thing about VPS servers compared to dedicated hosting and be equally wrong. Please accept that there are different use cases that come with different solutions, of which shared hosting is one.
I work for a shared/dedicated hoster, we're geared price-wise at the higher end of the market and we provide shared hosting for our business customers.
Our shared environments are closely monitored and never oversubscribed. We're constantly looking out for customer sites that misbehave and shut down those that are resource hogs or service affecting.
We have loads of customers running the internet facing parts of their businesses on shared.
Shared hosting, like all other things, is a case of "you get what you paid for".
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.
Edit: it was RH7, not RH5. Just checked. Still bad.
Shared Hosting has many downsides, but it still fills an incredibly important niche for businesses for whom a web presence beyond a Facebook page is needed but real managed hosting is completely out of their price range.
DO of course have a Wordpress appliance which makes it pretty easy to set up, if you can manage Wordpress you can do it, so long as you're not concerned with getting in to the details of security of your droplet. It's probably no less secure than a lot of virtual hosting arrangements with 777 access on content folders and such.
[If anyone wants a free $10 credit for DO then feel free to message me.]
>"You represent and warrant that you either own or have permission to use all of the material in your Emails." //
Fair use isn't permission, nor ownership, it is statutory right of use though.
They bring in Spamhaus' definition of spam too, which on first reading appears to be self-contradictory - requiring each message sent to be explicitly requested. Taken by the letter this would mean I couldn't, for example, send out a message to a group of customers with whom I had a standing relationship to let them know of a change to terms & conditions, for example, without explicit consent. That means anticipating every email. Catchall phrases like "agree to receive all email" wouldn't work as the customer "has not verifiably granted deliberate, explicit, and still-revocable permission for it to be sent".
Indeed "still-revocable" permission means that as soon as a mass email is sent it becomes spam regardless, it's no longer revocable. There are other problems too - verifiable opt in means an alternate system needs to be used for the verification emails.
In turn that means that any email I send to multiple recipients puts me in breech of Mandrill's T&Cs.
Mandrill have a circular reference from the Terms "You retain ownership of the materials you upload to the Service. We may use or disclose your materials only as we describe in these Terms and our Privacy Policy." and in the Privacy Policy:
>"Information You Provide to Us: When you register to use the Services, communicate with our customer service team, send us an email, or post on our blog, you’re giving us information that we collect. That information may include your IP address, name, physical address, email address, phone number, credit card information, and other details like gender, occupation, and other demographic information. By giving us this information, you consent to your information being collected, used, disclosed, and stored by us, only as described in our Terms of Use and Privacy Policy."
In short the policies allow them to harvest data from emails sent with the service and to use it as they wish. They go as far as to intimate that because they do use the message data internally that the service is not for personal email. There's also a clause Terms 5.f that allows doxing and combining the info with your account data.
The "protections" for selling of your info with the business don't work as there are standard "we can alter this agreement unilaterally" conditions.
tl;dr law - it's complicated. This service is absolutely not for "personal" emails however.
Sensitive emails contravene the T&C; I think those examples would be included in that definition.
This is like saying "Bicycles need to die out." just because you never ride one.
Disclaimer: I work for a web hosting company.
It tends to be a classic case of blaming the tools for the actions of the people using them.
For example, people track link clicks in a web app and they do it with Google analytics. If not handled correctly, it will break all the navigation on a page.
Seems like the only new feature are type hints. Looks like Hack has been rebranded as PHP 7.
The speed boost is due to massive engine changes and internal refactoring.