I work with emscripten and webgl and this looks like a fantastic tool for optimization in particular. Really looking forward to using it. Thank you!
How much optimiztion can you squeeze out of webgl + wasm? Don’t you still have to call into JS?
Sneak Peek at WebAssembly Studio
11–20 of 103 posts
Re: Sneak Peek at WebAssembly Studio
#12I came here to complain about it being yet another standalone app. I came back, after RTFA, to say that I'm pleasantly surprised that it runs completely in the web browser. https://webassembly.studio/
Really nice.
I like these new in-browser IDEs.
They often bring a full-fledged build system with them.
Just open the URL, write your code, hit compile and download your build.
Re: Sneak Peek at WebAssembly Studio
#13I came here to complain about it being yet another standalone app. I came back, after RTFA, to say that I'm pleasantly surprised that it runs completely in the web browser. https://webassembly.studio/
This is how it should be, if one wants to build an application out of the Web stack, then please use the browser I already have installed and provide the best UI/UX within those constraints.
Re: Sneak Peek at WebAssembly Studio
#14not bad, but four(4) config files for a single code file?
Where do you see 4? I see package.json only. Arguably the build script. And that number doesn't increase at all with more code. The number of files is exactly the same as if you weren't using webassembly, other than the one rust/c source file.
On AssemblyScript I see:
- tsconfig.json
- gulpfile.js
- package.json
- setup.js
Re: Sneak Peek at WebAssembly Studio
#15I came here to complain about it being yet another standalone app. I came back, after RTFA, to say that I'm pleasantly surprised that it runs completely in the web browser. https://webassembly.studio/
Funny. I came here to complain that it's not a standalone app and yet another crappy browser app.
I also would prefer standalone apps, but if my choice is between a browser app and a "standalone app" made with electron, the browser app wins in a landslide.
Re: Sneak Peek at WebAssembly Studio
#16I have to say I am pretty excited about WebAssembly. I've been through many programming languages. C# might be my favourite and F# always seemed like it would be if I took the time to learn it properly but for quite a few years now, JS has simply had such gravitational pull that I felt like I had to go with it. And I have to say, I've learned to not only like but to love it. Save for the mutable data structures that…
> Or, easliy write different packages in different languages and combine them into one app.
Just because the binary format can be shared doesn't mean code easily can. There's a tradeoff between requiring lots of glue or sharing a common lib across the langs. Either way, in WASM's current state, only the raw memory is shared and the only types are numeric primitives that can be used to address that memory. How each language lays out, for example, strings may be incompatible and most of the time where I've had to combine WASM libs for things like strings, there is a fallback to C-style (null-term'd or passing the length around).
So, while the common binary format will help open new architectures to existing langs, combining code from different langs still requires manual work and may be underperforming due to requiring they speak to each other in the lowest common denominator of raw byte arrays. Maybe some group will step up and federate a new libc for the WASM generation (even if there's no code and it only defines memory layouts). Even other proposals (GC w/ records/structs, host binding, ref types, etc) that bring higher level features don't necessarily solve interoperability issues.
Re: Sneak Peek at WebAssembly Studio
#17I came here to complain about it being yet another standalone app. I came back, after RTFA, to say that I'm pleasantly surprised that it runs completely in the web browser. https://webassembly.studio/
This is how it should be, if one wants to build an application out of the Web stack, then please use the browser I already have installed and provide the best UI/UX within those constraints.
You've clearly never tried to support more than one browser.
That's the big benefit of Electron packing its own browser: you know exactly what engine it's running in and which version of said engine. It's not dependent on what the user wants to use, the last time they updated it, etc.
Are there downsides? Sure, but the upsides vastly outweigh them for most users.
Re: Sneak Peek at WebAssembly Studio
#18I think WebAssembly is one of the most exciting efforts for the web right now, second maybe only to Houdini or IPFS.
I say that even as someone who works pretty much exclusively in Javascript now and who loves the language - a lower level format will be great for everyone. I can't wait for more native languages to start supporting it.
Re: Sneak Peek at WebAssembly Studio
#19I think WebAssembly is one of the most exciting efforts for the web right now, second maybe only to Houdini or IPFS. I say that even as someone who works pretty much exclusively in Javascript now and who loves the language - a lower level format will be great for everyone. I can't wait for more native languages to start supporting it.
Can someone link Houdini that OP is referring to? I'm having trouble finding it without context due to the ambiguous name
edit: is it this? https://github.com/w3c/css-houdini-drafts/wiki
Re: Sneak Peek at WebAssembly Studio
#20_Started_ working on it late December? That's an incredible amount of progress for less than 4 months.