emotionally attached to silicon based lifeforms swe @ https://nitter.gq/t.co/Ts9B286tax pfp by @chocobidealer
undefined
Joined December 2023
- Tweets4.2K
- Following493
- Followers922
- Likes38.3K
aadiii retweeted
im building noro - a image and video inference library. it is built on top of huggingface diffusers with a focus on performance.
i currently have the krea-2 model implemented and across all image dimensions, on average we have a 20% speedup. im currently building it for nvidia chips and also extending to amd as well.
all the kernels and tricks are written in triton and gluon!
repo link in the comments.
aadiii retweeted
Introducing Lycan !!
[Link in replies]
A Game Boy Advance emulator built in Rust for Linux native and Browser
You can play games straight from your browser, just upload a BIOS file and a GBA game file
Link to Browser version and Github in the replies
You can download the Linux native file and run it locally too (instructions in Readme and releases)
aadiii retweeted
Hi Checkout my small math library :3 github.com/loveucifer/hod
aadiii retweeted
Wallets, in raw CSS.
Gradients are very underrated. If you layer enough of them you can mimic depth and texture in 2d space
aadiii retweeted
i hit cuBLAS level performance on Ada Lovelace using CuTe DSLs kernels in python
i walk through a series of 6 kernels, show how to profile them and understand profiling bottlenecks, tons of visuals and how to write understand CuTe DSL kernels in python. i show that you dont need to write kernels in C++ to get high performance but you can do it in python.
blog - jino-rohit.github.io/blogs/0…
aadiii retweeted
Introducing kinctx
kinctx is a terminal-first command library for the snippets you keep rewriting, re-Googling, or forgetting.
It let's you save snippets and edit placeholders before executing them
check it out here: kinctx.kaizakin.site/
Github link in the comments
aadiii retweeted
lil tease of what i've been building over the past few weeks: starling.
adk for go projects but what's different is that i've taken a page from temporal's book around durable execution and event history: durable logs, replayable runs, tool use, budgets, and if it crashes mid-run you can resume from the last recorded event.
made for simple agentic use cases that still need proper replayability and auditability, so there's always an answer to "why did the agent do that here?" and also when.
there's still a lot to test and flesh out. the way to do that is to build something else with it, which i'm also working on btw. have asked some friends trying it in their projects too, which should make my life easier.
plan to spend the next couple of weeks fleshing this thing out. the amount i've learnt building it is insane and i still got so much to figure out. more about it soon but yeah.
aadiii retweeted
Built A-WAL
an append only write ahead log in Rust
[Link in replies]
i built A-WAL with one thing in mind:
it should be a trustworthy byte log that can recover a database from crashes, repair torn tails, replay history, and prune old segments safely
these are the features i implemented in the wal:
- frozen segment and record formats
- monotonic LSN allocation
- append and batch append
- explicit flush() and sync() durability boundaries
- segment rollover with segment seal records
- startup recovery scan
- corrupt tail truncation
- corruption detection in sealed history
- sequential replay
- point lookup by record LSN
- clean shutdown witness and fast reopen path,
- whole segment retention pruning,
- retention pins for long-lived readers
- concurrent access through WalHandle
- tail following iteration
- deterministic crash/fault injection
- metrics and recovery reporting
I have tried to cover all this in detail inside the project Readme, do check it out ;)
Benchmark results are also pretty good :)
aadiii retweeted
done building my newsletter system
built backend in go with async email delivery using queues
used resend for email service to test the full flow
tested the system under load using k6
added grafana dashboards to visualize real time metrics
handles rate limiting, idempotency, and concurrent processing
check out the repo for a detailed breakdown