Replied in thread
I appreciate your genuine efforts, @jon, but #Vivaldi is still based on #Chromium… you are technically dependent on a browser engine maintained by #Google! What if all of a sudden they decide to close it? As improbable as it might sound, we are in an epoch of absolutely improbable stuff happening.
I thought about giving Vivaldi a try, but to be honest I was never interested in installing any browser that is not a #Firefox fork.
#FreeSoftware is not an extra added value, but something fundamentally relevant!
(I read your articles about the points I raised, but they are just technical and they gliss political and socio-economic aspects)
Vivaldi Browser · Built using Chromium, but different from Chrome | Vivaldi
More from 
Team Vivaldi
Calling all Chromium developers and fans! 
Payment via GitHub Sponsors. 
Minimal Linux OS runs in a 6MB PDF Document in Chrome.![If you wish to try out the LinuxPDF, it requires a Chromium-based browser to work correctly (I checked, but it didn't work in Firefox on PC).
On the topic of speed and efficiency, [Ading2210] humbly admits that performance might be the largest problem with LinuxPDF. "The Linux kernel takes about 30-60 seconds to boot up within the PDF, which [is] over 100x slower than normal," notes the developer. With Chrome's current PDF engine having its Just-in-Time (JIT) compiler disabled, [Ading2210] sees no way of speeding up the code, for now.](https://nerdculture.de/system/media_attachments/files/114/211/704/385/933/637/original/7142a6047423bdbc.jpeg "If you wish to try out the LinuxPDF, it requires a Chromium-based browser to work correctly (I checked, but it didn't work in Firefox on PC).
On the topic of speed and efficiency, [Ading2210] humbly admits that performance might be the largest problem with LinuxPDF. \"The Linux kernel takes about 30-60 seconds to boot up within the PDF, which [is] over 100x slower than normal,\" notes the developer. With Chrome's current PDF engine having its Just-in-Time (JIT) compiler disabled, [Ading2210] sees no way of speeding up the code, for now.")
![[ImageSource: Ading2210]
The TinyEMU RISC-V emulator runs in the PDF thanks to a technique where its code is compiled "using an old version of Emscripten that targets asm.js instead of WebAssembly." This is embedded and loads in the PDF, subsequently auto-running a minimal Linux kernel targeting that architecture.
In this implementation, once you agree to 'Start Emulator' in your browser, you will see the LinuxPDF UI load, and a welcome message in the Linux viewport, as you wait for the OS to boot.](https://nerdculture.de/system/media_attachments/files/114/211/705/349/712/707/original/513838969c81eb99.png "[ImageSource: Ading2210]
The TinyEMU RISC-V emulator runs in the PDF thanks to a technique where its code is compiled \"using an old version of Emscripten that targets asm.js instead of WebAssembly.\" This is embedded and loads in the PDF, subsequently auto-running a minimal Linux kernel targeting that architecture.
In this implementation, once you agree to 'Start Emulator' in your browser, you will see the LinuxPDF UI load, and a welcome message in the Linux viewport, as you wait for the OS to boot.")
![[ImageSource: Ading2210]
Below the Linux viewport in the PDF is a soft keyboard created by an array of PDF buttons. However, it is likely quicker for everyone with a decent physical keyboard to input commands into the 'type here for keyboard inputs' field to the lower right of the keyboard UI area.](https://nerdculture.de/system/media_attachments/files/114/211/706/326/556/776/original/9f7e2d1a8c32c083.png "[ImageSource: Ading2210]
Below the Linux viewport in the PDF is a soft keyboard created by an array of PDF buttons. However, it is likely quicker for everyone with a decent physical keyboard to input commands into the 'type here for keyboard inputs' field to the lower right of the keyboard UI area.")
«Deep link: qué es y cómo usarlo (incluso en Firefox)»
