I read this article and found it to be a great example of why we should NOT adopt modern PHP techniques at our company.
50 lines of code and contrived examples (is HelloWorld class a view or controller? AwesomeClass is a model?) get one line of HTML emitted in a barely readable way.
This article fails to motivate why each layer of complexity is added. It basically starts with the assumption that you want to use a framework and says "hey look you can do the same thing with 50 lines of boilerplate, not really, but kind of."
I would be much more impressed with an article that starts with the obvious way to write a PHP application (.htaccess, index.php, products.php, library/database.php, library/*.php) and then explains the actual problems that would make you want to opt for more complexity/organization/modern techniques.
A visitor that comes to your site via social is MUCH more valuable than someone that comes via RSS. The economics of this reality are what removed RSS from the limelight.
Dear publishers, let's fix this. Whenever you publish a blog post, etc. please syndicate it on social and then go back to your site to add "DISCUSS THIS ON TWITTER/whatever AT https://t.co/aesou02". Make sure that this also syndicates to RSS.
Dear pubsubbers, let's fix this. In your reader software, please lint these special links and show the discussion below the news. We know you want to get into the content discovery business -- this is the first step.
See the Slashdot RSS feed as a good example, they inline the discussion right in the feed.
This article could be more clear in showing who it is addressed to.
"How to Make the Most Out of Pull Requests -- a guide for project maintainers" or "How to Make the Most Out of Pull Requests -- so that your contributions get accepeted"
I just want to say when iPhone supports external flash I will probably never use Canon again. And I've used it for 10+ years professionally in the studio. Seriously, it's like Japan's products are moving at the same speed as their economy, i.e. not at all in the past 20 years.
I have a 80D and there is a 1/4" mount at the bottom. But if you take a photo in portrait orientation with a long lens then the 1/4" bolt will not be strong enough and the camera will twist out of it. It's a joke!
I miss using machinations in MS Access back in the day. Now with Google Sheets, I am left wonting for a tool that enforces primary keys and is /easy/ to set up a view or query.
Thanks for understanding. I was writing this up and wasn't sure anyone would really connect with the story or care about one line of code against a now non-existing broker. I'm so happy to hear this support.
50 lines of code and contrived examples (is HelloWorld class a view or controller? AwesomeClass is a model?) get one line of HTML emitted in a barely readable way.
This article fails to motivate why each layer of complexity is added. It basically starts with the assumption that you want to use a framework and says "hey look you can do the same thing with 50 lines of boilerplate, not really, but kind of."
I would be much more impressed with an article that starts with the obvious way to write a PHP application (.htaccess, index.php, products.php, library/database.php, library/*.php) and then explains the actual problems that would make you want to opt for more complexity/organization/modern techniques.