Started coding at the age of 13, now a professional software engineer and Scrum Master, creating and maintaining enterprise solutions. Eat - Sleep - Code - Lift - Repeat 💪🏾
As already said by many others, value the inputs of the comments by yourself and take them as critical thought-provoking impulses.
On one hand there is the fact that you already have React experience on your team so it would not take much time to get on track with React.
On the other hand there is a nice post here about YAGNI(You aren't gonna need it). YAGNI maybe saying that you don't need React right now so go with Preact if it fits your needs for now.
My choice would be React and here are the arguments:
React done right prevents you from getting the mentioned spaghetti-like code.
With the future in mind, React may fit better for scaling purposes
The ressources on React and the community is (as of my knowledge) much bigger than Preact at the moment.
You have the React knowledge on your team, use it; don't loose it (by people possibly not ready to move to PreactJS)
Hope my few points can help you.
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.
As already said by many others, value the inputs of the comments by yourself and take them as critical thought-provoking impulses.
On one hand there is the fact that you already have React experience on your team so it would not take much time to get on track with React.
On the other hand there is a nice post here about YAGNI (You aren't gonna need it). YAGNI maybe saying that you don't need React right now so go with Preact if it fits your needs for now.
My choice would be React and here are the arguments:
Hope my few points can help you.