Agree. For some reason many developers thinks that “new” is automatically better than “old”. Which is certifiably crazy.
Old typically means fully bug fixed, with known limits and work arounds, and lots of examples to learn from. And a long track record of solutions using it.
New typically means full of bugs, unknown limits and work arounds, and very few examples to learn from. Plus a high chance of being abandoned and not supported 6 months or a year from now.
Given that, why on earth would you ever choose New over Old? Unless it is for fun personal projects.
Old typically means fully bug fixed, with known limits and work arounds, and lots of examples to learn from. And a long track record of solutions using it.
New typically means full of bugs, unknown limits and work arounds, and very few examples to learn from. Plus a high chance of being abandoned and not supported 6 months or a year from now.
Given that, why on earth would you ever choose New over Old? Unless it is for fun personal projects.