Twitter | Search | |
Ben Marks #London Nov 2
The most excellent doing his thing at . Konockout.js will be deprecated once is GA!
Reply Retweet Like
Max Chadwick Nov 2
Magento is a tech company and wants to move fast. Merchants are not primarily tech focused, the tech just supports their business, which is to sell online. Rapid iteration is not inline with their needs.
Reply Retweet Like
Anton Kril Nov 2
To clarify: it is too early to even discuss the removal date. One thing is defined: it will not be soon.
Reply Retweet Like
Mark Shust 👨‍🏫☕️🚀 Nov 3
great - you just stabbed m2 si's in the back. how in the hell are they supposed to close current/new m2 proposals if their clients are privvy to this information? also, are si's being disingenuous not informing potential clients of this information?
Reply Retweet Like
Anton Kril
Let me try to clarify again: the quote is from my answer about long-term plan for frontend. Current frontend is not deprecated now. It will not be deprecated for at least one more year. And it will stay in and will be supported for at least 3 more years.
Reply Retweet Like More
Anton Kril Nov 3
Deprecation will mean only marking APIs as “deprecated” and adding links to the preferred APIs - PWA. The deprecated APIs will still be supported.
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
Karen Baker Nov 3
Replying to @mrloo @AntonKril and 4 others
Yup, but this is old news, As soon as React was announced it was clear that existing frontend was dead dead dead
Reply Retweet Like
Anton Kril Nov 3
Replying to @wsakaren @mrloo and 4 others
That is why I’m surprised that the quote is considered as some kind of announcement.
Reply Retweet Like
Vinai Nov 3
The official communication at first was that both frontends would be supported.
Reply Retweet Like
Anton Kril Nov 3
For some reasonable period. Yes. And nothing changes there.
Reply Retweet Like
Christian Münch Nov 4
If we know that will be deprecated... Should we use it today for new developments? The quote in the tweet (without) context is unsettling people.
Reply Retweet Like
Anton Kril Nov 4
Replying to @cmuench @wsakaren and 5 others
Yes. Use it same as before: preferably for linking code. For all bigger customizations - isolate, make framework agnostic. In parallel, start looking at PWA studio. It is much closer to usable state than many people think.
Reply Retweet Like
Karen Baker Nov 4
Or worse moving target tech gimmicks. Please dev in iterative way that can be used early for all and build upon solid architectural foundations. Your game is our business
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
Anton Kril Nov 4
Replying to @wsakaren @cmuench and 5 others
This is exactly how it is being developed now. To allow early usage on simpler scenarios, and gradually adding features.
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