[WageWolf]

Have had plenty of feedback that we should be using a popular framework, rather than core PHP, for security, and future work reasons. Do you guys and gals agree?

Not sure if I should be getting it moved over then? Was told it will take around a month to complete the rewrite.

[kur042]

Definetily yes ! if want to make money from web dev, you'll work most of the time with php frameworks.
About security issue, they're most of the time serious about it since it'll be widely used. Plus, u'll be intuitively using conventions when coding with frameworks.
If you have a good knowledge of php, you can handle laravel within few hours, really. its concepts are simple and this framework target small/medium projects. If you want something much bigger to toy with, pick symfony.

[Nachfolger]

Sounds like BS. Whoever told you to explicitly move to Laravel probably benefits from it in some financial way, if your application is working just fine, why would you move. As long as you're not a moron, why would adding a framework make anything more secure? Follow security standards, pen test your code, stay up to date; and you'll be covered.

Frameworks are the dumbest thing to land on this earth. More dependencies, more problems.

[Don Vito Corleone]

As you can see, there has been a war going on forever between people that like and people that dislike frameworks. Honestly, if your current project works without any problem than you shouldn't be getting a rewrite. However the main reason I use frameworks is to not reinvent the wheel every time I start a new project. For example a fully secure login system takes only one command with Laravel (just one example). You can add your own raw php code to it as well so you can have the best of both worlds.

So if it works already for you than there's no reason to switch, but if you're looking to get a job than most companies like it if you know a little bit about laravel/symfony. Won't be a dealbreaker if you don't as they are pretty easy to learn. It all really depends on you and your preferences.

Try watching videos on "core php vs frameworks" it may help you in your decision, but make sure to look at your own specific situation and keep in mind that everyone is biased

[WageWolf]

Sounds like BS. Whoever told you to explicitly move to Laravel probably benefits from it in some financial way, if your application is working just fine, why would you move. As long as you're not a moron, why would adding a framework make anything more secure? Follow security standards, pen test your code, stay up to date; and you'll be covered.

Frameworks are the dumbest thing to land on this earth. More dependencies, more problems.

As you can see, there has been a war going on forever between people that like and people that dislike frameworks. Honestly, if your current project works without any problem than you shouldn't be getting a rewrite. However the main reason I use frameworks is to not reinvent the wheel every time I start a new project. For example a fully secure login system takes only one command with Laravel (just one example). You can add your own raw php code to it as well so you can have the best of both worlds.

So if it works already for you than there's no reason to switch, but if you're looking to get a job than most companies like it if you know a little bit about laravel/symfony. Won't be a dealbreaker if you don't as they are pretty easy to learn. It all really depends on you and your preferences.

Try watching videos on "core php vs frameworks" it may help you in your decision, but make sure to look at your own specific situation and keep in mind that everyone is biased

One of the main reasons was to allow additional developers an easier time working with the system. True, or not?

[Don Vito Corleone]

One of the main reasons was to allow additional developers an easier time working with the system. True, or not?

From my experience, definitely true.

[DashPHP]

I think it's great experience to understand how these frameworks work, because let's be real. In the real world, barely anyone uses native PHP. It's always some sort of framework, whether it's light like Slim, or heavy like Laravel. They're used a lot.

Personally I've started playing with the slim framework utilising Eloquent and Twig. It's a nice change and the structural aspect is way better than raw php.

I am someone who has been writing Raw PHP for over 6 years now, and only am I starting to see the benefits of some of these frameworks.

Never used Laravel btw. Only the ones I specified above.

[WageWolf]

From my experience, definitely true.

Do you feel it is worth the change? Currently we only have one developer, and sometimes I work on a few little things. No near future plans to bring anyone on, however it may be useful in the future?

[Don Vito Corleone]

Do you feel it is worth the change? Currently we only have one developer, and sometimes I work on a few little things. No near future plans to bring anyone on, however it may be useful in the future?

If he documents his code properly it's not necessary at all, but yeah for sure if your goal is scaling your business in the future than it's better to switch to a framework.

EDIT: I don't know the size of your project but one month of rewriting is A LOT tbh.

[WageWolf]

If he documents his code properly it's not necessary at all, but yeah for sure if your goal is scaling your business in the future than it's better to switch to a framework.

EDIT: I don't know the size of your project but one month of rewriting is A LOT tbh.

It is a very large project. 🤝

[Nachfolger]

It is a very large project. 🤝

I have to ask, did your developer tell you that you need to switch to Laravel or something? If you have a fully functional system, why would you want to rewrite it in Laravel when pure PHP is doing the job. As I mentioned before, I can only imagine that the person recommending this is benefiting from it in some way.

[To address your previous question]
Sure, prototyping new features will be easier with Laravel because it cuts down the amount of code you will need to write, but in the end, pure PHP will outlast any framework. In 5 years, if Laravel decides they no longer want to support their project, you're now stuck with a unsupported framework. Not to mention, anyone you want to hire to work on the project will now need experience in Laravel.

Damn I hate frameworks, they really irk me. Maybe my arguments aren't justified. I just cannot stand this whole new ecosystem of developing. Every company has to use or build their own little framework that will be irrelevant in 5 years.

[WageWolf]

I have to ask, did your developer tell you that you need to switch to Laravel or something? If you have a fully functional system, why would you want to rewrite it in Laravel when pure PHP is doing the job. As I mentioned before, I can only imagine that the person recommending this is benefiting from it in some way.

[To address your previous question]
Sure, prototyping new features will be easier with Laravel because it cuts down the amount of code you will need to write, but in the end, pure PHP will outlast any framework. In 5 years, if Laravel decides they no longer want to support their project, you're now stuck with a unsupported framework. Not to mention, anyone you want to hire to work on the project will now need experience in Laravel.

Damn I hate frameworks, they really irk me. Maybe my arguments aren't justified. I just cannot stand this whole new ecosystem of developing. Every company has to use or build their own little framework that will be irrelevant in 5 years.

You have no idea how much I agree with you, and how reassuring this post is.

I have always thought the same way about frameworks, however I keep seeing things everywhere shoving it down peoples throats, and making me second guess myself. Longevity is going to be key, going to stick with the Pure PHP app, coming soon! <3

/thread closed