Ant Design 6.0 来了！这一次它终于想通了什么？

Core Viewpoint - Ant Design 6.0 has undergone significant improvements, addressing previous criticisms and aligning more closely with modern front-end development paradigms, such as Tailwind and Headless UI [2][18]. Group 1: Performance Enhancements - The upgrade to Ant Design 6.0 has eliminated runtime performance issues by adopting a pure CSS Variables approach, resulting in zero runtime [3][4]. - This change allows for better performance as browsers natively support CSS variables, reducing the need for JavaScript to compute and insert styles [4]. - Theme switching has become instantaneous, requiring only changes to a few CSS variable values at the root node for immediate rendering [7]. Group 2: Component Semantics and Customization - All components have undergone semantic DOM restructuring, allowing for more precise style injections through classNames and styles attributes, akin to Headless UI [10][11]. - This flexibility enables developers to easily customize components without relying on complex CSS selectors, enhancing UI personalization [13]. Group 3: Support and Compatibility - Ant Design 6.0 has made a bold decision to completely remove support for Internet Explorer, which may impact teams maintaining legacy projects [14][15]. - The minimum required version of React has been raised to React 18, which streamlines the library and reduces the burden of polyfills and hacks for outdated browsers [15]. Group 4: New Features and Tools - The simultaneous release of Ant Design X 2.0 introduces AI-focused interaction logic, catering to the evolving needs of front-end development as it shifts towards AI interfaces [16]. - This new version aims to simplify the integration of AI functionalities into B-end products, reflecting the industry's transition from traditional CRUD systems [16]. Group 5: Upgrade Recommendations - For users of version 5, a direct upgrade to version 6 is recommended due to promised smooth migration and immediate performance benefits [17]. - Users of version 4 should consider transitioning to version 5 first, as version 6 has removed deprecated APIs, making it a more challenging upgrade [17]. - Teams still maintaining IE projects are advised to remain on version 5, which will continue to receive maintenance support for one year [17].