Twitter | Search | |
Joost van Veen Nov 3
Yep, that is what I read into this message as well.
Reply Retweet Like
Ben Marks #London Nov 3
The wait will be years in that case.
Reply Retweet Like
Joost van Veen Nov 3
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 #London Nov 3
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
Karen Baker Nov 3
As soon as you say ‘something will be deprecated’ it’s pretty hard to stand there and sell that to people for big bucks (if you have any integrity). Just as FYI.
Reply Retweet Like
Ben Marks #London Nov 4
That has boundaries and limits, though, right? I mean, Magento 1 was always going to be replaced by Magento 2. Is it not better to keep people informed? Maybe this is just a dialogue (poorly done on my part). Look at original EOL for M1. Market said LOLNOPE, we adjusted.
Reply Retweet Like
willem wigman Nov 4
Back when M1 was first announced EOL, my agency put all new project on hold for 3 months(!), because of the problems we had with M2, which was basically too immature for production. And clients no longer wanted a M1 site. Don’t underestimate the impact. It was big.
Reply Retweet Like
Ben Marks #London Nov 4
Interesting the high-level parallel (but NOT equivalency): The original M1 EOL was known since Nov 2015... with a three year shelf life. We messaged about it 1.5 years later. Here we're giving similar timeframes. This gives me a lot to think about, both ITO messaging & roadmap.
Reply Retweet Like
willem wigman Nov 4
Yes, messaging and timing are key. Deprecating before the alternative is ready-ready: that’s a problem for many SI’s
Reply Retweet Like
willem wigman Nov 4
And releasing M2 while it should have been in beta still, was the underlying problem.
Reply Retweet Like
Ben Marks #London Nov 4
Well, I have a lot to say about that! It turns out
Reply Retweet Like
Ben Marks #London Nov 4
Well-stated. I'd expand out from SIs though: it affects developers, extension vendors, as well as merchants. What do I learn/build, when, and for whom, plus: for how long will today's efforts matter in the future. <-- That's my framework for our planning.
Reply Retweet Like
willem wigman Nov 4
Lets not dwell on the past, but please don’t let history repeat. You make an impact on people’s lives. You know what it costed me personally...
Reply Retweet Like
Ben Marks #London Nov 4
If nothing else, we can improve communication + expectation setting. Ill effects aside, I'm glad to have these plans out 2-3 years early, when the ship is easier to point towards the proper destination.
Reply Retweet Like
willem wigman Nov 4
Just don’t set ships on fire before the new one is properly afloat. 🤷🏽‍♂️
Reply Retweet Like
Ben Marks #London Nov 4
I need breakfast to fully engage in nautical metaphors this... deep.
Reply Retweet Like