And a client that connects.

Klingel: Renlo, it would only be sent around interally to the page/app

Edinger: Compiling it should make it faster than reinterpriting it

Connel: Oh I misread that, the user / browser is going to be sent the source code

Crosland: Pastry: heuristics aren’t good enough.

Gavit: Pastry: ES6 modules are second-cl*** and limited exactly to avoid that problem

Sachse: Renlo:***embly/design/blob/master/

Byous: It will be important when it comes along

Pherson: Higuchi: only if you plan on writing compilers :

Kroesing: Renlo: not really for most people, no

Muschamp: Form data should just end up in an http request body right?

Lembke: Why’s that Dekok ? It seems to me that a lot of the internals of web apps will be web asm, and the ui will be the only js part

Banwell: For instance, where I work we do a lot of data processing, and some of that is done in the browser. it is relatively slow

Javier: Web asm is c code that compiles to specific js subset?

Berrett: Ah nvm I needed to use x-www-form-urlencoded

Pardieck: It is basically compiled code machine code which runs in a browser, i believe

Hanses: Renlo: WASM is just a tool for people who want to write efficient compilers for their programming languages. End users won’t see or write WASM.

Hazlett: Renlo: you’d, e.g.: use a C compiler that generates WASM code, just like you’d use a C compiler that generates x86 ***embly without having to know how x86 processors work

Wakley: Renlo: Web***embly is a binary AST format that will allow efficient compilation to web. Will Web***embly kill JS? See:***embly-make-JavaScript-skills-more-or-less-valuable-in-the-future/answer/Quildreen-Motta

Macksoud: Dekok: so it sounds like web asm has nothing to do with js

Lora: You write c that compiles to a specific byte code the browsers understand

Bramwell: Can websockets connect to regular non-“web server” servers?

Maze: Its not byte code, its ‘slim binaries’ / ‘binary AST’ apparently

Weingarten: So basically lets js do what you can already do in many laguanges, call some c functions for when you need it to be fast

Pexsa: Dekok, Isn’t WASM a subset of JS?

Pexsa: Oh. I’m I confusing it with asm.js then?

Servan: Phale: websockets can only connect to websocket servers.

Floan: I’m not entirely convinced by that Quora, in that it is a bit short-sighted; The answerer basically says it will be slower, but only now. In 10 years, all of the implementation issues will go away, WASM would be in every browser. It would therefore be a faster alternative to JS, which to me seems like it would be used more for *real* applications in a browser, like your ‘open office’ / ‘evernote’ / etc which runs in a browser

Ramstad: Dekok: so how can I connect to my python server instead?

Persico: Phale: you implement a websocket server in python

Csaszar: Renlo: sure, but we can’t really predict what will happen 10 or 20 years from now. Maybe the web will get faster. Maybe we’ll replace the web with something else entirely. Who knows?

Saavedra: Renlo: that answer was written by me btw

Moreta: Lol, didn’t see that at first

Hammerstrom: Aha, why cant javascript just have regular sockets

Kahrer: Phale: what you tryin to do

Mieszala: Phale: websockets are regular sockets. That follow a given communication protocol.

Eliades: Websockets run on tcp

Byro: Higuchi: well im running a TCP server on python atm

Kackley: Phale: there are probably many implementations of websockets in Python. You just need to pick one and use it

Shry: Phale: so you need a server that listens for web socket connections

Better: And a client that connects to servers via web sockets