Hacker Newsnew | past | comments | ask | show | jobs | submit | azriel91's commentslogin

"Hi everyone, today we're going to read the book of Acts."

opens terminal

(made me smile)


A graphviz substitute in rust:

https://azriel.im/disposition/

The text editor has an LSP built in to guide you to what can be entered, but see the examples.

I wanted a way to have visual documentation that can show/hide detail, and be pure svg so that it can be pasted into sites without becoming pixelated.

Also supports animations to show interactions between hosts, which always gets messy when drawing a static diagram.


Working on a GraphViz replacement (again):

Site: https://azriel.im/disposition

Repo: https://github.com/azriel91/disposition

It's written in Rust, has stable node positions, is stylable (and has default styling, dark mode styles), among other things.

The hardest part is calculating coordinates for edges:

- ranking nodes / positioning them when edges connect nodes of different nesting levels

- ensure edges don't overlap with nodes to not obscure content

- ensure edges don't overlap with each other

It's about 60% of what my version of "complete" looks like. Remaining parts:

- edge labels (might need a rewrite of how edge paths are calculated.

- images in nodes

- generating diagrams for different screen sizes

- LSP support (?)


> (again)

I can completely empathize - sometimes some problems never leave us.. like that piece of food stuck b/w teeth. There's a force within us asking us to right that problem in the world.

All the best to your project.


An SVG diagram generator to substitute GraphViz in pure Rust:

https://azriel.im/disposition

Solves some problems that were hard to work around with GraphViz, e.g. default and customisable styling, light and dark mode, stable / predictable layout.


I used to make these quite often: https://cards.azriel.im/

Now I still make them occasionally, though I haven't updated the blog for a while.

I find that tangible art could sometimes say "thank you" more than the utterance of the words themselves.

Also makes for a great wedding gift:

https://cards.azriel.im/2018/09/kevin-fiona.html


Does my side project provide any hope?

https://peace.mk/blog/checkpoint/

(old blog post, but I'm slow in making progress)


Working on "wanting to live". It's hard to create desire within oneself when one has experienced intense sorrow.

Been trying the "do the thing, and desire comes after" for many things (baking, piano, skating, ..), but that hasn't really worked. What has seemed to work is connecting with people (crucial that they know how to connect back).

Made a little web app that helped me communicate: https://azriel.im/tears/

(I could just point to the number when I couldn't talk/listen)


Thanks for the link, I think this is helpful and the tips resonate with me.

As I get older, the desires that "work" are very frequently the same ones as I had when I was a child.


I was at a games exhibition a few months ago - and there was a game designed to help people deal with grief which i found interesting. I cant remember the name


If you remember the name that would be something I would be interested in!


Gris and Spiritfarer are two recent-ish ones I'm aware of, both were well thought of by my partner who works in grief care. :)


Good luck, it can be tough, but you're worth the effort.


there's:

https://github.com/Pernosco/gha-runner

but I'm not sure how complete it is, and probably doesn't satisfy the author's use cases


https://www.nushell.sh/

I use this as my main shell on Windows, and as a supplementary on Mac and Linux.


What I'd like is a future where software is "stupidly fast":

1. RIIR -- for native code execution performance, and correctness

2. async rust preferably -- green threads for efficient cpu usage

3. the constraint efficiency of game developers: 16 ms window to do all your processing

4. data structures sized to fit cache lines

5. vulkan/metal rendering pipeline

oh my

(edit: formatting)


> the constraint efficiency of game developers: 16 ms window to do all your processing

This is the only one that really matters. It also implies a complete redesign of how "responsiveness" is handled, because the usual failure mode of slow GUIs is to get blocked on a whole cascade of updates which have to be done in series. Immediate mode GUIs are a lot better for this because the programmer knows that they can't call out to get some data; you render what you're given, either it's arrived on this frame or it hasn't.


When you see how slow modern CLI tools can be, you don't need all this technology. Just think of respecting human time. The only true currency of life until we invent immortality.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: