Meant to say I "can" communicate in shorthand :) My kingdom for an edit button :P
Meant to say I "can" communicate in shorthand :) My kingdom for an edit button :P
In both the @aspire.dev and #hex1b codebases I cannot communicate in shorthand because there is enough code that shapes the agent's behavior. Building "repo dialect" is an important role for developers doing engineering with coding agents. It is what unlocks productivity.
Adding AGENTS.md and SKILL.md files is a big part of that dialect being in place when you start a project, but as you progress the code itself, if following consistent patterns should form a much larger part of the dialect.
I think one of the biggest challenges that people have with coding agents is establishing a domain specific dialect that they and the agent can use to efficiently communicate.
Giving the agent the right context can help with this, but there are multiple sources for this context.
GitHub Copilot has been busy extending the Editor widget in #hex1b to support syntax highlighting. Here is a little taste test of where it is at.
Just shipped an update to #hex1b today which adds a `WithDockerContainer` API to Hex1bTerminaBuilder. The idea is that you attach a running container to your terminal to help with test isolation. Works fairly well although not very visual. Was @davidfowl.com's idea.
github.com/mitchdenny/h...
TUI map rendering in #hex1b.
I love it. Canβt wait for the next season. Also β¦. Bring Discovery back. Also bring Stargate Universe back. Also bring back firefly.
I was always fascinated by BeOS UX
This larger video shows one of the challenges I'm dealing with right now which is around occlusion of images. You can see that the z-order is messed up. I may need to slice up the image into cell sized blocks and place partials of it to fake the layering that Hex1b can support.
Been experimenting with getting #hex1b to support Kitty Graphics Protocol. Very early days bat at least something is showing on the screen. I've got it working inside Hex1bTerminal itself (on this branch of the code), but this screenshot shows it flowing through from a Hex1b app (TUI framework).
Vegimite Liberation Front
Had a go to see whether I could get @github.com Copilot to write a *.obj to braille renderer inside of Hex1b. Seemed to do already - not perfect by any stretch but not bad given the constraints. The demo has built in decimation but it's not very good.
π
#csharp #dotnet
#hex1b drag and drop support with drag ghost overlays AND a proof-of-concept for terminal thumbnails
Here is a little terminal multiplexing experiment for #hex1b. This one shows a main terminal window and a panel on the right with thumbnails which I can then drag and drop (with previews) onto the main terminal to switch between them.
Every dev that Iβve ever spoken to that has built temporal APIs have deep emotional scars.
Looks like Bluesky is currently getting inundated with bot accounts.
#hex1b
Yeah Hex1b does surface diffing on the TUI path automatically.
I got a more advanced version going in WASM Blazor last night. Including rolling cloud cover. Trick is managing GC in a reactive API.
Itβs adaptive. But i think there was an animation going off every 30ms. But the trick is to reduce that. If it isnβt moving the framerate stays constant in terms of rendering logic but the effective bytes going to the terminal drops to zero. Itβs not fully optimized.
Understandable. Although I would recommend you reframe things in your head a little bit. They are called pull requests for a reason - they arenβt called Tasks/TODOs because no one has the right to place demands on your time as the maintainer.
You are the most valuable and finite resource.
#hex1b ... interactive surface rendering as a background for a Window Panel.
A lot of the perf work I did was in service of a fun little demo for #AspireConf that I'm putting together. The video above is not from that demo - if you want to see that you'll need to come along: aspire.dev/aspireconf/?...
Here is a nice little example of what you can do with Hex1b. Over the past week I've been making some performance improvements to #Hex1b. Some big wins and lots of little optimizations - and a few more things to work on.
We did have that issues a few versions back. Are you running 13.1.1?
Hey there @bridged.yellows.ink can you give some more details about what you are seeing in the Aspire log viewer? Can you share a screenshot of the issue (including details of which version of Aspire etc).
Is there a GitHub issue that we can look at?
Wow while working with @github.com #copilot today I walked it through the process of fixing a bug in a dependency package and using the local and PR builds to validate and now it's doing it automatically for another issue I just found. Takes some of the drudgery out of things.