shubham-j-sde commented on PR #287: URL: https://github.com/apache/kvrocks-controller/pull/287#issuecomment-2742686611
@SharonIV0x86 , I really value your time and opinion and our brainstorming discussion to decide whats best for community and users of Kvrocks and Cluster controller. and I'd be happy to change to JSX if needed. but as we are still discussing, i'd propose reasons for why to include TS now. 1. Typescript is not an optimization, its more reliable language, ensure safety, scalability and easy to maintain in long run. [ref1](https://www.reddit.com/r/reactjs/comments/14784fy/javascript_vs_typescript/) [ref2](https://radixweb.com/blog/typescript-vs-javascript) > As the current focus is to develop a MVP of the kvrocks-controller with the essential things integrated in it. Yeah I agree with you and i am saying both things are possible, so we do them along with using best practices together. 😃 > Looking ahead, whether now or in the future, transitioning to typescript will be essential for a long-term development strategy. It's not transitioning if done now, current website got live just a few days back, so it will cost no additional bandwidth. Doing this now would save lot of future bandwidth (which are difficult to get hold of for open source project) for community to work upon developing new features, This would also save any possible downtime for users during future migration. Using modern practices also means less worry for dependency failures in near future. > Honestly, i believe current code lacks even some Next.js module standards, not to mention basic web accessibility standards. And Lack of Module standards is Red Flag for Open Source project as it hinders new users to follow code and contribute. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
