As a Laravel developer, what would you say to a potential client that asks “why not Magento?”

When a client comes to me (or I approach them), they want to know that I am the right person for that work.

When they shop around to multiple people*

If I am great at laravel and ok at Go, and they ask, I will flat out say that I can do the project more efficiently, quicker, with a higher level quality result due to my experience with laravel.

A client would rather hear "Laravel is the right choice because it is more flexible" than "it's all I know how to use."

I have basically told them that Laravel is my choice because it is cheaper for them (quicker), and the product they get from me will be better due to my own expert view and experience (higher quality).

Again you are just saying "this is all I know how to use."

Honestly for most dev work I get I can use a few different languages fairly well but I tend to use php/laravel mainly due to how good it is at most things.

I like Laravel too!

If the customer still wants me to use Go after this, then fair enough I will use Go. But ultimately most customers will want to find the right dev based in experience and capability.

This is where you tell the customer "Go is bad because X". Nowhere in my thread did I say that they should go with a client that wants to use Magento. I said there are significantly more compelling arguments than "Laravel is all I know how to use."

You wouldn't join a Go team as a lead developer if you never really used Go. Likewise you never should say yes to absolutely everything a customer asks because of FOMO and instead embrace your talent.

No, and I wouldn't expect a Laravel shop to drop everything and use Magento, either. I would expect them to give the client a good reason to use Laravel over Magento.

In over 10 years worth of dev, many client based, I have rarely come across such a requirement being an issue.

Great

This is a rare issue and honestly tends to crop up when you are upgrading an existing code base or something. Again, it's normally better to re write for a legacy upgrade vs actually use a decade or more framework strung together without documents...

Now we're going off topic

/r/laravel Thread Parent