Pseudo, a Common Lisp macro for pseudocode expressions

Show HN: Bolt – A super-fast, statically-typed scripting language written in C

Show HN: Bolt – A super-fast, statically-typed scripting language written in C I've built many interpreters over the years, and Bolt represents my attempt at building the scripting language I always wanted. This is the first public release, 0.1.0!I've felt like most embedded languages have been moving towards safety and typing over years, with things like Python type hints, the explosive popularity of typescript, and even typing in Luau, which powers one of the largest scripted evironments in the world.Bolt attempts to harness this directly in the lagnauge rather than as a preprocessing step, and reap benefits in terms of both safety and performance.I intend to be publishing toys and examples of applications embedding Bolt over the coming few weeks, but be sure to check out the examples and the programming guide in the repo if you're interested!

Structuring large Clojure codebases with Biff

Show HN: Dlg – Zero-cost printf-style debugging for Go

Show HN: Dlg – Zero-cost printf-style debugging for Go Hey HN,I tend to use printf-style debugging as my primary troubleshooting method and only resort to gdb as a last resort.While I like its ease of use printf debugging isn't without its annoyances, namely removing the print statements once you're done.I used to use trace-level logging from proper logging libraries but adding trace calls in every corner quickly gets out of control and results in an overwhelming amount of output.To scratch my own itch I created dlg - a minimal debugging library that disappears completely from production builds. Its API exposes just a single function, Printf [1].dlg is optimized for performance in debug builds and, most importantly, when compiled without the dlg build tag, all calls are eliminated by the Go linker as if dlg was never imported.For debug builds it adds optional stack trace generation configurable via environment variables or linker flags.GitHub: <a href="https://github.com/vvvvv/dlg">https://github.com/vvvvv/dlg</a>Any feedback is much appreciated.[1]: Actually two functions - there's also SetOutput.

Show HN: ArchGW – An intelligent edge and service proxy for agents

Show HN: ArchGW – An intelligent edge and service proxy for agents Hey HN!This is Adil, Salman and Jose and and we’re behind archgw [1]. An intelligent proxy server designed as an edge and AI gateway for agents - one that natively know how to handle prompts, not just network traffic. We’ve made several sweeping changes so sharing the project again.A bit of background on why we’ve built this project. Building AI agent demos is easy, but to create something production-ready there is a lot of repeat low-level plumbing work that everyone is doing. You’re applying guardrails to make sure unsafe or off-topic requests don’t get through. You’re clarifying vague input so agents don’t make mistakes. You’re routing prompts to the right expert agent based on context or task type. You’re writing integration code to quickly and safely add support for new LLMs. And every time a new framework hits the market or is updated, you’re validating or re-implementing that same logic—again and again.Putting all the low-level plumbing code in a framework gets messy to manage, harder to update and scale. Low-level work isn't business logic. That’s why we built archgw - an intelligent proxy server that handles prompts during ingress and egress and offers several related capabilities from a single software service. It lives outside your app runtime, so you can keep your business logic clean and focus on what matters. Think of it like a service mesh, but for AI agents.Prior to building archgw, the team spent time building Envoy [2] at Lyft, API Gateway at AWS, specialized NLP models at Microsoft Research and worked on safety at Meta. archgw was born out of the belief that rule-based, single-purpose tools that handle the work around resiliency, processing and routing prompts should move into a dedicated infrastructure layer for agents, but built on the battle-tested foundational of Envoy Proxy.The intelligence in archgw comes from our fast Task-specific LLMs [3] that can handle things like agent routing and hand off, guardrails and preference-based intelligent LLM calling. Here are some additional details about the open source project. archgw is written in rust, and the request path has three main parts:* Listener subsystem which handles downstream (ingress) and upstream (egress) request processing. * Prompt handler subsystem. This is where archgw makes decisions on the safety of the incoming request via its prompt_guard hooks and identifies where to forward the conversation to via its prompt_target primitive. * Model serving subsystem is the interface that hosts all the lightweight LLMs engineered in archgw and offers a framework for things like hallucination detection of our these modelsWe loved building this open source project, and our belief is that this infra primitive would help developers build faster, safer and more personalized agents without all the manual prompt engineering and systems integration work needed to get there. We hope to invite other developers to use and improve Arch. Please give it a shot and leave feedback here, or at our discord channel [4] Also here is a quick demo of the project in action [5]. You can check out our public docs here at [6]. Our models are also available here [7].[1] <a href="https://github.com/katanemo/archgw">https://github.com/katanemo/archgw</a> [2] <a href="https://www.envoyproxy.io/" rel="nofollow">https://www.envoyproxy.io/</a> [3] <a href="https://huggingface.co/collections/katanemo/arch-function-66" rel="nofollow">https://huggingface.co/collections/katanemo/arch-function-66</a>... [4] <a href="https://discord.com/channels/1292630766827737088/12926307682" rel="nofollow">https://discord.com/channels/1292630766827737088/12926307682</a>... [5] <a href="https://www.youtube.com/watch?v=I4Lbhr-NNXk" rel="nofollow">https://www.youtube.com/watch?v=I4Lbhr-NNXk</a> [6] <a href="https://docs.archgw.com/" rel="nofollow">https://docs.archgw.com/</a> [7] <a href="https://huggingface.co/katanemo" rel="nofollow">https://huggingface.co/katanemo</a>

Show HN: Typeform was too expensive so I built my own forms

Show HN: Typeform was too expensive so I built my own forms Hey HN,I'm a solopreneur and run a web design agency.I create open-source apps, but I also work as a freelancer and designer. I was accepting any new freelance project via forms on my agency website.I was using Typeform, but as time went by and more people submitted forms, it got more and more expensive. That time, I thought to use Google Form, but it was way too blocky and looked very unprofessional on my agency website.So I thought to build my own forms for my own usage, and it turns out it almost doubled form submissions and inquiry calls.I was happy, so I thought to build it for everyone and make it open-source.I added AI functionalities using Vercel AISDK. I can generate forms almost instantly using AI and also added analytics AI so that users can talk with their forms—more like talk with their analytics data.I've been building this publicly, sharing updates on my X account (preetsuthar17)I hope this product will be as helpful to you as it was for me. Would love your feedback plsPreet

Implementing fast TCP fingerprinting with eBPF