Why was wasm used for this? It's not a javascript replacement as stated by webassembly.org.
Vim.wasm
161–170 of 291 posts
Re: Vim.wasm
#162Earlier quoted context omitted.
Both alternatives that I mentioned, Flash and PNaCL did have open source implementations available, it is just a matter of following the links I posted. WASM doesn't offer any security over internal data corruption as buffer access within linear memory aren't validated for data bounds or nullability. So it is possible, for a WASM module generated from C or C++ code, to provide input data to its functions in such a wa…
Wasm linear memory is a building block, if you want higher security boundaries, stitch together multiple Wasm envs and communicate via webworkers. Wasm is nearly identical, but different in the ways that matter. You are being blinded by being ahead of the curve, but the curve has moved now.
I am eagerly waiting for the first set of CVEs related to WASM, and the "you are holding it wrong" comments from WASM advocates.
Re: Vim.wasm
#163My test for "non-native" Vim is always 'q:' which should open a command line window of previous commands at the bottom of your screen - unfortunately that does not work. Furthermore I can't use 'Ctrl-v' that let's you select a column of text (EDIT: correction, this does work). 'q:' should not be captured by the browser? Nevertheless impressive work.
vi( vi' vi" also didn't work
Re: Vim.wasm
#164My test for "non-native" Vim is always 'q:' which should open a command line window of previous commands at the bottom of your screen - unfortunately that does not work. Furthermore I can't use 'Ctrl-v' that let's you select a column of text (EDIT: correction, this does work). 'q:' should not be captured by the browser? Nevertheless impressive work.
ctrl+v works fine for me (firefox windows)
It does not work for me on Firefox/Fedora (EDIT: it does). However 'q:' still does nothing.
Re: Vim.wasm
#165Where’s the escape key on my iPhone?
Where's the escape key on my Macbook Pro?
Re: Vim.wasm
#166Re: Vim.wasm
#167Earlier quoted context omitted.
The actual issue is that Windows and Linux don't properly use a ‘super’ key―while the ‘Win’ key is sitting there uselessly. Ironically, MS' own ‘ergonomic’ (cough) keyboards have gigantic Win keys, right under the thumbs which are the strongest digits. These keys are great to use on Mac, it's an eye-opener as to how the historical keyboard mutations ended up in just the wrong way for two platforms (and for Emacs). I…
I’d love to hear your take on the nonsensical shape and staggered key layout. Do you have suggestions for keyboards that do away with this? I have myself been looking at https://ergodox-ez.com/ but I’d love to hear of alternatives, especially if you have first hand experience on them.
Hi, I have experience both with the ergodox and the now-discontinued Truly Ergonomic Computer Keyboard™. The TECK honestly has a slightly better layout for me - the two halves are closer together and seem to fit my hands just a bit better. On the downside, the TECK's hardware quality was atrocious with keys double-pressing or missing presses after about a year of use. It also uses its own microcontroller with its own closed-source firmware so there's nearly no community around it. I'm not sure I can politely explain just how much the TECK fails.
The ErgoDox on the other hand has been a joy to use for approximately a year now and its design allowing for wasy swapping of keyswitches plus its open-source firmware mean I have limitless customisability and am not stuck using low-quality chinese cherry-mx clones (kailh). I hear they've actually improved now, but the ones in the TECK were definitely subpar.
I use a split ortholinear keyboard because a standard layout keyboard makes my fingers hurt after a while. ErgoDox and TECK(while it worked) were both good enough for mitigating my problems while not being as exotic and unwieldy as a kinesis.
I would love to try out a https://shop.keyboard.io/ once (hopefully) the price comes down a bit.
Re: Vim.wasm
#168On mobile I see a blank gray page. Perhaps this only works on desktop browsers. I still have no idea what it is.
Re: Vim.wasm
#169Earlier quoted context omitted.
At this point, the easier route to getting a text-based browser to support something like this would be creating a new one based on WebKit/Blink. It would probably need to get the engine to draw to a fake screen buffer and run an OCR algorithm over that. And even if the OCR and layout worked well, there would be a lot other work necessary to get reasonable text based interactivity, though that's probably partially so…
> OCR Hey, dial back the blasphemy there. HTML is not PDF, it's usually made from text in the first place. I'd guess you could force all text to use a monospace font, with fixed measures and line-height, and limit the width of the page. Then mostly dump the resulting text arrangement into the terminal. Now, layouts from the various elements and CSS are probably a lot trickier, but snapping all margins and padding to…
> Hey, dial back the blasphemy there. HTML is not PDF, it's usually made from text in the first place.
Hey, dial back the blasphemy there. PDF is not an image, it’s usually[0] made from text in the first place.
As someone who has a bunch of experience both creating and parsing PDFs, it’s definitely very doable to extract the text content and render it in a similar way on a terminal. Yes, parsing the PDF format is much more painful than average HTML, but these days there’s libraries commonly available to assist.
[0] unless the PDF is a famous redacted DOJ document, then it’s a poorly scanned collection of image crammed into a PDF container.
Re: Vim.wasm
#170Why was wasm used for this? It's not a javascript replacement as stated by webassembly.org.
Because it's a pure port of Vim, which is written in C.