Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #30449
| From | Aleksandro <aleksandro@gmx.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Node.js |
| Date | 2016-05-16 18:08 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <nhdg6r$nif$1@dont-email.me> (permalink) |
| References | <662bb095-fcbf-4eea-a597-07d07a7975e9@googlegroups.com> <7fab549c-269c-49ab-9b8d-45c30860f0f4@googlegroups.com> <2f390f05-400c-4d34-9e65-d5a066daaaed@googlegroups.com> <5lujjbdjstq25ar3hq92nvvlh6cpq73vif@4ax.com> <13691380.NLzAtpMErn@PointedEars.de> |
On 16/05/16 16:20, Thomas 'PointedEars' Lahn wrote: > Tim Slattery wrote: > >> jonas.thornvall@gmail.com wrote: >>> Are all .js files serverside "executed on server", i want clientside >>> "browser executed" javascript but i want to split the code/script >>> over several files, is that possible? >> >> All (or nearly all) javascript is shipped to the client and executed >> there. You can have various chunks of code in various *.js files on >> the server, so long as the HTML page references all of them. > > There are no “HTML pages” (this is an outdated concept that has always been > underdefined at best), and *client-side* script resources can now be loaded > *on demand* in a reliable, non-blocking, and standards-compliant way. [1] > (If ECMAScript implementations in Web browsers would also implement the > “export” and “import” features of ECMAScript 2015, we could be writing > script modules and have them loaded implicitly now instead of through > RequireJS [2] and similar libraries. [3]) > > Since the References header field is borken, presumably because Google > Groups borked the Message-ID, I cannot see if and how this pertains to > Node.js, which is a *server-side* environment based on Google V8 JavaScript > in that regard; Node.js modules are *never* “shipped to the client”. [4] > > The OP should read the FAQ and learn “How To Ask Questions The Smart Way”. > > The author of the precursor should read the FAQ, STFW, and update their > knowledge base before giving further advice. > > __________ > [1] <https://www.w3.org/TR/2014/REC-html5-20141028/scripting-1.html#the-script-element> > [2] <http://requirejs.org/> > [3] <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export> > [4] <https://nodejs.org/en/> As always, your daily doze of copypasta plus arrogance is always appreciated. ;)
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Node.js jonas.thornvall@gmail.com - 2016-05-16 08:49 -0700
Re: Node.js jonas.thornvall@gmail.com - 2016-05-16 09:00 -0700
Re: Node.js jonas.thornvall@gmail.com - 2016-05-16 09:19 -0700
Re: Node.js jonas.thornvall@gmail.com - 2016-05-16 09:41 -0700
Re: Node.js jonas.thornvall@gmail.com - 2016-05-16 09:46 -0700
Re: Node.js Tim Slattery <tim@risingdove.com> - 2016-05-16 12:53 -0400
Re: Node.js Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-05-16 22:20 +0200
Re: Node.js Aleksandro <aleksandro@gmx.com> - 2016-05-16 18:08 -0400
Re: Node.js Tim Streater <timstreater@greenbee.net> - 2016-05-16 23:16 +0100
Re: Node.js Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-05-17 08:01 +0200
Re: Node.js Aleksandro <aleksandro@gmx.com> - 2016-05-17 16:16 -0400
Re: Node.js DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-05-18 02:25 +0100
Re: Node.js Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-05-18 20:08 +0200
Re: Node.js Aleksandro <aleksandro@gmx.com> - 2016-05-18 14:54 -0400
Re: Node.js Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-05-19 06:55 +0200
Re: Node.js jonas.thornvall@gmail.com - 2016-05-17 00:35 -0700
Re: Node.js Aleksandro <aleksandro@gmx.com> - 2016-05-17 16:51 -0400
Re: Node.js Luuk <luuk@invalid.lan> - 2016-05-16 20:01 +0200
csiph-web