Hyperlisk

Very cool! I'm working on something similar but am taking it much slower with a focus on accuracy. Mine recompiles into Golang to take advantage of built-in SIMD support.

I've been building the tooling around the PS2 binaries and hope to have a standalone PSS player out soon that can play PSS files as they are encoded, via simulated renderer, and via in-game engine renderer. The future is so bright with LLMs!

Here's one I remember: http://jgae.de/sdaeng.htm

From here: https://pajhome.org.uk/crypt/md5/uses.html#sdp

I used this many years ago, like literally 20 years ago. And it appears to have had a bounty! Maybe it is what you recall as well!

Google explicitly allows this and documents how: https://antigravity.google/docs/cli/headless/

I literally just wrote about exactly that https://nicktrevino.com/your-repository-is-your-swarm.html

I just submitted it last night on HN, actually. So it should be on my profile in my submissions. It's written more about my experience rather than as a tutorial, but I think it becomes clear how it should work.

I just wrote about this.

Not this exactly, but how your repository can be your swarm, and essentially be your harness.

Using Gitea/GitHub Actions within your repo and agent runner containers allow you to have agents working in your repos 24/7. Not just that, but in a containerized world you can just link up their brains over some shared storage. Using Antigravity, this means you can share the `brain` and its conversation directory with your agent runners and they can get the entire history of everything.

While building it out it becomes apparent that we are just getting started!

Related repo from them, mentioned in the readme as well: https://github.com/xoreaxeaxeax/asm-hall-of-shame

> Instruction latency analysis usually focuses on performance optimization—making code run as fast as possible. The Assembly Hall of Shame takes the opposite approach: searching for the absolute floor of single-instruction performance.

Fun stuff!

This reminds me of a related issue: http://iscaliforniaonfire.com/

perma.cc is great. Also check out their tools if you want to get your hands dirty with your own archival process: https://tools.perma.cc/

Here is some related software from many years back: https://ollydbg.de/Paperbak/index.html

Here's one method for this that I have bookmarked: https://miunau.com/posts/dynamic-text-contrast-in-css/

This is interesting. I really like the DSL. It is a little limited though, just because it works on the month-level only.

One thing that I think is missing is having different dates for transactions to occur. So like some things happen just once ever, or transactions on the last day of the month which shifts.

This just means the stats that are given by this app are a bit rough. Looking at the source it seems to estimate the projections. Not a bad thing, just something to note.

I recently translated my own script-based cash flow simulator to a web app as well, which might be interesting: https://nicktrevino.com/tools.cashflow-simulator.html

One last thing, if you haven't heard of Wails, and you like Golang, I recommend it when thinking about making a desktop version of a web app: https://wails.io/

Nice! I share a similar set of thoughts and ideals around configuration languages and I'm working on one as well. Mine has a very similar syntax, so you might be interested! You can find it if you dig through my comments.

That's not true. I just wrote a similar comment about design coming first. If you've written software for awhile you just know what it looks like and which design patterns will be useful. Then when you see what your LLM says is the right code you can glance at it and see if it is even on the right track.

If you're trying to LLM your way to a new social site you're going to need to know what entities make up that site and the relationships they have ahead of time. If you have no concept of an idea then of course the LLM will be "correct" because there were no requirements!

Software design is important today and will be even more important in the future. Many companies do not require design docs for changes and I think it is a misstep. Software design is a skill that needs to be maintained.

This is my experience as well. I've been skeptical for a long time, but recent releases have changed my mind (it's important to try new things even if skeptical). Large context windows are game-changers. I can't copy/paste fast enough.

The future is coming, but you still need fundamentals to make sure the generated code has been properly setup for growth. That means you need to know what you expect your codebase to look like before or during your prompting so you can promote the right design patterns and direct the generation towards the proper architecture.

So software design is not going away. Or it shouldn't for software that expects to grow.

Yes! Another vote for CC-BY-NC-SA! I release my code under this license as well, even snippets I post on my (tiny) blog.

I think this is what a lot of people would use if it were more known about. I feel like a lot of people do not actually read what a license provides and just default to MIT because it is widely used.

This looks nice with a friendly UI. I've been very happy with Caddy[1], but this seems like something I might recommend to someone that is new to the web environment.

[1] https://caddyserver.com/docs/quick-starts/static-files

Are you ready to get naked?

  ['style','link[rel=stylesheet]','link[type="text/css"]'].forEach(selector => document.querySelectorAll(selector).forEach(e => e.parentNode.removeChild(e)));
  document.querySelectorAll('[style]').forEach(el => el.removeAttribute('style'));

My little page seems to pass (submitted things here previously, but it's not naked currently)

I'm working on a configuration file format. I see a lot of complexity in the current space, and not enough thought put into the use-cases for a configuration language.

YAML is prone to typos, TOML does not seem obvious to me, and JSON is not as easy to edit.

I've been designing CLEO:https://code.nicktrevino.com/cleo/

The focus is on a configuration language that a single application would use. Not a system-level configuration that might need control flow, etc.

It is at a solid state right now, though it's not officially released yet as I slowly validate it with usage.