Magento Masters on Magento 2

[goivvy]

Hi,

I recently interviewed 3 Magento experts: Marius Strajeru, #1 on Magento.Stackexchange Q&A site, Jisse Reitsma, Founder, Yireo and Rakesh Jesadiya, top contributor to Magento in India.

I asked them 12 questions and their answers you can check out here. They shared their expertise and knowledge on various Magento 2 aspects.

 

[antropy]

Great interviews and some very interesting answers, for example:

5. How would you deal with slow Magento 2 site? Name three optimization tweaks you would do.

Marius Strajeru:
- full page cache (varnish that now has native support).
- throw hardware at it.
- hire a good sys-admin/devops that deals with these things every day.

Jisse Reitsma:
Enable Zend OPCache, even in development, and tune it. Tune MySQL InnoDB buffers. And make sure to work with all caches enabled, even in development (except for FPC).

Rakesh Jesadiya:
-- Use defer js extension.
-- Image optimization, CSS/JS Merge/minify.
-- Keep Better code (try to avoid get rid of foreach loop and objects)
-- Disable unnecessary core extension.
-- For static files we use cdn server to give more boost to the site.
​

So some of the best Magento developers in the world say get around site speed problems by: throwing hardware at it, doing extensive very complex (only server engineers would do it) configuration, and trying to cache everything.

And:

12. What Magento 2 skills were the hardest for you to learn and why?

Marius Strajeru:
Definitely UI-components. I'm still struggling with it. I mean I got used to the concept, I can do simple tasks with them, but when you deviate a little more from the "usual" I have troubles.

Jisse Reitsma:
Magento 2 frontending was one of the toughest parts, not just for me but for most developers.
Currently, I'm actually giving a lot of developers training in how to use KnockoutJS and RequireJS properly in Magento 2 to build your own modules and themes, even leading up to the creation of your own uiComponents.
There is a lot to digest. But because I hang in there, I now feel confident in working with it. It takes time and effort to learn this, but if you make that effort and invest that time, it pays off. The methods that you use to learn, might differ: You might invest in a quickstart training, learn from online tutorials, listen to talks at conferences.
But in the end, the energy that you invest into learning Magento 2 leads to the end result of you having full control. And that's what Magento 2 is all about.

Rakesh Jesadiya:
Knockout js and UI Component were hardest for me to learn in Magento 2.​

And there we have it - three of the best, most experienced Magento developers in the world, struggling with "simple tasks". This shows how complex Magento is and why development with it is very expensive, as I have explained in great detail here:
https://www.antropy.co.uk/blog/the-lure-of-magento/

If your company can afford to pay a team of the best developers in the world plus dedicated dev ops engineers then great, maybe Magento is for you. If you're a small-medium business, please don't think that because some really big, successful companies use Magento that you should too.

 

[WebshopMechanic]

Every Magento site I've ever worked on has caused headaches. I'm a marketer so I've been at the sharp end as a day-to-day user. Whilst it is a good system, it's so complex and most businesses only use about 15% of it's capability.

It has been responsible for more frustration and wasted time than I care to remember.

I wonder if 2.0 will be any easier to use or have a better UX?

A client of mine is having to re-write a load of 3rd party stock management feeds because the new Magento core is completely different to the existing one. I'm currently spec'ing things out at the moment.

More pain on the horizon maybe...

 

[GoingOnline]

I have totally moved away from Magento and unless I am starving and there is nothing else at all in the market (including gardening roles) I am staying that way. As a developer, it's just not worth the headache, and it's terribly overengineered.

And as a user there are other simpler, nicer solutions that fit 90% of the businesses I deal with.

 

[owas]

We are currently working on a project and part of that is migrating 1000+ products from ebay. The magento2 set up was simple enough, made a few modification on an pre made template. But gettign the products in is proving harder than we thought. Each product has 5 unique size and 14 different colours. eBay File exchange manager gives a good CVS of these options but its not configured good for magento2 import. We tried a magneto2 connect extension but this simply creates each option as a simple product which pushes the memory usage up to nearly 400MB which then crashes the site. So its more than likely the script but with how resource heavy magento 2 is as per the OP magento 2 is not ideal.

 

[goivvy]

I didn't know this thread would turn into 'how-much-I-hate-Magento' discussion.

Of course it is complex. Comparing it with opencart is like comparing bicycle with spacecraft. Many need a bicycle. Only a few need a spacecraft. For those was this interview.

Great interviews and some very interesting answers, for example:

5. How would you deal with slow Magento 2 site? Name three optimization tweaks you would do.

Marius Strajeru:
- full page cache (varnish that now has native support).
- throw hardware at it.
- hire a good sys-admin/devops that deals with these things every day.

Jisse Reitsma:
Enable Zend OPCache, even in development, and tune it. Tune MySQL InnoDB buffers. And make sure to work with all caches enabled, even in development (except for FPC).

Rakesh Jesadiya:
-- Use defer js extension.
-- Image optimization, CSS/JS Merge/minify.
-- Keep Better code (try to avoid get rid of foreach loop and objects)
-- Disable unnecessary core extension.
-- For static files we use cdn server to give more boost to the site.
​

So some of the best Magento developers in the world say get around site speed problems by: throwing hardware at it, doing extensive very complex (only server engineers would do it) configuration, and trying to cache everything.

And:

12. What Magento 2 skills were the hardest for you to learn and why?

Marius Strajeru:
Definitely UI-components. I'm still struggling with it. I mean I got used to the concept, I can do simple tasks with them, but when you deviate a little more from the "usual" I have troubles.

Jisse Reitsma:
Magento 2 frontending was one of the toughest parts, not just for me but for most developers.
Currently, I'm actually giving a lot of developers training in how to use KnockoutJS and RequireJS properly in Magento 2 to build your own modules and themes, even leading up to the creation of your own uiComponents.
There is a lot to digest. But because I hang in there, I now feel confident in working with it. It takes time and effort to learn this, but if you make that effort and invest that time, it pays off. The methods that you use to learn, might differ: You might invest in a quickstart training, learn from online tutorials, listen to talks at conferences.
But in the end, the energy that you invest into learning Magento 2 leads to the end result of you having full control. And that's what Magento 2 is all about.

Rakesh Jesadiya:
Knockout js and UI Component were hardest for me to learn in Magento 2.​

And there we have it - three of the best, most experienced Magento developers in the world, struggling with "simple tasks". This shows how complex Magento is and why development with it is very expensive, as I have explained in great detail here:
https://www.antropy.co.uk/blog/the-lure-of-magento/

If your company can afford to pay a team of the best developers in the world plus dedicated dev ops engineers then great, maybe Magento is for you. If you're a small-medium business, please don't think that because some really big, successful companies use Magento that you should too.

 

[antropy]

Comparing it with opencart is like comparing bicycle with spacecraft. Many need a bicycle. Only a few need a spacecraft.

Haha exactly that!