News for hackers. Stuff that matters.
Re:Ruby on WebAssembly by robotmay on Sunday April 29, 2018 @01:49PM (#16953041)
JavaScript isn't everyone's cup of tea, and performance isn't always a huge concern :)

The more other languages I learn, the more often I come back to Ruby. I'm excited to see it becoming a more portable language, and I think it'll make a good language for web clients someday.

Re:Ruby on WebAssembly by untog on Sunday April 29, 2018 @03:34PM (#16953518)
> performance isn't always a huge concern :)

This is what concerns me a little with WASM. There are already too many web development experiences that prioritise developer experience and neglect user experience, I'm wondering what future we're walking into where we bundle three different standard libraries, ignore binary size, etc etc

Re:Ruby on WebAssembly by morgancmartin on Sunday April 29, 2018 @04:49PM (#16953847)
I've never understood this take on things, though I'm ready to if it can be explained to me. :)

To me, it seems that the user experience vs dev experience trade off is subject to market forces and if it swings too wildly in either direction, a competitor will come through and wipe the floor with everyone else, no? It's always seemed unnecessary to me to worry about the effects of _more_ options, at least in the context of application development anyway.

Re:Ruby on WebAssembly by CyberDildonics on Sunday April 29, 2018 @02:13PM (#16953164)
Again, all the IO still has to be done in javascript, you can only do raw processing in web assembly right now.

If you try to write the web assembly part in ruby, you are sending your users a run time and using an interpreter that is itself being JITed, purely to transform some amounts of data between IO from the user, including any information to and from the DOM.