Напередодні Різдва з’являється особливе пиво, а ми його ДАРУЄМО!
Розігруємо запас Різдвяного для поціновувачів. Буде 2 переможці, кожен отримає по упаковці на 24 банки.
Умови прості:
1. підписка
2. лайк
3. ретвіт
Переможців виберемо 20.12 за допомогою рандому.
Для тих, хто не хоче чекати: https://t.co/ftLC7bPX9Z
@OleksKravchuk@Cloudways Exceptions are trusted 3rd party vendors that follow the Magento coding standards, and semantic versioning and are designed to be easily extensible.
In this case, when the development best practices are respected, 3rd party compatibility issues would be avoided.
6/6
#CWChat
@OleksKravchuk@Cloudways To conclude, it is preferable to use 3rd party extensions when the features they provide are enough to fulfill your project needs with minimal customizations or without them.
If not, custom development would be a more reliable way.
5/6
#CWChat
@OleksKravchuk@Cloudways In the long run, saved time for development will inevitably be spent on resolving compatibility issues during upgrades and its maintenance. That often makes that approach implicitly more expensive than a custom solution.
4/X
#CWChat
@OleksKravchuk@Cloudways The best but not obvious solution for avoiding compatibility issues with 3rd parties is not to use 3rd party extensions for major further customization.
At a first glance, it might look cheaper to use 3rd party solution and extend it rather than custom development.
3/X
#CWChat
@OleksKravchuk@Cloudways Most of the extensions just work after installation and you can even forget about their existence.
Until you try to customize them.
A long story short, most of the extensions are not designed to be customized, and have compatibility preserved during upgrades.
2/X
#CWChat
@OleksKravchuk@Cloudways In the ideal case, a developer should rely only on Major server versions components when possible and extension points: see https://t.co/oI40GIDVRb
But of course, it is not so simple in real life.
1/X
#CWChat
Hello Magento Community!
I would be happy to hear from you a story about when the Magento merchant had issues with the platform which led to change of the platform. Was it because of Magento itself, 3’rd party vendors, or issues with customizations?
Do you want to know what’s new in Magento 2.4? @MaksymNovik and I have prepared an article about Brave New World of Magento 2.4!
https://t.co/wsykQYxlnX
Those of you who missed discussions about In-Store Pickup functionality might get quickly involved watching this presentation during last year #MageConf by @MaksymNovik and @OleksKravchuk#Magento#Magento2 https://t.co/prZzOt9T3L
Me and @MaksymNovik have prepared some basic API documentation for upcoming In-Store Pickup feature in Magento 2.4.
Your feedback is wanted!
https://t.co/dqyjhPIwfC