201–210 of 216 posts
Earlier quoted context omitted.
Is Electron the baseline to compare to these days, instead of an actual native app?
I meant Electron brought webapps to the Desktop. Now Web Assembly seems to bring native apps to the browser.
Earlier quoted context omitted.
It's mostly written in C++, and the bulk of the effort which made this possible should probably be credited to Qt: https://wiki.qt.io/Qt_for_WebAssembly
Qt clearly deserves the credit for having a WASM runtime that gets us a working GUI toolkit. But this was still a gigaton of work to pull off inside LibreOffice (starting many years ago, actually natively using Qt as one of the GUI toolkits in the code, over to porting the build system, how the mainloop runs etc etc). Also note that using Qt here is mostly a shortcut to get a demo out, longer-term we'd want to use na…
You're welcome. :) What version of Qt did you use for this demo? Also, for local system file access dialog on Qt wasm, you can use https://doc.qt.io/qt-6/qfiledialog.html#getOpenFileContent
Earlier quoted context omitted.
Qt clearly deserves the credit for having a WASM runtime that gets us a working GUI toolkit. But this was still a gigaton of work to pull off inside LibreOffice (starting many years ago, actually natively using Qt as one of the GUI toolkits in the code, over to porting the build system, how the mainloop runs etc etc). Also note that using Qt here is mostly a shortcut to get a demo out, longer-term we'd want to use na…
> Qt clearly deserves the credit for having a WASM runtime that gets us a working GUI toolkit. You're welcome. :) What version of Qt did you use for this demo? Also, for local system file access dialog on Qt wasm, you can use https://doc.qt.io/qt-6/qfiledialog.html#getOpenFileContent
Earlier quoted context omitted.
No. I wouldn't want to inflict that upon anyone. I'm more bummed that I let the domains expire, especially the short one which was o-w.com.
> I'm more bummed that I let the domains expire, especially the short one which was o-w.com. It's ironic that you could've made more money than you would have gotten from VCs with that domain name. You probably didn't know that back then.
I'd have been a millionaire many times over if I could have read the future. All those Bitcoins I mined in early 2010 and lost all the keys/wallet.
Earlier quoted context omitted.
Makes me wonder if it is possible/usefull to make the download a two step process, first download a small wasm bittorrent client, then use it to download (and share) the 300mb file.
Webtorrent already exists, and does not require wasm. https://github.com/webtorrent/webtorrent
Now make firefox run inside my edge browser using wasm
Earlier quoted context omitted.
> I'm more bummed that I let the domains expire, especially the short one which was o-w.com. It's ironic that you could've made more money than you would have gotten from VCs with that domain name. You probably didn't know that back then.
Ha, no. 3 letter dotcoms were still worthless in 1998, I don't think they were quite all used up. Especially ones with a hyphen in them. Going back to 1994 I owned a whole bunch of domains that later got sold for 7 digits. All dotcoms were free in 1994. It was later they started charging for them, so I let them all expire. I'd have been a millionaire many times over if I could have read the future. All those Bitcoins…
Earlier quoted context omitted.
Indeed, people have got used to running their stuff on other people's machines.
TBH, "In a browser" (like here) is pretty different from "on the Internet" (like google docs). Except that if someone was to make slight changes to the hosted application, it could leak everything.
I remember when LibreOffice was called Star Office and would run like molasses on a Celeron 300A OC to 450mhz machine. The office suite would take up most of the ram and eventually crash due to system resource exhaustion. Now we can run the whole thing in a browser like it's Minesweeper. Wow.
... and it's as slow as on the Celeron! I guess it doesn't crash my entire machine, but that's an implementation detail which we'll surely workaround next.