Isomorphic JavaScript - Revision history

Wavesmiley at 20:36, 12 November 2024

2024-11-12T20:36:23Z

← Previous revision		Revision as of 20:36, 12 November 2024
Line 8:		Line 8:

	== Frameworks ==		== Frameworks ==
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [http://haskell-miso.org/ Miso] and [[Meteor (web framework)\|Meteor]] (framework). Others include [~~https://nextjs.org/~~ Next.js], [~~https://nuxtjs.org/~~ Nuxt], [https://kit.svelte.dev/ Sveltekit], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [http://haskell-miso.org/ Miso] and [[Meteor (web framework)\|Meteor]] (framework). Others include [[Next.js]], [[Nuxt]], [https://kit.svelte.dev/ Sveltekit], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}

	==References==		==References==

Northern Moonlight: Removing unsourced content, original research

2024-10-27T22:24:43Z

Removing unsourced content, original research

← Previous revision		Revision as of 22:24, 27 October 2024
Line 3:		Line 3:

	'''Isomorphic JavaScript''', also known as '''Universal JavaScript''', describes [[JavaScript]] applications which run both on the [[Client (computing)\|client]] and the [[Server (computing)\|server]].		'''Isomorphic JavaScript''', also known as '''Universal JavaScript''', describes [[JavaScript]] applications which run both on the [[Client (computing)\|client]] and the [[Server (computing)\|server]].

	== Mechanism ==
	Isomorphic JavaScript works in the context of a [[single-page application]] (SPA). In a typical SPA, most of the application logic, including [[Web framework#URL mapping\|routing]], is encapsulated in a bundled JavaScript file that is sent to the client. While this frees up the server, as it does not have to handle so many requests, it also makes the initial load slow for the client, as the entire application needs to be sent over to the client.

	With Isomorphic JavaScript, when a client web page is first requested from the server, the view of the page is generated on the server, similar to [[Dynamic web page#Server-side scripting\|server-side dynamic web pages]], and sent over to the client. The client can then render the view immediately. After the initial view is rendered, the complete SPA is downloaded in the background, and subsequent actions are handled client-side.

	== Name ==		== Name ==
	The naming of the term 'Isomorphic JavaScript' has been a matter of controversy.<ref name=":0">{{Cite web\|url=http://2ality.com/2015/08/isomorphic-javascript.html\|title=Is "Isomorphic JavaScript" a good term?\|website=2ality\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621091912/http://2ality.com/2015/08/isomorphic-javascript.html\|archive-date=2017-06-21\|url-status=live}}</ref> The term 'isomorphic' was first coined by Charlie Robbins from [[Nodejitsu]], in one of the company's blog posts.<ref>{{Cite web\|url=https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|title=Scaling Isomorphic Javascript Code {{!}} Nodejitsu Inc.\|last=Inc.\|first=Nodejitsu\|website=blog.nodejitsu.com\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170703210112/https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|archive-date=2017-07-03\|url-status=live}}</ref> Spike Brehm, a software engineer from [[Airbnb]], wrote another blog post using the same term.<ref>{{Cite web\|url=https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|title=Isomorphic JavaScript: The Future of Web Apps\|last=AirbnbEng\|date=2013-11-11\|website=Airbnb Engineering & Data Science\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170617233510/https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|archive-date=2017-06-17\|url-status=live}}</ref> However, others have proposed to use the term Universal JavaScript instead.<ref name=":0" /><ref>{{Cite web\|url=https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|title=Universal JavaScript\|date=2015-06-08\|website=Michael Jackson\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621140654/https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|archive-date=2017-06-21\|url-status=live}}</ref><ref>{{cite web\|url=https://learnshareit.com/javascript-dates/\|title=Javascript Dates}}</ref>		The naming of the term 'Isomorphic JavaScript' has been a matter of controversy.<ref name=":0">{{Cite web\|url=http://2ality.com/2015/08/isomorphic-javascript.html\|title=Is "Isomorphic JavaScript" a good term?\|website=2ality\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621091912/http://2ality.com/2015/08/isomorphic-javascript.html\|archive-date=2017-06-21\|url-status=live}}</ref> The term 'isomorphic' was first coined by Charlie Robbins from [[Nodejitsu]], in one of the company's blog posts.<ref>{{Cite web\|url=https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|title=Scaling Isomorphic Javascript Code {{!}} Nodejitsu Inc.\|last=Inc.\|first=Nodejitsu\|website=blog.nodejitsu.com\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170703210112/https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|archive-date=2017-07-03\|url-status=live}}</ref> Spike Brehm, a software engineer from [[Airbnb]], wrote another blog post using the same term.<ref>{{Cite web\|url=https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|title=Isomorphic JavaScript: The Future of Web Apps\|last=AirbnbEng\|date=2013-11-11\|website=Airbnb Engineering & Data Science\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170617233510/https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|archive-date=2017-06-17\|url-status=live}}</ref> However, others have proposed to use the term Universal JavaScript instead.<ref name=":0" /><ref>{{Cite web\|url=https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|title=Universal JavaScript\|date=2015-06-08\|website=Michael Jackson\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621140654/https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|archive-date=2017-06-21\|url-status=live}}</ref><ref>{{cite web\|url=https://learnshareit.com/javascript-dates/\|title=Javascript Dates}}</ref>

	== Benefits ==
	* Better user experience: By rendering important parts of the application with the real data on the server-side, an isomorphic application can show a meaningful initial page. On the other hand, client rendering application can’t show any meaningful information until it fetches all external data it needs. In the meantime, the only thing a user will see is a loading indicator.
	* Faster overall loading time: Although an isomorphic application will be slower in responding an initial page compared to a client rendering application (as it fetches data and renders more markups on the server-side before responding), overall completion time to the final user interface is faster because data access on the server-side is much faster than client-side API requests.
	* More predictable SEO and Site Indexing: In order to index content that JavaScript apps render on client-side, Googlebot must run those JavaScript apps inside a full browser environment and capture the rendered DOM. This involves complex browser compatibility issues. Also, because JavaScript apps can make AJAX requests for further rendering, Googlebot must have a policy that controls apps’ network access. These are why getting your JavaScript app indexed properly by Googlebot is still challenging.

	== Frameworks ==		== Frameworks ==

Frost: Reverted edits by 31.94.10.115 (talk): unexplained content removal (HG) (3.4.12)

2024-10-10T13:44:23Z

Reverted edits by 31.94.10.115 (talk): unexplained content removal (HG) (3.4.12)

← Previous revision		Revision as of 13:44, 10 October 2024
Line 1:		Line 1:
	{{Short description\|JavaScript applications that run on both the client and server}}		{{Short description\|JavaScript applications that run on both the client and server}}
	{{distinguish\|Isomorphism}}		{{distinguish\|Isomorphism}}

			'''Isomorphic JavaScript''', also known as '''Universal JavaScript''', describes [[JavaScript]] applications which run both on the [[Client (computing)\|client]] and the [[Server (computing)\|server]].

	== Mechanism ==		== Mechanism ==

31.94.10.115 at 13:44, 10 October 2024

2024-10-10T13:44:01Z

← Previous revision		Revision as of 13:44, 10 October 2024
Line 1:		Line 1:
	{{Short description\|JavaScript applications that run on both the client and server}}		{{Short description\|JavaScript applications that run on both the client and server}}
	{{distinguish\|Isomorphism}}		{{distinguish\|Isomorphism}}

	'''Isomorphic JavaScript''', also known as '''Universal JavaScript''', describes [[JavaScript]] applications which run both on the [[Client (computing)\|client]] and the [[Server (computing)\|server]].

	== Mechanism ==		== Mechanism ==

199.27.253.189: /* Frameworks */

2024-03-18T04:46:25Z

Frameworks

← Previous revision		Revision as of 04:46, 18 March 2024
Line 18:		Line 18:

	== Frameworks ==		== Frameworks ==
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://kit.svelte.dev/ Sveltekit], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby~~], [http://haskell-miso.org/ Miso~~], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [http://haskell-miso.org/ Miso] and [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://kit.svelte.dev/ Sveltekit], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}

	==References==		==References==

Rublov: Adding local short description: "JavaScript applications that run on both the client and server", overriding Wikidata description "also known as Universal JavaScript, describes JavaScript applications which run both on the client and the server."

2024-02-29T00:22:17Z

Adding local short description: "JavaScript applications that run on both the client and server", overriding Wikidata description "also known as Universal JavaScript, describes JavaScript applications which run both on the client and the server."

← Previous revision		Revision as of 00:22, 29 February 2024
Line 1:		Line 1:
			{{Short description\|JavaScript applications that run on both the client and server}}
	{{distinguish\|Isomorphism}}		{{distinguish\|Isomorphism}}

1.168.234.167: /* Frameworks */ include sveltekit in the list

2024-02-13T21:52:04Z

Frameworks: include sveltekit in the list

← Previous revision		Revision as of 21:52, 13 February 2024
Line 17:		Line 17:

	== Frameworks ==		== Frameworks ==
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://kit.svelte.dev/ Sveltekit], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}

	==References==		==References==

BattyBot: Removed/fixed author parameter(s) to remove article from :Category:CS1 errors: generic name, performed general fixes

2024-01-31T04:15:03Z

Removed/fixed author parameter(s) to remove article from Category:CS1 errors: generic name, performed general fixes

← Previous revision		Revision as of 04:15, 31 January 2024
Line 9:		Line 9:

	== Name ==		== Name ==
	The naming of the term 'Isomorphic JavaScript' has been a matter of controversy.<ref name=":0">{{Cite web\|url=http://2ality.com/2015/08/isomorphic-javascript.html\|title=Is "Isomorphic JavaScript" a good term?\|website=2ality\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621091912/http://2ality.com/2015/08/isomorphic-javascript.html\|archive-date=2017-06-21\|url-status=live}}</ref> The term 'isomorphic' was first coined by Charlie Robbins from [[Nodejitsu]], in one of the company's blog posts.<ref>{{Cite web\|url=https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|title=Scaling Isomorphic Javascript Code {{!}} Nodejitsu Inc.\|last=Inc.\|first=Nodejitsu\|website=blog.nodejitsu.com\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170703210112/https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|archive-date=2017-07-03\|url-status=live}}</ref> Spike Brehm, a software engineer from [[Airbnb]], wrote another blog post using the same term.<ref>{{Cite web\|url=https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|title=Isomorphic JavaScript: The Future of Web Apps\|last=AirbnbEng\|date=2013-11-11\|website=Airbnb Engineering & Data Science\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170617233510/https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|archive-date=2017-06-17\|url-status=live}}</ref> However, others have proposed to use the term Universal JavaScript instead.<ref name=":0" /><ref>{{Cite web\|url=https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|title=Universal JavaScript~~\|last=Jackson\|first=Michael~~\|date=2015-06-08\|website=Michael Jackson\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621140654/https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|archive-date=2017-06-21\|url-status=live}}</ref><ref>{{cite web\|url=https://learnshareit.com/javascript-dates/\|title=Javascript Dates}}</ref>		The naming of the term 'Isomorphic JavaScript' has been a matter of controversy.<ref name=":0">{{Cite web\|url=http://2ality.com/2015/08/isomorphic-javascript.html\|title=Is "Isomorphic JavaScript" a good term?\|website=2ality\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621091912/http://2ality.com/2015/08/isomorphic-javascript.html\|archive-date=2017-06-21\|url-status=live}}</ref> The term 'isomorphic' was first coined by Charlie Robbins from [[Nodejitsu]], in one of the company's blog posts.<ref>{{Cite web\|url=https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|title=Scaling Isomorphic Javascript Code {{!}} Nodejitsu Inc.\|last=Inc.\|first=Nodejitsu\|website=blog.nodejitsu.com\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170703210112/https://blog.nodejitsu.com/scaling-isomorphic-javascript-code/\|archive-date=2017-07-03\|url-status=live}}</ref> Spike Brehm, a software engineer from [[Airbnb]], wrote another blog post using the same term.<ref>{{Cite web\|url=https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|title=Isomorphic JavaScript: The Future of Web Apps\|last=AirbnbEng\|date=2013-11-11\|website=Airbnb Engineering & Data Science\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170617233510/https://medium.com/airbnb-engineering/isomorphic-javascript-the-future-of-web-apps-10882b7a2ebc\|archive-date=2017-06-17\|url-status=live}}</ref> However, others have proposed to use the term Universal JavaScript instead.<ref name=":0" /><ref>{{Cite web\|url=https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|title=Universal JavaScript\|date=2015-06-08\|website=Michael Jackson\|access-date=2017-06-15\|archive-url=https://web.archive.org/web/20170621140654/https://medium.com/@mjackson/universal-javascript-4761051b7ae9\|archive-date=2017-06-21\|url-status=live}}</ref><ref>{{cite web\|url=https://learnshareit.com/javascript-dates/\|title=Javascript Dates}}</ref>

	== Benefits ==		== Benefits ==
Line 17:		Line 17:

	== Frameworks ==		== Frameworks ==
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{cn\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{citation needed\|date=April 2019}}

	==References==		==References==
	<references />		<references />



	[[Category:JavaScript]]		[[Category:JavaScript]]

DreamRimmer: Reverting edit(s) by 120.89.104.69 (talk) to rev. 1160928923 by --WikiUser1234945--: (RW 16.1)

2023-06-19T15:50:49Z

Reverting edit(s) by 120.89.104.69 (talk) to rev. 1160928923 by --WikiUser1234945--: (RW 16.1)

← Previous revision		Revision as of 15:50, 19 June 2023
Line 17:		Line 17:

	== Frameworks ==		== Frameworks ==
	To=build
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{cn\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{cn\|date=April 2019}}

120.89.104.69: /* Frameworks */Cht

2023-06-19T15:49:15Z

Frameworks: Cht

← Previous revision		Revision as of 15:49, 19 June 2023
Line 17:		Line 17:

	== Frameworks ==		== Frameworks ==
			To=build
	There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{cn\|date=April 2019}}		There have been several isomorphic JavaScript frameworks and libraries created, most notably [[Meteor (web framework)\|Meteor]] (framework). Others include [https://nextjs.org/ Next.js], [https://nuxtjs.org/ Nuxt], [https://rendrjs.github.io/ Rendr], [http://derbyjs.com/ Derby], [http://haskell-miso.org/ Miso], [http://ezeljs.com/ Ezel] and [https://catberry.github.io/ Catberry].{{cn\|date=April 2019}}