Member Since 5 Years Ago
4,975 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
I've been working on an app with React-Native which appears to be an awesome step up from current hybrid mobile apps while also making it possible to learn once and write for both iOS and Android. My only point in bringing that up is if you believe you may be doing some mobile work in the future then time invested learning React now could pay off down the road.
SP1966 left a reply on Setting The Tic Key To Open The Terminal On A Mac...
@olyckne Thank you, that's it!!
SP1966 started a new conversation Setting The Tic Key To Open The Terminal On A Mac...
In one video, which for the life of me I cannot find @JeffreyWay showed us how to set up a Mac to a press of the Tic key would open the terminal, does anybody know which one?
With ES6 coming the tic is quite useful and I would very much like to reset the key. Unfortunately I cannot recall how in the hell I did it in the first place! :)
On an Atom related note, Visual Studio Code, which is based upon the same underpinnings as Atom is pretty phenomenal when it comes to JS coding. If you use a framework there are likely Typescript TSD files available which give you some very nice autosence like hinting. I also like the git integration within VSC.
Microsoft takes a well earned beating among the coding community but VSC looks like it'll mature into an exceptional JS editor, splitting the difference between a raw editor's speed and an IDE's helpful features.
Are you building a SPA (single page app) front end with Aurelia or just trying to functionality to Laravel views?
If you're building a SPA then I personally would not integrate them at all. Keep them separate, including build environments and save the potential headaches on integrating them tightly.
If you're simply adding some functionality to your Laravel views then IMO Aurelia is a bit heavy and that is a perfect use example for something like VueJS.
SP1966 left a reply on What Frontend Framework Would You Choose For A Slick Web App?
@andyg1 "Then I read somewhere that even though it is backed by Google they don't actually use it for any of their systems, which is where React stood out for me i.e. Facebook use it in production."
Don't believe everything you read on the internet, unless it comes from @Bashy or @JeffreyWay. Angular was an internal project specifically for internal use which was made publicly available later. I believe the first product they used it on was their advertising platform, and given Google is an advertising driven company I would say thats a pretty big commitment.
Framework discussions are often more flammable than political or religious discussions and often times emotional people write complete bullshit in support of their personal choice, or against competitors. Community size alone should be a decent arbiter of what has been weeded out and what has proven useful!
SP1966 left a reply on What Frontend Framework Would You Choose For A Slick Web App?
Angular version 1 definitely has an up and down learning curve. On the other hand the community is by far the largest of the JS frameworks so getting help is usually only a Google search away. It also has a massive number of packages available so you're not reinventing the wheel as you go along. Regarding Angular V.1 performance, they've remedied much of the past issues which were largely limited to pages with thousands of bindings. In later versions, beginning with 1.3 I believe, you now have the ability to set one time bindings so Angular will not have to watch everything, only those bindings which can/will change.
Version 2 is a significant change, people who complained about the 4.2 -> 5.0 upgrade of Laravel won't be happy going from a V.1 Angular app to V.2. On the other hand they're still not only supporting V.1, they're still developing it so you're not forced to change. Finally, from what I've been seeing V.2 is going to be a far easier to learn and far more performant in all areas.
For my money community is what separates the winners from the also rans in the framework world. Laravel had to be great to build the community, but the community is what really helps it grow with both packages and knowledge. No other JS framework has anywhere close to the level of community resources available that Angular does. With Laravel and Angular you have to two most popular frameworks in their respective languages and focuses, and they're both the most popular for very good reasons.
Angular is my choice!
Edit: @Ruffles made an excellent point that I missed, Ionic Mobile Framework! Mobile apps are important these days, probably more important than web apps, and with Angular JS, HTML, and CSS its relatively easy to leverage your existing knowledge to build excellent hybrid mobile apps!!
Final Edit: If you've built more than a simple Laravel app you've more than likely used community packages to ease and speed up the development. You'll have the same types of resources available with Angular, no re-inventing the wheel, there are over 1500 packages available to Angular developers and most can be found here: http://ngmodules.org/
Your security resides on the back end as there is nothing you can do to keep your front end code private.
In the long run V1 is going to become V2 which will become V3 and so on. If it were me I would prefer to not have all of that combined with my main site code. If it were me I would simply create a subdomain for the API and keep a separate copy of Laravel or Lumen there.
I don't know if you're using Laravel's built in Auth for your app but you're likely to find it difficult to manage with a mobile app. Mobile apps tend to be easier to deal with using token based auth which would require some changes to your main site if you're not already using them.
For my money in the long run the added complexity of separating the two easily overcomes the duplication required.
Between the open sourcing of the site code and making the videos free I thinks my idea for www.thebestlaraveltraining.com is going to fly!
And don't ask, there'll be no freebies ya cheap SOBs!
This thread is 238KB gzipped/519KB total size and takes just under 2 seconds on my 75Mb connection.
I think this may be what you're looking for: http://laravel.com/docs/5.1/queries#advanced-where-clauses
You're welcome! It's nice to occasionally be able to help rather than always the guy looking for help!! :)
What @JeffreyWay said. There is constructive criticism and then there's acting like a petulant child, one shows respect and deserves respect in return, the other doesn't.
@jlrdw You're comment in support of IE6 was that "proper HTML is the key" but now you suggest newer tech is lousy without allowing for proper coding. A poorly coded site using current tech is in no way a good reason to remain in the past.
If you're building an API back end to serve the Angular front end then build it completely separately and use CORS to connect to the API. Tightly integrating Lumen/Angular is unnecessary and adds difficulty in the vast majority of cases IMO.
@vitr If you use JWT tokens you shouldn't be storing any state data server side. The token is self validating, so long as each of your servers that accept the token for validation knows the secret/salt used in signing the token they can each validate it independently.
@miso I highly doubt anything as large as airbnb is running a framework like Laravel, certainly not on the API end. Besides, it makes no sense whatsoever to run a full framework like Laravel to simply respond to an API, especially a busy API. The author of Laravel himself uses a micro-framework for the busier aspects of his projects which was the motivation for developing a Laravel like micro-framework in the first place.
How busy do you expect the API to be? If you're feeling a need for speed then Lumen all the way, if not then Laravel would likely be a little easier and far more flexible. Regarding the API being used for both websites and mobile apps you're likely to find JWT/JSON Web Tokens far easier to use across all platforms than a session based auth.
The idea that you need to install Laravel simply to use it's generators, then C&P over to your actual app is inane. I'm very curious why generators are removed from Lumen and wonder if they cause some sort of performance issue?
@yadakhov To use Lumen or not should not be decided based upon if you need what Lumen is missing so much as how much of Laravel don't you need. You may find you have to add a few things to Lumen to get the functionality you desire, but that can still be better than getting those few things included in Laravel with a bunch of other stuff you'll never use.
@devinfd Well, then it would be nice if I would start noticing such things! You can lead a blind man to water, but you cannot make him see version tags!
@JeffreyWay It would be nice if all the videos were tagged with the version of Laravel/Lumen used and we could select the version we want as with the forum labels. I realize much of the older work is still valid with even 5.1, but it would be a nice feature to have if you have the time to implement it!
To me the current docs assume you have a solid understanding of PHP OOP programming and I don't think that's unreasonable. I think even with the improved docs Taylor is working on all that is going to happen is those of us who're a little (or a lot) behind the curve are going to have an easier time C&P code into our projects while not really having an understanding of why. All that is likely to change IMO is when the questions arise, not if they will.
That said, better docs are always better!!
You cannot stop people from trying to access of publicly visible API. You need to secure the API and only respond to those with the proper access privileges. As @BrianDillingham said, tokens are the way to go! Google JWT/JSON Web Tokens.
You have an error in your post regarding Bitbucket, the free account lets you have as many private repositories as you like but only five users on your team.
I'll toss out Github's Atom Editor as a very nice, and free alternative to Sublime! They're on the verge of their 1.0 release and as recently as a couple months ago it was on the slow side, they've really gotten it optimized and it feels every bit as fast as Sublime. Take a look before you throw down money on another text editor!
I'm sure @JeffreyWay is a busy guy but I would be interested to hear his take on Atom!
You shouldn't be trying to use regular old session style auth or CSRF protection with apps. When you find yourself building a backend that will serve native apps you'll be best served using JWT/JSON Web Tokens for your security, they have you covered for both auth and CSRF protection.
@pasadinhas In OS X there are at least two /Library directories. The /Library directory is global, the ~/Library is specific you your user account. In fact the ~ is a shortcut to your user account so something like a theme, or even your own unique setup for an app would go in ~/Library so that any other users could have their own themes or setups and they won't interfere with yours.