When can I start using Framework (Laravel)?

Question

I want to start with the fact that I searched a lot for this exact question, but none of them satisfied my needs.

I program Php, MySQL, HTML, CSS and Javascript the "old way", using only a text editor and creating each site from scratch. I created sites from the simplest to almost e-commerce, just coding every part of the application. The most important thing I did was to use some simple classes, such as database wrapper, singleton, and for the rest I always used functions.

Now, recently I signed up for a site where there are courses (I won’t say his name because I don’t know if I’m allowed), and I followed him about Laravel 3 (I know that version 4 is currently available .x), and I have to admit that I fell in love with her. I really like it, and I want to start using it, but I'm afraid it will make me "stupid."

I mean, Laravel has many helper functions, rough structure, etc., so using this, I will no longer learn pure Php, because for everything you need, there is already a built-in helper function.

To make a very simple example, if you want to join some tables, you use Eloquent and in literally 3 seconds you will do it. If you want to register a user, again you have an Auth class that does everything for you, even establishing sessions.

This is my greatest fear that I won’t know anything else, because everything you need is already provided, you don’t need to think about it anymore.

Laravel, on the other hand, helps you a lot, and it makes your job a lot easier. As far as I want to start digging into it more, I cannot but be afraid of its shortcomings.

• So, do you think I should wait and learn more about traditional Php before diving into the Framework?
• When is the right time to start using?

Answer 1

Take a look at all the sites you have created. Identify redundant items. Extract them into classes and functions and create your own environment. . This will allow you to quickly create sites and create a library. Once you do this, do not go down there. You can use another or not ... but you will also have your own.

What I've done. I have my own framework. And this is not bad!

There are two types of developers:

• users - they can use the material and receive
• actual developers - they can create things from scratch and provide users with tools

Choose which model best suits your needs.

• Category 1 is suitable for quick results, efficient and does its job. These guys should use third-party structures and libraries.
• The second category is artists moving forward with each new piece of code that they create. They go for performance during processing, the beauty and functionality of the code, as well as just functionality, etc. These guys feel offended by third-party structures and libraries and always fold their own. Because they can!

There will be another catch. . In some environments, there may be too much fat for your needs. Creating more specialized solutions can lead to increased productivity than to a single size. This is another perspective.

Bafta mai Departe :)