Ummm, Ionic is heavily relying under the hood on AngularJS, and Laravel is currently advocating for VueJS.
I wonder if there is a solution as I've seen many people use Meteoric (Meteor + Ionic), Vueonic? hahaha
Laracasts has a ReactJS tutorial also, and ReactJS just broke into the mobile world. Maybe a: Vureactionic? Lol, I can see the new series to come: "Let's build a Laravureactionic from Scratch!"
I suppose you are referring to a score number that relies on a complex algorithm rather than a simple integer?
What I do for those is having a column (if it takes multiple columns I go with a different table) for that information, and every time something happens that would change the result, I trigger an event and re eval the algo just for that user and stores the new score.
With that approach, once I have to do the query, I don't have to run the algo for every user, it's already computed, so I only have to do an ordering by the final result.
Somehow, as the algo gets more complex, results have 1 million reasons to loose sync with the result it "should have", so I usually run a backup Cron daily to recompute the algo for every active user (inactive users triggers a recompute event once the log back in).
As the apps get more complex, you start using Queues and more regular Crons to maintain the Algo results updated without overloading servers.
That's what I meant, instead of a few L4 and unrelated videos, go for a small series of 6/8 videos, with a sense of continuity and direction.
I would like to see Jeffrey's point of view, best practices and tricks about working with queues, from practice to artisan hahaha. Start by explaining queue theory in a few lessons, then beanstalk basic usage, then how to queue events, how to dispatch them, etc...
Funny that I've found today the EloquentRepository methods @thepsion5 might be using while checking the old forums for some queryScope issues...
You cannot learn this in one month, or two. Programming is not a course you learn in X hours, it's a discipline.
The main difference is that learning a course is about spending some time and then keeping that knowledge for some time. Math equations, color theory, reading a Game of Thrones novel, etc...
Disciplines is more about lifestyle. You keep yourself in a constant learning and improving state. Instead of going through 400 pages in one week, and trying to grasp all that knowledge, you learn a tiny bit of knowledge, 10 minute video per week for example, and then you stick with that for a month until it becomes part of your programming style, until it becomes natural.
It's also useful that instead of writing the exact same code as Jeffrey writes, you take one of your old projects, and you refactor it with the new knowledge you had learned. Do it with 2 or 3 projects, and then keep the new ones going with that technique. Practice refactoring of old code and writing new one.
Neuroscientist says that in average, you need to keep trying for 90 days until the habit becomes part of yourself and you encounter less inner resistance, feel less lazy about it, or you simply cannot understand coding without it.
Think about it like space shuttles, 90% of the energy used for the space voyage is wasted during the first minute taking off.
@jamesaps you can find that information in the object oriented bootcamp video series.
I think this concept deserves a video from @JeffreyWay.
It's the difference between the Eloquent model, the Illuminate\Database\Eloquent\Builder (the one jamesaps is asking for), and the final collection/result from the query.
There is some "magic" going on behind the scenes, and it's somehow confusing to understand when you are dealing with each object.
I have 3 betacoins for the mailbox beta.
I use mailbox on iphone, ipad and now on my mac. It's not the best app in the world, but I like it.
If you need one, reply here. First 3 get them.
Took 3 days before they sent me one, so it's not a big deal.
You could either narrow or wide your CV.
If you HAVE to go with other PHP frameworks (narrow), go with our brother/daddy Symfony2. You will learn a few things that Laravel is doing under the hood.
If you prefer to go wide, learning the non blocking NodeJS, or starting an iOS (Swift / ObjectiveC) and/or Android (Java) path, are both good options in terms of job opportunities.
Another option is to enhance your cv with certifications, for example some Scrum/Agile ones, improving your portfolio, experience with side projects of different size and structure, alternative languages (Spanish/Chinese/German), etc..
(third and fourth might not be a requirement, but are strongly desirable)
After those, you should be ready to start with a framework like Laravel.
My opinion is that a laravel newbie presented for the first time to 4.3, and getting the same explanation depth we received for 4.0/1/2, should learn the new structure without too much trouble.
The real problem is not Larave itself, it's the growing amount of tutorials for free all around the web getting outdated and building frustration/confusion to the community.
@JeffreyWay - Thank you for the quick response.
@JeffreyWay - Are you planning on a lesson for Larabook and the (unfinished?) API about moving them from 4.2 into 4.3?
Another quick question. The new version of Laravel is going to make the backward lessons in Laracasts a bit confusing because of the new directory structure. Are you planning to tag each version with the Laravel version used on them?
Whats the number there? ranking? visits per second? unique visitors per day? requests/hour?
Btw, I missed an important one for me, "Caffeine". A small cup of coffee placed at the topbar. Works like a toggle. Pressed, system do not suspend. Unpressed, system goes asleep. Nice for laptops while reading, watching videos, using them as secondary computer with a stylesheet, etc...
On a side note, many big and important places do not publish what are they built with for security reasons mainly.
For example, well known sport newspaper from Spain is using Symfony2, they have millions of requests daily, and those SF2 components are part of Laravel. I also know for sure of a world wide dating website with more than 5 years of existence and millions of profiles is running SF2 currently, once again Laravel core.
If they publish on date XX/XXXX that they are using framework blablabla, they wont be updating that framework production components regularly, hackers know that, so the company inherit the framework vulnerabilities.
When you read "we use blablabla", think they are using a fairly modified version, or they already passed several security audits, or it's a small/medium size project, or they are simply mad hehehe
I would suggest you let us know a bit more about what are you calling "scalability issues"
Depending on the answer to those questions will vary a lot the response, from "absolutely scalable" to "nope, wrong technology decision".
Old PHP Wordpress with proxies, CDN, WPO, load balancers, memcache, etc... can scale up to million visitors per day "Search Engine Land" for example. Brilliant nodejs code may end up filling to quickly a redis instance, later killed by a system daemon collapsing the system.
I have a magic mouse for Illustrator/Photoshop. I also have 2 21'' monitors. None of those get much use recently, I somehow returned to the laptop simplistic style recently.
Profesional projects will open during august/september, personal are headed for christmas.