vimslayer

Isn't qt webkit what the infamous pgAdmin 4 used to use? shivers

Most compilers that target WebAssembly can also target asm.js, which is compatible with IE.

AFAIK it's more about missing stuff like DOM access and GC that stands in the way.

Indeed, JS does not have classical inheritance. IMO introducing a class syntax that looks so much like the classes from other languages and yet behaves differently was a mistake.

The rest of your comment sounds a bit misinformed to me. You seem to have decided that prototypical inheritance is somehow inherently worse than classical inheritance, but don't mention why that would be. I have found very little practical difference between the classes in JS and other languages in everyday use, and can't quite imagine what the problems with it might be.

Furthermore, ES6 (ES2015) is not a "transpiled language". I think it's obvious that if you take a very new language, say, ES2018 and want to run it on your toaster that doesn't have support for such new languages, you are going to have to do some kind of precompilation step. That is true for ES2018 today and it will be true for ES2019 next year and for ES2020 the year after that.

ES2015, however, has been around for several years. All the modern browsers (that is, all major browsers except IE) support it already. Node 10 even supports the new module loading syntax (behind a flag), or you can use a very lightweight transformer like esm[1] for older Node versions.

And if you do end up using and having problems with, say, Babel, it would be more constructive to give concrete examples of the issues you've had. I personally have never faced a syntax problem where the issue would've been due to a bug in Babel instead of just my incorrect understanding of the language feature.

[1]: https://github.com/standard-things/esm

Yep, works well now.

The page load speed is seriously impressive, congrats!

There's something weird going on with the styling of the dropdowns, though: https://i.imgur.com/WQ3m52X.gif

I'm on Windows 10 & Chrome

It looks even worse on mobile https://i.imgur.com/EOm3D4Y.png

I also don't think the JS is that bad here, the site loaded pretty fast for me even when I tested with a slow 3G network. But yeah that UI doesn't give a good reading experience.

But IDB follows the same-origin policy, so you can't share the cached runtime between different apps.

At least not unless you can load it from the same public CDN.

Edit: Actully, I'm not sure you could do that even with the public CDN.

Definitely not, but the original commenter was looking for any purely functional programming language, not necessarily one with dependent types. I think we are years away from having an easily comprehensible and usable dependent type system, if it's even possible to have one.

Obviously, not all railways are like Promises (they don't need to be async) but Promises are kind of railways, as the parent commenter said.

Not sure what you mean by "recursively build up and tear down" but this JS snippet sure looks a lot like the F# one in the slides

  const updateCustomerWithErrorHandling = (...args) =>
    receiveRequest(...args)
      .then(validateRequest)
      .then(canonicalizeEmail)
      .then(updateDbFromRequest)
      .then(sendEmail)
      .then(handleSuccess, handleError)

Here, each of the functions can return a result (async or not) or reject with Promise.reject or by throwing. If any of the functions rejects, the rest of the functions in this "happy path" are not called.