An unfinished spreadsheet-based interface for entering time. Meant for consulting, but never got around to persisting the data. Mostly created it because I couldn't stand all the ways that time trackers force users to enter structured time when there's a cute algorithm to handle just about every way a human might naturally enter time.
In the days of LLMs, it would be far easier to categorize ingredients and format them into TeX for publishing as a PDF file. The idea behind this project was to let people essentially copy/paste recipes off the web or scans of handwritten content and autoformat it.
Given a distance, an allowable time to reach that distance, a payload to send, and an expected exhaust velocity, how would you calculate the time required to convert energy into antimatter fuel and how much antimatter needed to arrive at the destination (starting from the Moon)?
There are a few side calculations, such as the size of the radiator, estimated footprint of the fusion reactor itself, and how much metamaterial is needed. This is to help figure out timelines for a sci-fi novel, so ballpark answers are completely fine.
The calculations yield what appear to be values around the correct order of magnitude. Would be delighted to have insights, comments, and corrections.
This hides memory allocations altogether. As long as the open/close functions are paired up, it gives me confidence that there are no inadvertent memory leaks. Using small functions eases eyeballing the couplings.
For C++, developing a unit test framework based on Catch2 and ASAN that tracks new/delete invocations is rather powerful. You can even set it up to discount false positives from static allocations. When the unit tests exercise the classes, you get memory leak detection for free.
(I don't mind down votes, but at least reply with what you don't like about this approach, and perhaps suggest a newer approach that we can learn from; contribute to the conversation, please.)
> As long as the open/close functions are paired up
Let me stop you right there. I did not downvote you, but I bet that's why others did. If humans were capable of correctly pairing open/close, new/delete, malloc/free, then we could've called C's memory management "good enough" and stopped there. Decades of experience show that humans are completely incapable of doing this at any scale. Small teams can do it for small projects for a small period of time. Large teams on large projects over long eras just can't.
If the advice for avoiding resource errors includes "all the programmer has to remember is...", then forget it. It's not happening. Thus the appeal of GC languages that do this for the programmer, and newer compiled languages like Rust that handle resource cleanup by default unless you deliberately go out of your way to confuse them.
As you add more code between the "open" and the "close", you introduce more opportunities for control flow to accidentally skip the "close" (leak), or call it more than once (double-free). It forces you to use single-return style, which can make some things very awkward to express.
You're basically doing "defer"-style cleanup manually; you may as well just use the real "defer" if your compiler supports it. It's supposed to be official in a future standard, too.
When developing KeenWrite[1], I opted to support only plain TeX. This is because I wanted math typesetting to work for either LaTeX or ConTeXt[2]. To render TeX in the preview panel, I forked NTS[3] into a highly optimized Java version. The lack of cross-platform event-based UI system is what kept me from writing the entire application in Rust (some ten years ago). Has the Rust ecosystem improved with respect to Markdown processing, event-based UIs, and now TeX support?
Sorry for the inconvenience. The email works now. Regarding the article - I use similar ideas to extract colors form artwork images, only difference is I added color prevalence scale for each color and limited it to 10 colors per palette.
My free, open-source, bare-bones, caching-free, dependency-free, authentication- and authorization-free pure PHP raw Git viewer. I developed it because GitList blew out my shared host's drive space and memory (due to a caching bug) and to consolidate my GitHub, BitBucket, and GitLab repos. There's something rewarding about self-hosting and not being beholden to the whims of third parties.
> I truly love GitHub, and I hope they find their way.
I jumped ship as soon as they added MFA. I vibe-coded my own raw Git repository reader to help consolidate my other repos (BitBucket, GitLab), which inevitably started to impose more restrictions (disk space, MFA), as well. It's no GitHub, but works, doesn't cache, and is pure PHP.
The NSF is an independent federal agency that funds roughly a quarter of all basic academic research in the US, laying the groundwork for technologies like the Internet backbone and MRIs. The NSB is its governing body, composed of top scientists who serve staggered six-year terms specifically so no single administration can wipe out the entire board at once. That continuity is designed to insulate scientific priority-setting from political pressure, ensuring American research funding is directed by objective merit rather than political patronage. Dismissing all members simultaneously removes the exact oversight mechanism built to prevent political offices from dictating scientific agendas.
From a political science perspective, this is an institutional move Robert Paxton described in his stages of fascist development. His framework identifies patterns where political actors weaken or bypass independent bodies designed to constrain executive power. In Paxton's fourth stage, the exercising of power, an executive consolidates control by actively dismantling these checks. Centralizing control over scientific governance by firing the board for opposing a budget cut is hollowing out an independent institution; it's a pathway Paxton documented whereby institutional checks are weakened in ways that accumulate over time.
https://repo.autonoma.ca/repo/timeivy
An unfinished spreadsheet-based interface for entering time. Meant for consulting, but never got around to persisting the data. Mostly created it because I couldn't stand all the ways that time trackers force users to enter structured time when there's a cute algorithm to handle just about every way a human might naturally enter time.
https://stackoverflow.com/a/49185071/59087
* Recipe managers
https://repo.autonoma.ca/repo/recipe-fiddle
In the days of LLMs, it would be far easier to categorize ingredients and format them into TeX for publishing as a PDF file. The idea behind this project was to let people essentially copy/paste recipes off the web or scans of handwritten content and autoformat it.
reply