This item should have been 'Protractor 6 will break compatibility if you don't make the transition'. Which essentially is - your code will break if you don't maintain it. Thanks cap. But I'm thinking about benefits I get like readability, and resolving what you mentioned under #4
Yes, maybe. Not more complicated than Java+Selenium stack though. But in the end who cares, if eventually you talk to the last layer of the stack (protractor itself), which is pretty straight forward. You don't mention how NodeJS is complicated under the hood, but why would you care if use don't need to know it to start using it, right?
That exactly the point why async/await were brought to the game, to solve this 10 level code structure
Nothing in particular is required for testing, it's always what you like/prefer, so why not Protractor? which has very good community support, unlike many new tools (at least for now)
Don't get me wrong, the practice shows that those who don't make transition to newer technologies timely, lose their marketability. But that's not about Protractor in 2020
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Such a nonsense to be honest in my opinion... Yes, sooner or later Protractor may be a bad choice, but why I disagree to the mentioned as of today:
Don't get me wrong, the practice shows that those who don't make transition to newer technologies timely, lose their marketability. But that's not about Protractor in 2020