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.
> (perceived?) reality is that social grows your user base and RSS doesn't
Another fair point... in general RSS can be thought of as "broadcasting to users" instead of the illicit "user engagement".
On another fair point though, the RSS app I currently use [Podcast Addict] has a "share" option with beget-plenty list of options [from eMail to Twitter]. I can't imagine other RSS apps not having the same in Current Year.
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.
Engage where? Engage how? Tech savvy may not be what you're looking for, and is not always a good thing.
I think what fulldecent is saying is that people reading on RSS have a barrier to sharing and a barrier to commenting that doesn't exist on social media. On Twitter or Facebook, the "share" action is intrinsically linked to the article in its native format. Not so on RSS.
I've been wanting to set something like this up with Hacker News. The problem is that you have to do it two-stage; your website needs to go live, then you need to post it (so you can get the post url), then you need to update the website.
It's not insurmountable, it's just a bit harder than it should be to automate, especially if you're running a static site or something that takes a minute or two to go live. I'd love if social sites had some kind of API for settting up a draft post or deterministic urls, so you could pre-include the link during your build step.
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.
...sounds like a fun project to trigger an external flash on manual from the iPhone flash! I wonder if those lightning triggers would be sensitive enough.
Ah -- but the iPhone would need manual exposure settings or you'd likely overexpose.
For me at least, having an external flash has very little to do with how bright it is, and very much to do with where the light is coming from. A flash coming from 1/4" away from where the lens is, usually doesn't look too great.
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!
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.