# more above but I suppose not so much related but ask me if interested wagnerc: sometimes you'd setup ssi for cgi output too! that sounds terrifying and insecure not terribly hobbs: I don't think I've ever in my life been in a situation where I was responsible for deployments and there wasn't anything 'not normal' involved :P I remember when that was how you put a counter on your web page :D execute a C program. sim, CGI and then SSI?? > execute a C program. Hey, people are starting to that again! With webassembly this time, though wagnerc: yea, because the adserver stuff was all SSI based The Great Wheel turns inexoribly. But SSI is how we got PHP. :) * daxim has quit (Quit: WeeChat 2.3) also these days we have people serving up their entire app in a gig of client-side js :( i can't wait for WASI to really start getting it's feet on the ground. it'll make for some really interesting deployment stuff WASI? https://www.infoq.com/news/2019/04/wasi-wasm-system-interface and no that's not an april fools day joke Ok cool 'cause wikipediaing it brought me to Wechsler Abbreviated Scale of Intelligence Mozilla .NET :D wagnerc: basically :) once it gets further I'm *really* tempted to try to get perl running under it honestly webassembly sounds like java or silverlight but "This time it won't have all those security flaws because *we* made it" Why haven't you implemented Perl in JavaScript yet?? wagnerc: someone else beat me to it https://webperl.zero-g.net/ XD Will this initiative to run perl under wasm include getting xs modules to run under wasm 'cause that seems hard wasi will be a bit different PavelB: that'd be the idea, it should be doable I don't know how you can translate arbitrary C into WASM The way I see it you'd have to adapt the source of every XS module you want to use That doesn't look like a Perl implementation. It looks like a script server. http://blog.builtinperl.com/post/5-major-websites-that-use-perl wagnerc: it's a port of perl to WASM that then lets you use it as the scripting language for html PavelB: you can absolutely do C in WASM, that's kinda the point. there's a number of system interfaces (i.e. sockets, files, etc.) that need to exist to do any arbitrary stuff, and that's what WASI is intending to do. you probably wouldn't get things like mmap and other low-level system stuff but that's not a big deal * theory has quit (Quit: theory) There's C you've written to target WASM specifically, and there's arbitrary C they're the same WASM doesn't require special casing of things What happens if you try to dynamically link a library? that's not a C thing, that's a platform thing which is the kind of thing that WASI is targeting C itself doesn't know a damned thing about linking.