Original text
3.3 Use Code-Splitting Within Projects
Success Criterion - Code Splitting
Breakdown bandwidth-heavy components into segments that can be loaded as required.
Suggested text
3.3 Modularize Components Within Projects
This approach is applicable across various programming languages and platforms, both client-side and server-side. By modularizing code and assets, you can ensure faster load times, better resource management, and improved scalability for your application. Additionally, reducing unnecessary data transfer and optimizing load times can contribute to more energy-efficient operations, helping to lower the environmental impact, improve the UX of your web application or service.
Success Criterion - Modularize Components
Breakdown bandwidth-heavy components, frontend and backend side into smaller, modular segments that can be loaded only when required.
Reason
The guideline refers to "code-splitting" which is mainly associated with tools like Webpack and frameworks like Node.js, but the concept itself is broadly applicable to any language or framework that involves loading large assets or code. By thinking on server side and in language agnostic context, we can apply the same principle. Moreover, the core idea behind "code-splitting" is deeply rooted in the long-standing principles of modular programming, which have been around since the early days of computing (1950s). For example, languages like ALGOL and Pascal emphasized the use of procedures, functions, and modules to break down large programs into smaller, more manageable units. The goals were the same as today: improved code organization, performance, reusability, maintainability, and reduced complexity.
Original text
3.3 Use Code-Splitting Within Projects
Success Criterion - Code Splitting
Breakdown bandwidth-heavy components into segments that can be loaded as required.
Suggested text
3.3 Modularize Components Within Projects
This approach is applicable across various programming languages and platforms, both client-side and server-side. By modularizing code and assets, you can ensure faster load times, better resource management, and improved scalability for your application. Additionally, reducing unnecessary data transfer and optimizing load times can contribute to more energy-efficient operations, helping to lower the environmental impact, improve the UX of your web application or service.
Success Criterion - Modularize Components
Breakdown bandwidth-heavy components, frontend and backend side into smaller, modular segments that can be loaded only when required.
Reason
The guideline refers to "code-splitting" which is mainly associated with tools like Webpack and frameworks like Node.js, but the concept itself is broadly applicable to any language or framework that involves loading large assets or code. By thinking on server side and in language agnostic context, we can apply the same principle. Moreover, the core idea behind "code-splitting" is deeply rooted in the long-standing principles of modular programming, which have been around since the early days of computing (1950s). For example, languages like ALGOL and Pascal emphasized the use of procedures, functions, and modules to break down large programs into smaller, more manageable units. The goals were the same as today: improved code organization, performance, reusability, maintainability, and reduced complexity.