News for hackers. Stuff that matters.

A comment on Matestack – Reactive UIs in pure Ruby. Parent comment

Re:Matestack – Reactive UIs in pure Ruby by joelbluminator on Sunday November 22, 2020 @04:57AM (#25176255)
> streamed over a websocket

That's my problem with this approach, I wonder what the penalty is (performance and complexity wise) for going that route. What is it using for websockets btw, Action Cable?

[ Parent | on HN ]
Re:Matestack – Reactive UIs in pure Ruby by ksec on Monday November 23, 2020 @02:35AM (#25184389)
>What is it using for websockets btw, Action Cable?

And that is a problem because by default Action Cable isn't scalable. You cant get it work by 100 - 200 connection and response time are very slow at 50ms+ and a lot higher at 95th percentile. AnyCable helps a lot but this is another pieces of complexity added to the system.

Not a problem for Elixir and BEAM when they are sort of built for these type of workload.

Although I am waiting for all the Fibre, Async and Ractor addition to Ruby 3 and see how they add fit in.

[ Parent | on HN ]
Re:Matestack – Reactive UIs in pure Ruby by joelbluminator on Monday November 23, 2020 @04:36AM (#25185054)
> AnyCable helps a lot but this is another pieces of complexity added to the system.

What is the added complexity? I honestly never used all this stuff.

[ Parent | on HN ]