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

LibreOffice running natively in the browser via WebAssembly

lab.allotropia.de

Post reply on HN
Print view View original

151–160 of 216 posts

Re: LibreOffice running natively in the browser via WebAssembly

#152

Post by wtetzner »

amelius wrote: post #143
jeroenhd wrote: post #115

Earlier quoted context omitted.

It runs relatively well in Firefox on Android, though the UI latency is a bit higher than using the Chromium engine. If Firefox fails, you should check your privacy/scripting settings, because it's working fine for me even with privacy-preserving addons installed. Of note is that if you're on iOS, all browsers must use Safari as a rendering engine by Apple's decree, so any browser you try is actually just Safari with…

> This means you can't run this on iOS, due to Apple's WASM size restrictions, regardless of the browser you try. What is this? I paid for x GB of RAM and now Apple prevents me from using it? Edit: abstracted away actual memory size.

128GB of RAM on iOS?

Re: LibreOffice running natively in the browser via WebAssembly

#153

Post by cprecioso »

iSnow wrote: post #129
apexalpha wrote: post #125

Earlier quoted context omitted.

I meant Electron brought webapps to the Desktop. Now Web Assembly seems to bring native apps to the browser.

So the next step would be to write "electron-browserify.js" which emulates a JS runtime in browser so you can run Electron apps remote.

I can’t really remember who but some months ago a coding scratchpad website launched full virtualized Linux environments in the browser through WASM, you could run Node on it.

Re: LibreOffice running natively in the browser via WebAssembly

#154

Post by tmpfs »

Abishek_Muthian wrote: post #37

I started experimenting with Go-WASM recently and learnt that writing non-blocking code is very crucial, Timer even inside a Goroutine blocks & crashes WASM. Leading me to use unreliable JS timers(albeit mitigating it with a worker) and performing only non-blocking compute on WASM. Is this just a consequence of using Go for WASM(i.e. lack of WASM threads), What are people who built LibreOffice in WASM or Doom3 using?…

This doesn't sound right to me, are you running your WASM in a worker so it doesn't block the main UI thread?

Re: LibreOffice running natively in the browser via WebAssembly

#157

Post by kroltan »

sgjohnson wrote: post #97
deathanatos wrote: post #41

Earlier quoted context omitted.

300 MiB. & … "a bit" — it takes nearly 20 seconds on "Gigabit" fiber. (312 MiB in 19.22s, or 136 Mbps.) Runs shockingly smoothly once it starts, though.

> Runs shockingly smoothly once it starts, though. On what hardware? I've got a 2019 MacBook Pro with i9 and 32 GB of RAM, and there's a noticable delay (I'd guess 200~400-ish miliseconds) when clicking any elements with Firefox or Chrome.

Same on a very beefy desktop Windows system.

Re: LibreOffice running natively in the browser via WebAssembly

#158

Post by jackson1442 »

amelius wrote: post #143
jeroenhd wrote: post #115

Earlier quoted context omitted.

It runs relatively well in Firefox on Android, though the UI latency is a bit higher than using the Chromium engine. If Firefox fails, you should check your privacy/scripting settings, because it's working fine for me even with privacy-preserving addons installed. Of note is that if you're on iOS, all browsers must use Safari as a rendering engine by Apple's decree, so any browser you try is actually just Safari with…

> This means you can't run this on iOS, due to Apple's WASM size restrictions, regardless of the browser you try. What is this? I paid for x GB of RAM and now Apple prevents me from using it? Edit: abstracted away actual memory size.

The most expensive iPhone 13 models ship with 6GB of RAM.

Re: LibreOffice running natively in the browser via WebAssembly

#159

Post by GeorgeHahn »

dspillett wrote: post #131
mofosyne wrote: post #126

Earlier quoted context omitted.

Does make you wonder what other optimization can be done. Maybe the whole thing doesn't have to be loaded in immediately.

Such lazy loading might be difficult to retrofit into an application designed for an environment where it can load a lot from disk to RAM quickly and has never (IME) been well design in terms of such resource use. Some lazy loading could probably be done relatively easily where OO does on-demand load libraries, but that would significantly resource apparent in-use performance if truly done live so you'd want to backg…

Autodesk has shared some information about how they solved this when building AutoCAD Web, which is a wasm app derived from their desktop codebase.

Video: https://www.infoq.com/presentations/autocad-webassembly/

Re: LibreOffice running natively in the browser via WebAssembly

#160

Post by jfk13 »

fouc wrote: post #111

I wonder if title should say "in Chromium-based browsers" rather than "in the browser". Especially when it doesn't run in Firefox or Safari.

In Firefox 97 on Windows, I repeatedly got "this page is slowing down your browser"; but in Firefox Nightly (99) it's amazingly smooth.
Post reply on HN