CalcuLaTeX VS monolith

Check out the main repo here: https://github.com/mkhan45/CalcuLaTeX And the website repo here: https://github.com/mkhan45/CalcuLaTeX-Web

Hey HN, I created CalcuLaTeX because I was frustrated with my workflow for chemistry and physics homework. Generally, I'd use the Python REPL as a calculator and type each problem into LaTeX to turn it in. CalcuLaTeX merges these two steps and makes it easier to reason about calculations by real time visual feedback.

I've posted on r/rust as well (https://www.reddit.com/r/rust/comments/lqn5aa/calculatex_a_p...), and there seems to be interest in using it for scientific papers and such.

The only alternative I know of is PTC MathCAD, which is quite powerful and definitely worth looking into. However, it's quite expensive and Windows only.

The main repo (a Rust library and basic CLI) can be found here: https://github.com/mkhan45/CalcuLaTeX

The website repo using WASM and very hacky JS can be found here: https://github.com/mkhan45/CalcuLaTeX-Web

It supports basic unit conversion via the Unit hints. E.g. you can write 1 hour = ? days. A long term goal is proper Unit coercion which is kind of hard to explain but I did my best in this issue https://github.com/mkhan45/CalcuLaTeX/issues/3.

I'm still working on https://github.com/mkhan45/CalcuLaTeX. I'm hoping for it to be ready for my chemistry quiz next week. I've created a very basic web interface via WASM here: https://mkhan45.github.io/CalcuLaTeX-Web/.

Monolith is a CLI tool for saving complete web pages as a single HTML file.

I have never used monolith to say with any certainty, but two things in your description are worth highlighting between the goals of WARC versus the umpteen bazillion "save this one page I'm looking at as a single file" type projects:

1. WARC is designed, as a goal, to archive the request-response handshake. It does not get into the business of trying to make it easy for a browser to subsequently display that content, since that's a browser's problem

2. Using your cited project specifically, observe the number of "well, save it but ..." options <https://github.com/Y2Z/monolith#options> which is in stark contrast to the archiving goals I just spoke about. It's not a good snapshot of history if the server responded with `content-type: text/html;charset=iso-8859-1` back in the 90s but "modern tools" want everything to be UTF-8 so we'll just convert it, shall we? Bah, I don't like JavaScript, so we'll just toss that out, shall we? And so on

For 100% clarity: monolith, and similar, may work fantastic for any individual's workflow, and I'm not here to yuck anyone's yum; but I do want to highlight that all things being equal it should always be possible to derive monolith files from warc files because the warc files are (or at least have the goal of) perfect fidelity of what the exchange was. I would guess only pcap files would be of higher fidelity, but also a lot more extraneous or potentially privacy violating details

console $ nix-init default.nix -u https://github.com/Y2Z/monolith [...] (press enter to select the defaults) $ nix-build -E "(import { }).callPackage ./. { }" [...] $ result/bin/monilith --version monolith 2.7.0

For example, here’s a command-line tool to save webpages as HTML files: https://github.com/Y2Z/monolith

monolith: Convert any webpage into a single HTML file with all assets inlined.

There is also a program (monolith: https://github.com/Y2Z/monolith) that does the same

besides wget, for single pages I use monolith https://github.com/Y2Z/monolith

You can pipe the URLs through something like monolith[1].

https://github.com/Y2Z/monolith