Conversation

Notices

1. Embed this notice
   anna (navi@social.vlhl.dev)'s status on Monday, 11-Nov-2024 08:41:23 JST anna

   in reply to

   • Julia :v_trans: :v_bi: (not cute)
   @julia the difference is making a web framework meant to be a web framework, and adding "web" as the target to your already existing library
   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Julia :v_trans: :v_bi: (not cute) (julia@eepy.moe)'s status on Monday, 11-Nov-2024 08:41:24 JST Julia :v_trans: :v_bi: (not cute)

     in reply to

     @navi@social.vlhl.dev most rust wasm web frameworks use the dom afaik- sycamore, leptos, yew, et al, but yeah most direct ports of native apps just use a canvas.

   • Embed this notice
     Julia :v_trans: :v_bi: (not cute) (julia@eepy.moe)'s status on Monday, 11-Nov-2024 08:41:25 JST Julia :v_trans: :v_bi: (not cute)

     in reply to

     Also the only use case for it would be rust web apps via wasm and I've come to realize that that isn't worth the trouble, web apps should be written in JS, maybe with some auxiliary parts in rust or C++ for performance reasons

   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Monday, 11-Nov-2024 08:41:25 JST anna

     in reply to

     • Julia :v_trans: :v_bi: (not cute)
     @julia every wasm webapp i see does that "make the whole site a canvas and just render to it" thing that completely ignores assistive tech because the html tree is basically empty
     
     i'd say this is common because it's the easy way to port desktop renderers to web, but it sucks
   • Embed this notice
     Julia :v_trans: :v_bi: (not cute) (julia@eepy.moe)'s status on Monday, 11-Nov-2024 08:41:26 JST Julia :v_trans: :v_bi: (not cute)

     I really want to figure out a means of doing efficient reactive computation at a low level in rust but low level and reactivity don't couple well