Laravel is ideally suited for fluent PHP developers who want a framework that can be used to both rapidly prototype web applications as well as support scalable, enterprise-level solutions. I think where it is less ideal is where the client has an expectation of using a certain CMS, or of having a certain experience on the admin side that would perhaps be better suited to a full CMS such as Drupal or WordPress. Additionally, for developers who don't want to write PHP code, Laravel may not be the best solution.
NetBeans is extremely user friendly and easy to start developing complex applications. Adding and configuring external libraries is much simpler than in Eclipse. It is highly cost effective and most of the latest framework based libraries required are automatically downloaded to the projects. The overall tool is also light weight and consumes less memory as compared to other competitor tools.
Significant learning curve. You cannot be an expert in a week. It takes many experimentations to properly understand the underlying concept. We ourselves learned it by using it on the job.
Too much to soak in. Laravel is in everything. Any part of backend development you wish to do, Laravel has a way to do that. It is great, but also overwhelming at the same time.
Vendor lock in. Once you are in Laravel, it would not be easy to switch to something else.
Laracasts (their online video tutorials) are paid :( I understand the logic behind it, but I secretly wish it would be free.
The eloquent ORM is not my recommendation. Let's say you want to write a join, and based on the result you wish to create two objects. If you use Laravel to do automatic joins for you, Laravel internally actually makes two calls to database and creates your two object rather than making one join call and figuring out the results. This makes your queries slow. For this reason, I use everything except eloquent from Laravel. I rather write my own native queries and control the creation of objects then rely on Laravel to do it. But I am sure with time Laravel will make fewer calls to DB.
NetBeans [should] work smoothly with systems having less RAM. Systems with less RAM face trouble with NetBeans.
File open history also requires improvement. Once NetBeans is restarted, all files are closed automatically and there is no shortcut to open last opened files.
Netbeans enhances my coding work, shows me where I have errors and helps find variable instances. I would be lost without find/replace in projects functionality as I use projects as templates for new projects. Occasionally the code hints aggravate me, but I understand that it is actually making me a better coder, working to get the 'green light' of a clean file with no errors or clumsy code.
NetBeans has a very strong user community. We can find solutions here for almost all the problems we face. In addition, we can forward NetBeans Support teams the problems we cannot solve. We can get quick feedback from the support teams, but I generally try to solve my problems by following the forums.
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.
It works very smoothly as compared to other tools . The problem of restarting and reimporting the projects is not in the netbeans IDE . The front end development features are good . Netbeans connector is one of the best thing which enables us to deeply integrate netbeans IDE with google chrome browser
Laravel allows us to rapidly prototype and build complete, scalable applications internally, which saves us time and allows us to have internal tools that fit out precise needs. We use Symfony for a similar purpose, but Laravel is an even higher-level framework that we find saves us substantially more time when building many types of web applications.
Laravel solves many of the underlying concerns of building a large application (such as authentication, authorization, secure input handling) in the right ways. It saves us from handling those low-level concerns ourselves, potentially in a way that could take a lot of time or sets us up for issues in the future. It's tough to assign an ROI to this, but I'm sure it has prevented issues and saved time, which both have an impact on our financial situation.
By working on Netbeans I just learned one more tool and can teach others about it. One should learn every tool so that it might help someday if another editor is not available and you have to use different software for your work.
Compiling code became easy as it is not a feature of normal text editors. Only IDE can do this.
