Comparison of JavaScript-based web frameworks - Revision history

The Anome: ES Modules

2025-03-28T14:34:58Z

← Previous revision		Revision as of 14:34, 28 March 2025
Line 167:		Line 167:

	== High-level framework comparison ==		== High-level framework comparison ==
	JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including [[Web Components]], modern JavaScript APIs like [[Fetch API\|Fetch]] and [[ES Modules]], and browser capabilities like [[Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>		JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including [[Web Components]], modern JavaScript APIs like [[Fetch API\|Fetch]] and [[ECMAScript Modules\|ES Modules]], and browser capabilities like [[Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as [[Svelte]] and [[Preact]], take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as [[Svelte]] and [[Preact]], take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />

The Anome: /* High-level framework comparison */ linking

2025-03-28T14:33:18Z

High-level framework comparison: linking

← Previous revision		Revision as of 14:33, 28 March 2025
Line 167:		Line 167:

	== High-level framework comparison ==		== High-level framework comparison ==
	JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>		JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including [[Web Components]], modern JavaScript APIs like [[Fetch API\|Fetch]] and [[ES Modules]], and browser capabilities like [[Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as [[Svelte]] and [[Preact]], take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />

	A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|website=[[GitHub]] \|url=https://github.com/enhance-dev }}</ref><ref>{{Cite web \|title=Astro framework \|website=[[GitHub]] \|url=https://github.com/withastro/astro }}</ref><ref>{{Cite web \|title=Fresh \|website=[[GitHub]] \|url=https://github.com/denoland/fresh }}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":02" /><ref name=":12" /><ref name=":22" />		A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|website=[[GitHub]] \|url=https://github.com/enhance-dev }}</ref><ref>{{Cite web \|title=Astro framework \|website=[[GitHub]] \|url=https://github.com/withastro/astro }}</ref><ref>{{Cite web \|title=Fresh \|website=[[GitHub]] \|url=https://github.com/denoland/fresh }}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":02" /><ref name=":12" /><ref name=":22" />

The Anome: /* High-Level Framework Comparison */ fmt heading

2025-03-28T14:31:22Z

High-Level Framework Comparison: fmt heading

← Previous revision		Revision as of 14:31, 28 March 2025
Line 166:		Line 166:
	\|}		\|}

	== High-~~Level~~ ~~Framework~~ ~~Comparison~~ ==		== High-level framework comparison ==
	JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>		JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>

87.252.254.43: /* Browser support */

2025-02-20T14:03:37Z

Browser support

← Previous revision		Revision as of 14:03, 20 February 2025
Line 1,023:		Line 1,023:
	\|-		\|-
	!{{rh}}\|[[Webix]]		!{{rh}}\|[[Webix]]
	\|<!-- MSIE --> 8+<ref name="webix.com">{{cite web\|url=https://docs.webix.com/desktop__compatibility.html\|title=Compatibility Webix Docs\|website=docs.webix.com}}</ref>		\|<!-- MSIE --> 11+<ref name="webix.com">{{cite web\|url=https://docs.webix.com/desktop__compatibility.html\|title=Compatibility Webix Docs\|website=docs.webix.com}}</ref>
	\|<!-- Firefox --> 3+<ref name="webix.com"/>		\|<!-- Firefox --> 93+<ref name="webix.com"/>
	\|<!-- Safari --> 4+<ref name="webix.com"/>		\|<!-- Safari --> 5+<ref name="webix.com"/>
	\|<!-- Opera --> 9+<ref name="webix.com"/>		\|<!-- Opera --> 95+<ref name="webix.com"/>
	\|<!-- Chrome --> 1+<ref name="webix.com"/>		\|<!-- Chrome --> 95+<ref name="webix.com"/>
	\|<!-- Edge -->		\|<!-- Edge --> 95+<ref name="webix.com"/>
	\|}		\|}

87.252.254.43 at 13:39, 20 February 2025

2025-02-20T13:39:08Z

← Previous revision		Revision as of 13:39, 20 February 2025
Line 154:		Line 154:
	\|-		\|-
	!{{rh}}\|[[Webix]]		!{{rh}}\|[[Webix]]
	\|<!-- Version --> 4.1<br />{{nowrap\|November ~~2016~~}}		\|<!-- Version --> 11.0<br />{{nowrap\|November 2024}}
	\|<!-- Size --> 188 kB (gzipped)		\|<!-- Size --> 188 kB (gzipped)
	\|<!-- License -->[[GPL]] & Commercial<ref>{{Cite web \|title=JavaScript UI Components Library Webix - Licenses \|url=https://webix.com/licenses/ \|access-date=2022-06-01 \|website=webix.com \|language=en}}</ref>		\|<!-- License -->[[GPL]] & Commercial<ref>{{Cite web \|title=JavaScript UI Components Library Webix - Licenses \|url=https://webix.com/licenses/ \|access-date=2022-06-01 \|website=webix.com \|language=en}}</ref>

Citation bot: Altered title. Add: website, publisher, date, authors 1-3. Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Software comparisons | #UCB_Category 60/101

2025-02-07T21:07:22Z

Altered title. Add: website, publisher, date, authors 1-3. Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Software comparisons | #UCB_Category 60/101

← Previous revision		Revision as of 21:07, 7 February 2025
Line 167:		Line 167:

	== High-Level Framework Comparison ==		== High-Level Framework Comparison ==
	JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>		JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949 \|last1=Uzayr \|first1=Sufyan bin \|last2=Cloud \|first2=Nicholas \|last3=Ambler \|first3=Tim \|date=November 2019 \|publisher=Apress }}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047 \|last1=Rojas \|first1=Carlos \|date=13 November 2020 \|publisher=Apress }}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098 \|last1=Scherer \|first1=Justin \|date=28 February 2020 \|publisher=Packt Publishing, Limited }}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />

	A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev ~~\|url-status=live~~}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro ~~\|url-status=live~~}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh ~~\|url-status=live~~}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":02" /><ref name=":12" /><ref name=":22" />		A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|website=[[GitHub]] \|url=https://github.com/enhance-dev }}</ref><ref>{{Cite web \|title=Astro framework \|website=[[GitHub]] \|url=https://github.com/withastro/astro }}</ref><ref>{{Cite web \|title=Fresh \|website=[[GitHub]] \|url=https://github.com/denoland/fresh }}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":02" /><ref name=":12" /><ref name=":22" />

	== Features ==		== Features ==
Line 720:		Line 720:
	\|<!-- React -->		\|<!-- React -->
	\|<!-- SproutCore --> {{yes}}		\|<!-- SproutCore --> {{yes}}
	\|<!-- Svelte --> {{yes}}<ref>{{cite web\|url=https://svelte.dev/docs/svelte/compiler-warnings#a11y_accesskey\|title=Compiler Warnings • Docs • Svelte}}</ref>		\|<!-- Svelte --> {{yes}}<ref>{{cite web\|url=https://svelte.dev/docs/svelte/compiler-warnings#a11y_accesskey\|title=Compiler Warnings • Docs • Svelte}}</ref>
	\|<!-- Vue -->		\|<!-- Vue -->
	\|<!-- ZK --> {{yes}}		\|<!-- ZK --> {{yes}}

99.28.156.162: /* Features */ add a little bit of info on Svelte, but more work should definitely be done

2025-01-26T00:44:02Z

Features: add a little bit of info on Svelte, but more work should definitely be done

← Previous revision		Revision as of 00:44, 26 January 2025
Line 368:		Line 368:
	\|<!-- React -->		\|<!-- React -->
	\|<!-- SproutCore --> {{yes}}<ref name="showcase.sproutcore.com">{{cite web\|url=http://showcase.sproutcore.com/#demos/Transition+Plugins\|title=Showcase\|website=showcase.sproutcore.com}}</ref>		\|<!-- SproutCore --> {{yes}}<ref name="showcase.sproutcore.com">{{cite web\|url=http://showcase.sproutcore.com/#demos/Transition+Plugins\|title=Showcase\|website=showcase.sproutcore.com}}</ref>
			\|<!-- Svelte --> {{yes}}<ref>{{cite web\|url=https://svelte.dev/docs/svelte/transition\|title=transition: • Docs • Svelte}}</ref>
	\|<!-- Svelte -->
	\|<!-- Vue -->		\|<!-- Vue -->
	\|<!-- ZK --> {{yes}}		\|<!-- ZK --> {{yes}}
Line 720:		Line 720:
	\|<!-- React -->		\|<!-- React -->
	\|<!-- SproutCore --> {{yes}}		\|<!-- SproutCore --> {{yes}}
			\|<!-- Svelte --> {{yes}}<ref>{{cite web\|url=https://svelte.dev/docs/svelte/compiler-warnings#a11y_accesskey\|title=Compiler Warnings • Docs • Svelte}}</ref>
	\|<!-- Svelte -->
	\|<!-- Vue -->		\|<!-- Vue -->
	\|<!-- ZK --> {{yes}}		\|<!-- ZK --> {{yes}}

Azarboon at 05:46, 22 January 2025

2025-01-22T05:46:49Z

← Previous revision		Revision as of 05:46, 22 January 2025
Line 14:		Line 14:
	<!-- section (such as the "References" section) will also be removed. -->		<!-- section (such as the "References" section) will also be removed. -->
	<!-- ====================================================================== -->		<!-- ====================================================================== -->
	This is a comparison of [[web framework]]s for [[front-end web development]] that are ~~heavily~~ reliant on [[JavaScript]] code for their behavior.		This is a comparison of [[web framework]]s for [[front-end web development]] that are reliant on [[JavaScript]] code for their behavior.

	==General information==		==General information==
Line 165:		Line 165:
	\|<!-- Language --> XML + Java (JavaScript optional)		\|<!-- Language --> XML + Java (JavaScript optional)
	\|}		\|}

			== High-Level Framework Comparison ==
			JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":02">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":12">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":22">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>

			Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":02" /><ref name=":12" /><ref name=":22" />

			A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev \|url-status=live}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro \|url-status=live}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh \|url-status=live}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":02" /><ref name=":12" /><ref name=":22" />

	== Features ==		== Features ==

GreenC bot: Rescued 2 archive links; reformat 1 link. Wayback Medic 2.5 per Category:All articles with dead external links

2025-01-17T06:36:14Z

Rescued 2 archive links; reformat 1 link. Wayback Medic 2.5 per Category:All articles with dead external links

← Previous revision		Revision as of 06:36, 17 January 2025
Line 198:		Line 198:
	\|<!-- Enyo -->		\|<!-- Enyo -->
	\|<!-- ExtJS --> {{yes}}<ref name="docs.sencha.com"/>		\|<!-- ExtJS --> {{yes}}<ref name="docs.sencha.com"/>
	\|<!-- GWT --> {{no}}<ref>{{cite web\|url=https://code.google.com/p/google-web-toolkit/source/browse/#svn/trunk/user/src/com/google/gwt/user/client/impl\|title=Google Code Archive - Long-term storage for Google Code Project Hosting.\|website=code.google.com}}</ref><ref>{{cite web\|url=https://www.google.com/support/forum/p/Google+Docs/thread?tid=72fe7b0e15737560&hl=en\|~~title=Google Groups\|website~~=google.com~~}}{{Dead link~~\|date=~~February~~ ~~2022~~ \|~~bot~~=~~InternetArchiveBot~~ \|~~fix-attempted~~=~~yes~~ }}</ref>		\|<!-- GWT --> {{no}}<ref>{{cite web\|url=https://code.google.com/p/google-web-toolkit/source/browse/#svn/trunk/user/src/com/google/gwt/user/client/impl\|title=Google Code Archive - Long-term storage for Google Code Project Hosting.\|website=code.google.com}}</ref><ref>{{cite web\|url=https://www.google.com/support/forum/p/Google+Docs/thread?tid=72fe7b0e15737560&hl=en\|archive-url=https://archive.today/20130505035218/http://www.google.com/support/forum/p/Google+Docs/thread?tid=72fe7b0e15737560&hl=en\|url-status=dead\|archive-date=5 May 2013\|title=Google Groups\|website=google.com}}</ref>
	\|<!-- jQuery --> {{yes}}<ref>{{cite web\|url=http://docs.jquery.com/Release:jQuery_1.3\|title=jQuery 1.3 Released - Official jQuery Blog\|first=jQuery Foundation -\|last=jquery.org\|website=docs.jquery.com\|date=14 January 2009 }}</ref>		\|<!-- jQuery --> {{yes}}<ref>{{cite web\|url=http://docs.jquery.com/Release:jQuery_1.3\|title=jQuery 1.3 Released - Official jQuery Blog\|first=jQuery Foundation -\|last=jquery.org\|website=docs.jquery.com\|date=14 January 2009 }}</ref>
	\|<!-- jQWidgets --> {{yes}}		\|<!-- jQWidgets --> {{yes}}
Line 791:		Line 791:
	\|<!-- Ember.js -->		\|<!-- Ember.js -->
	\|<!-- Enyo -->		\|<!-- Enyo -->
	\|<!-- ExtJS -->{{yes}}<ref>[http://dev.sencha.com/deploy/dev/docs/?class=Ext.chart.Chart Chart API]~~{{Dead link\|date=July 2020 \|bot=InternetArchiveBot \|fix-attempted=yes }}~~</ref>		\|<!-- ExtJS -->{{yes}}<ref>[https://archive.today/20120709235342/http://dev.sencha.com/deploy/dev/docs/?class=Ext.chart.Chart Chart API]</ref>
	\|<!-- GWT -->		\|<!-- GWT -->
	\|<!-- jQuery --> {{depends\|With plugin}}<ref>{{cite web\|url=http://www.flotcharts.org/\|title=Flot: Attractive JavaScript plotting for jQuery\|website=flotcharts.org}}</ref><ref>[http://www.filamentgroup.com/lab/jquery_visualize_plugin_accessible_charts_graphs_from_tables_html5_canvas/ jQuery Visualize Plugin] {{webarchive\|url=https://web.archive.org/web/20090709085716/http://www.filamentgroup.com/lab/jquery_visualize_plugin_accessible_charts_graphs_from_tables_html5_canvas \|date=9 July 2009 }}</ref>		\|<!-- jQuery --> {{depends\|With plugin}}<ref>{{cite web\|url=http://www.flotcharts.org/\|title=Flot: Attractive JavaScript plotting for jQuery\|website=flotcharts.org}}</ref><ref>[http://www.filamentgroup.com/lab/jquery_visualize_plugin_accessible_charts_graphs_from_tables_html5_canvas/ jQuery Visualize Plugin] {{webarchive\|url=https://web.archive.org/web/20090709085716/http://www.filamentgroup.com/lab/jquery_visualize_plugin_accessible_charts_graphs_from_tables_html5_canvas \|date=9 July 2009 }}</ref>

Uzume: consistent linking to Angular article throughout page

2024-11-27T08:51:18Z

consistent linking to Angular article throughout page

← Previous revision		Revision as of 08:51, 27 November 2024
Line 26:		Line 26:
	! Source language		! Source language
	\|-		\|-
	!{{rh}}\|[[Angular (~~application~~ ~~platform~~)\|Angular]]		!{{rh}}\|[[Angular (web framework)\|Angular]]
	\|<!-- Version --> 14.0.4<br />{{nowrap\|29 June 2022}}		\|<!-- Version --> 14.0.4<br />{{nowrap\|29 June 2022}}
	\|<!-- Size --> {{nowrap\|563 kB}} (minified & compressed)		\|<!-- Size --> {{nowrap\|563 kB}} (minified & compressed)