Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Popcorn: Run Elixir in WASM

popcorn.swmansion.com

Post reply on HN
Print view View original

1–10 of 31 posts

Re: Popcorn: Run Elixir in WASM

#5

Post by pesnk »

Congratulations on the project! It works great, until we need to handle the best part of Elixir, that's creating multiple actors.

This Task code, for example doesn't work.

  Enum.map(0..10, fn(_) ->
    Task.async(fn -> IO.puts("new process") end)
  end) |> Task.await_many()

Re: Popcorn: Run Elixir in WASM

#6

Post by Lord_Zero »

I'm honestly surprised at how slow WASM is moving. As a very experienced web dev, when I first learned about WASM I was sure people would be building production UIs in Python and Golang and other traditionally server-side languages.

Re: Popcorn: Run Elixir in WASM

#8

Post by Muromec »

Lord_Zero wrote: post #6

I'm honestly surprised at how slow WASM is moving. As a very experienced web dev, when I first learned about WASM I was sure people would be building production UIs in Python and Golang and other traditionally server-side languages.

Wasm doesn help much with UI, its more about moving parts of the server into the client as blacboxes with no access to dom.

The blackbox can of course return the state of UI to be rendered/pathced, but that doesnt unlock much (if any) interesting capabilities for amount of overhead it adds

Re: Popcorn: Run Elixir in WASM

#9

Post by eterm »

Lord_Zero wrote: post #6

I'm honestly surprised at how slow WASM is moving. As a very experienced web dev, when I first learned about WASM I was sure people would be building production UIs in Python and Golang and other traditionally server-side languages.

Well there's blazor, which does that rather well, but it's treated with the same suspicion that most MS frameworks are. The fear that it'll be killed for poor adoption, leading to poor adoption.

The blazor adoption probably isn't even that bad, but it's hard for MS to shake this stigma since so many people got burned on Silverlight and don't ever want to make the same mistake.

Re: Popcorn: Run Elixir in WASM

#10

Post by throwawaymaths »

eterm wrote: post #9
Lord_Zero wrote: post #6

I'm honestly surprised at how slow WASM is moving. As a very experienced web dev, when I first learned about WASM I was sure people would be building production UIs in Python and Golang and other traditionally server-side languages.

Well there's blazor, which does that rather well, but it's treated with the same suspicion that most MS frameworks are. The fear that it'll be killed for poor adoption, leading to poor adoption. The blazor adoption probably isn't even that bad, but it's hard for MS to shake this stigma since so many people got burned on Silverlight and don't ever want to make the same mistake.

I thought blazor failed because people didn't like websites that take minutes to load up all the websites assets. I'm not sure why, it could be:

- Technical issue with blazor performance or blazor makes perf regressions hard to fix

- blazor technical framework encourages programming style that is bad for perf

- blazor or blazor ecosystem attracts programmers that can't deal with perf issues

Post reply on HN