Twitter | Search | |
willem wigman 2 Nov 18
Replying to @AntonKril @BenMarks
So (to clarify) this does not mean ‘replaced’? It means you’ll drop Luma and PWA will be the only frontend. Without context, stating ‘we deprecate requirejs’ insinuates something completely different. Which makes it a very confusing tweet.
Reply Retweet Like
Anton Kril 2 Nov 18
Replying to @willemwigman @BenMarks
Luma will be deprecated and supported for a while. But yes eventually it will be dropped, and PWA studio will be the only frontend.
Reply Retweet Like
Joost van Veen 3 Nov 18
This is confusing news. We whave several clients planned for transfer from M1 to M2, all on custom built front ends - which is a very big and costly overhaul for them. Are you saying they will need to have their complete frontend rebuilt again in a few years?
Reply Retweet Like
willem wigman 3 Nov 18
I think you could see it like an M1 shop that’s not on the RWD theme. It still works and will work for a long time. But it’s not the latest and fanciest technology. Pretty sure there’s still plenty M1 sites around with a heavily customized theme that’s not based on RWD.
Reply Retweet Like
Joost van Veen 3 Nov 18
That would be totally okay. The phrase that struck me was that both Blank and Luma would be totally removed. Which would mean any theme based on Blank or Luma would not work anymore. That *would* be a problem for shop owners who have recently invevested in a new custom M2 shop
Reply Retweet Like
Enno Stuurman 3 Nov 18
Agree I would advise any shop owner who still has to start M1 to M2 replatform to not start on Blank or Luma OOTB themes but either wait for or start building custom modern FE stack on top. This clear message from Magento supports this IMO.
Reply Retweet Like
Joost van Veen 3 Nov 18
Yep, that is what I read into this message as well.
Reply Retweet Like
Ben Marks 3 Nov 18
The wait will be years in that case.
Reply Retweet Like
Joost van Veen 3 Nov 18
Which is why I find it confusing. On the one hand PWA is great but still in its infancy, on the other hand building a new shop on a frontend that will break in a few years time seems a waste of time and effort. What woukd you recommend as the best way to go?
Reply Retweet Like
Ben Marks 3 Nov 18
I think that , myself, and some others will get together soon to give some guidance. Full disclosure: I am not well informed at this point, so I won't be surprised if we know these details already. Getting them out to everyone ASAP will be a priority.
Reply Retweet Like
Matthew Zimmerman
We will be supporting the existing solution for at least two years through at least 2.3. 2.4 isn't even planned yet, so it's premature to know when the removal will come. PWA Studio is available today, and some are already building PWA front ends right now.
Reply Retweet Like More
Matthew Zimmerman 3 Nov 18
It may also make sense to wait for Venia to be released, as it will provide a much easier path for implementation of a PWA.
Reply Retweet Like