The SitePoint PHP blog has a post to their site introducing SparkPost, an email delivery service (in the same vein as Mandrill) that you can hook into your PHP applications to prevent the need to run your own mail servers.
I’ve used Mandrill for as long as I can remember. It sends transactional email, like the kind you receive when you sign up for a new account. Like me, many have been happy to use a free account for sending a relatively low number of emails a month. That is, until recently, when Mandrill caused a bit of a stir. The heart of the matter is that Mandrill removed their free tier. Anybody wishing to send mail through Mandrill now requires a paid-for MailChimp account
[…] Mindful that people are looking for alternatives (to power their personal newsletters or whatever), I spoke to Aydrian Howard. Aydrian is the Developer Advocate at SparkPost, whom I met at FluentConf. We talked for a bit about SparkPost and what makes it different from MailChimp.
After the little bit of Q&A about the service, the tutorial gets in and shows you how to get SparkPost set up for your application. They help you install their own client library and send a first test email using your account. Code is provided showing the configuration of the client with your key and the options you can define when sending the message.
On the NetTuts.com site they’ve published a tutorial that explains Laravel packages – what they are and how you can create your own to seamlessly integrate with this popular framework.
As a PHP developer, you may be interested in working with frameworks. Frameworks attempt to make the process of development easier by simplifying common practices used in the majority of developing web projects such as packages, modules, plug-ins, and even components (CakePHP).
[…] There are two types of packages; some are framework independent (stand-alone) and the others are for a specific framework. This tutorial will exclusively cover Laravel packages.
They start with a look at what these packages are and how they integrate with the framework and your application. They also link to a few of the packages they’ve found useful in their development including an IDE helper and OAuth wrapper. With this knowledge in place the tutorial then gets into to creating your own packages, installable via Composer and using a Service Provider to set up configuration needs. The post ends with a look at integrating and enabling your package through the application configuration.
In this recent post to the /r/php subreddit on Reddit.com, the question is asked „what is the nature of PHP?“ and how it relates to what features make it into the language and which don’t.
I’ve heard many times that a proposed RFC/new feature got rejected by PHP internals in voting phase, since ‚it does not fit the nature of PHP‘. But the question is, what is PHP’s nature? Does it even have a nature at all? If yes, is there a standard or guideline of what fits in PHP’s nature? I think its very confusing, isnt it? Anyone actually have some insights in this?
In the comments other users provide a wide range of opinions including:
- „I would recommend taking those types of comments with a grain of salt. PHP’s nature is a very subjective topic, as you can tell by the other comments.“
- „PHP was made to make dynamic web pages at a time when webpages contained minimal dynamic content. It was made at a time when web pages doesn’t required a programming language to generate.“
- „Easy to pick up and make a website for weak devs/prototypes (easy to abuse). Much of the hate for PHP is because this abuse is possible and exploited often.“
Check out the full post for more opinions or to voice your own!
There’s a good conversation happening over on Reddit today about what constitutes the „PHP community“ and how it can be defined. JordanLeDoux wonders if those who just write PHP are included in that group as well.
One conversation was with a dev who hates PHP because (mostly) they work with code that was written by some non-PHP dev who was asked to write it. The other was with /u/krakjoe from the PHP internals team, where I was commenting on a sentiment that sometimes finds its way into the internals mailing list: if you want a real programming language, then go use one.
In both cases, I made the assertion that most people who utilize PHP or edit a script aren’t actually part of the PHP community. […] How can someone that is functionally isolated from any other person working in PHP be part of the PHP community?
Responses to the post are, for the most part, encouraging suggesting that
- There’s not a single „PHP community“ but many smaller ones
- sub-communitiies can revolve around technology or a product
- The different definitions of community
- The broad range of skills that „PHP developers“ are known to have
Check out the full post for more opinions and share your own!