Maybe it's just me because I'm not a native English speaker, but I'm writing some documentation talking about relations and after reading the Laravel docs and looking at the source code, I'm confused as to when to use one term or the other.
I've looked at the Ruby on Rails documentation because they have the same concept, and they also use both terms.
To me they both mean the same, so wouldn't it be better to just use one or the other? Or is there really a semantic nuance that I'm not getting? When do you use one or the other?
NoelDeMartin started a new conversation [Laracasts Snippet #98] Defining An Ideal Media Architecture - Just For Fun
I've been listening to the podcast for a while and I find it really interesting :). Many times I've got some thoughts about an episode, but I don't know exactly where to put them. I guess Jeffrey is fine with us reaching out in twitter, but I find it too ephemeral. @JeffreyWay would it make sense to add a disqus comments box like we have for lessons?
Anyways, for this episode I thought it'd be fun to share my thoughts on an "ideal" architecture for consuming media. I've been thinking about this for a while, and most of the things Jeffrey brings up in the podcast are thoughts I've had as well. So just for fun, or as an exercise on software design, let's talk about what'd be an ideal architecture - if you could remove the current landscape and legal restrictions from the equation.
So here's my proposal to get the ball rolling. Let's define three actors:
On an ideal scenario, consumers own a license to watch a movie. This license would only be paid once (similar to buying a BlueRay). Owning this license would allow any consumer to watch a movie in any streaming service free of charge.
How does a distributor earn money then? With a subscription. But this subscription would only cover using the platform. The actual ability of watching a movie would depend on the user holding a valid license for each piece of media. Imagine using Netflix with this architecture: you'd have access to all movies and once you try to watch one it either asks for the license or sells you one. In this regard, Netflix would act only as a mediator between the Producer and the Consumer. What would differentiate Netflix from its competitors then? The user experience. Maybe you like Netflix's interface better than Youtube. Or maybe you even prefer to use an Open Source client that is free.
In this scenario, consumers would have a collection of licenses and pay a subscription for the streaming services they like the most. But it'd be free to change between them without losing any media content.
Some notes about the technology:
Well I guess that answers my question then. The specific question I had is if there is any way to use StyleCI and have the same validation checks locally.
I'd prefer to use StyleCI instead of phpcs since it's what they use for the framework code, that's all.
I have been looking into how does Laravel apply php style conventions, and they use styleci.io which I have used and is great.
I am now trying to setup CI for a new project and I want to have the style checked as part of the build, but I am finding an issue with StyleCI because it only works online. As far as I know from Laracasts lessons, Jeffrey recommends using phpcs, but I haven't found a way to keep that compatible with styleci (other than trying to have the same standard, but it's difficult because they don't use the same nomenclature).
So what is the actual "best practice" at the moment, if any? Seems like the laravel/framework repository relies only on StyleCI and any problem is automatically fixed, but I don't like tools modifying my code automatically so I prefer to get an error if something is wrong. It'd be great to see those errors beforehand in my code editor instead of having to push to validate my code.
Is the only option to achieve this to use StyleCI online and phpcs locally, with all the headaches of making sure that the standards are compatible?