Elm and Web Components - Richard Feldman

[@nelsonc5339]

19:40 - where he describes the "Time Travelling Web Components" (_great talk as usual Richard!_)

[@hotscriptgg]

the best hairstyle ever in the front row :D

[@AdamSchelenbergCom]

Oh, man, I thought who the hell did a great job at NoRedInk. Great company, I'm using their services to up my English grammar )

[@Алексей-е9х5л]

How about ELM for PWA?!..

[@nikgraf6972]

I asked Richard on Twitter and it seems like not yet so far: twitter.com/rtfeldman/status/808837008005033984

[@Алексей-е9х5л]

Nik Graf Ask him about ELM roadmap! I can't find it..

[@nikgraf6972]

You can find it here: github.com/elm-lang/projects for the language itself

[@h3rteby]

All you need to be a "PWA" is a manifest.json and a service worker. There's not many differences from a plain website, you could easily do that with Elm. If you need some special features you can do with JS and ports.

[@shalokshalom]

@@h3rteby Like database?

[@LizardanNet]

no run-time exceptions = errors are swallowed

[@GagePeterson]

Elm (almost always) doesn't swallow errors, it actually requires you to handle them. You could just ignore them but you would have to do so knowingly. For instance, if you're getting the first element of the list it won't just give you the item or Null it will give you a `Maybe value` which requires you to write conditional logic around the "nothing there case" and the "something there" case to get the value out. Not doing so would not compile.