godbledger VS pyodide

Shameless self plug: ive been building a similar open source command line accounting system

https://github.com/darcys22/godbledger

Its heavily inspired by both ledger and beancount but my biggest issue with them is that text files arnt great for double entry bookkeeping. Having a relational database is the better option which is what GoDBLedger has.

After a certain point a business cant keep track of its transactions in text files because there are simply too many of them, so these systems really only scale to personal finance levels (few hundred transactions maybe thousand transactions).

In addition building plugins that can import your whole text file into a sql system so you can query them is redundant. Just have it in a relational database to start with.

I’ve been building an open source accounting system in go.

https://github.com/darcys22/godbledger

Id love for any seasoned golang experts to do a review of my code and highlight any areas that could be improved.

This has also been my opinion for the accounting industry. Just like c compilers before gcc were proprietary and poor performing the accounting software that exists has many limitations. That means there is a huge opportunity for an open source system to blow them out of the water.

Ive been building one myself but i know there are many more coming for this industry :)

https://github.com/darcys22/godbledger

https://github.com/darcys22/godbledger

I love these command line self hosted accounting software packages. But double entry bookkeeping was invented using ledgerbooks with ruled tables. I feel the plain text dataformats are a regression compared to a sql database. A general ledger just works so well with columns that you can sum.

It also saves you from needing a custom tool like bean-query to replicate sqlite-ish queries because it could have been in a database from the start

GoDBLedger https://github.com/darcys22/godbledger

Its the core of my open source accounting system. Its slightly further along than half baked because the core works but that just means you can do double entry bookkeeping on the command line. Currently building a web interface to interact with it which hopefully will attract non technical users

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.