Twitter | Search | |
Vinai
Very confusing messaging in this thread :( Two very important facts where omitted until late in the thread: 1) Deprecated only on the store front, not adminhtml (afaik) 2) Still supported even though deprecated until about 2021
Reply Retweet Like More
Vinai Nov 3
Replying to @VinaiKopp
So lets don’t panic and keep our socks on, regardless whether that news made you happy or sad.
Reply Retweet Like
Nils Preuß Nov 3
Replying to @VinaiKopp
But panicking is so much fun to follow on twitter
Reply Retweet Like
Rico Neitzel 👨🏼‍💻 Nov 3
Replying to @tutnix @VinaiKopp
Reply Retweet Like
Len 🇪🇺🇳🇱🇧🇷 Nov 3
Replying to @tutnix @VinaiKopp
*insert popcorn eating gif*
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
We stopped all ‘new’ coding on knockout.js end of last year. Total waste of effort imo, writing was on wall long ago on this. Sooner sort the better, push a third party frontend if needed let’s just move on and fast
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
Used to feel the same. Now I think backward compatibility is a key factor of $$$ success.
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
I think throw it away ASAP. Bad tech bad decisions, move on as fast as possible to a technology where will encourage new breed of developers into ecosystem. And that’s React/graphql imo
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
How is that a new breed of developers? Please explain.
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
Throwing things away before the replacement was ready gave us the Magento 2.0 release. Still many traumatized from that experience. It’s a lot better nowadays.
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
I think it will pull in React focused developers that aren’t necessarily in ecommerce space today. And won’t need to be so specific tomorrow, which I think is a good thing
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
And as a result I think they may bring new ideas from outside hence ‘new breed’.
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
It will still be Magento specific. DIY is (and was) always an option but that is costly and isn’t always the right choice, especially with an inexperienced team. The alternative is building on the platform which will continue to be quite specific but can save $$$.
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
We shall discuss in person Saturday? ;)
Reply Retweet Like
Karen Baker Nov 3
Replying to @VinaiKopp @magento
And actually I’m covering this to some extent in my talk, so maybe I’ll research a little more and expand on it. We have decoupled code from magento and I think for solid reasons. I’m not SI so hard to comment for them
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
It is (and was) the same situation on the sever side. It’s totally possible to create code that’s decoupled from Magento or bring in other frameworks (not me but whatever). Those devs bring in ideas from outside the Magento space. But there is a cost associated with that, too.
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
Yes, excellent! Lets!
Reply Retweet Like
Vinai Nov 3
Replying to @wsakaren @magento
Yes, different set of constraints and requirements.
Reply Retweet Like
Mark Shust 👨‍🏫☕️🚀 Nov 3
I agree. I consider myself an intermediate react dev and would love the new stack, but don't like this news at all from a business standpoint. The current PWA offering is so far away from production that even mention deprecating knockout/luma right now is not a smart decision.
Reply Retweet Like
Mark Shust 👨‍🏫☕️🚀 Nov 3
react devs want nothing to do with a PHP stack
Reply Retweet Like