impermalink VS pyodide

https://impermalink.spiffy.tech - Save Links for Later. Optimized for a triage-save-read-trash loop.

I'm a long-time Instapaper/Pocket/Wallabag user. I love scanning my RSS feeds, saving links into those, and clicking 'mark all as read'. Then, when I have some downtime, I pore over all the interesting articles/videos I saved. I always have something interesting to read, and I can read it with focus, not doomscrolling and hoping to luck into something good.

But Instapaper et al. aren't built for the way I use them. I put a link in, read it, and delete it. No tagging, no archiving. I usually don't even want text extraction. I just want to read something interesting, then I'm done with it. I can bookmark the link in my browser if I really want to.

Also, I want to open HN/Reddit/YouTube links in their native mobile apps. Instapaper/Wallabag make that clumsy, Pocket makes it almost impossible. These apps also have bugs with sync, but I don't care about offline access, so why am I paying the cost for buggy offline sync I don't use?

Impermalink is designed to streamline my workflow. You can share to it from other apps. When you click a link to open it, it's marked for deletion and will disappear the next time you click another link. You can rescue a link from the recycle bin. Links are grouped by domain, so it's easy to lump all those YouTube videos under a collapsed header so you can focus on other content. Links are just links - your browser will open them however it's normally configured to, including opening them in native apps on mobile.

The app's condition is "rough and ready". It works enough that I use it every day and really enjoy it. The UX has obvious areas for improvement. The home page has no content. Svelte has bugs that double-render some of the content sometimes. But it's there, and it works.

Give it a try, let me know what you think, [email protected]

Install the app to your home screen with Chrome on Android. Yes, Chrome, not anything else, not even Chrome derivatives. I haven't tried on iOS yet. You can use the app in any browser you want, but only Chrome on Android knows how to share links to web apps.

https://impermalink.spiffy.tech

https://github.com/spiffytech/impermalink

We implemented an in-browser Python editor/interpreter built on Pyodide over at Comet (our users are data scientists who need to build custom visualizations quite often, and the most familiar language for most of them is Python).

One of the issues you'll run into is that Pyodide only works by default with packages that have pure Python wheels available. The team has developed support for some libraries with C dependencies (like scikit-learn, I believe), but frameworks like PyTorch are particularly thorny (see this issue: https://github.com/pyodide/pyodide/issues/1625 )

We ended up rolling out a new version of our Python visualizations that runs off-browser, in order to support enough libraries/get the performance we need: https://www.comet.com/docs/v2/guides/comet-ui/experiment-man...

Thank you! Yes, one of the items in the Roadmap is support for Pyodide (https://github.com/pyodide/pyodide) for running in-browser python on the results of each of the code blocks! This should allow most ML libs to be usable in-browser! This is pretty high-up on our priority list.

If I understand correctly, WASM only makes sense for compiled languages, you can run the python interpreter in WASM of course[1], but that will be at a significant performance disadvantage to the native javascript interpreter, and it's also something that has to be loaded every time you load the website.

[1]: https://github.com/pyodide/pyodide

If you absolutely need something comparable to Sympy, then one option might be to figure out how to best call Sympy from Rust. e.g. - RustPython, although it seems like Sympy isn't supported yet - Pyodide, and figuring out how to run it outside of a web browser. Probably also not very easy. - PyPy, and having a pretty simple Python binary for every platform - ...

For running programming languages other than JavaScript in the browser there is Emscripten and WebAssembly. There is v86, where a Linux build is compiled to WASM. Folks have written QuickJS into a Linux build compiled to WASM, Node.js into the Linux buildroot https://github.com/cemalgnlts/now, so Python or CPython can be written to the image and loaded into the browser as WASM as well https://github.com/pyodide/pyodide.

There's a Python runtime that runs on WebAssembly (https://github.com/pyodide/pyodide). I have no idea what it's like, I've never used it.

Still in a quest to provide some tooling to quickly compose documentation websites: https://github.com/synw/docdundee . As I have tons of libs to document and was tired of managing restructured language for readthedocs I started with this, and now it has executable Python examples in the frontend via a Pyodide wrapper composable: usePython

This project's brand new and a lil hacky, but I've already reached out to the scikit-learn team, and they recommended that I experiment with using Pyodide as an alternative backend for the Python bridge.