Joel Martin

@kanaka.bsky.social

61 Followers 56 Following

Creator of mal/make-a-lisp, noVNC, websockify, clj-protocol, conlink, instacheck, miniMAL, wam, wac, warpy, raft.js (github.com/kanaka). Interested in Clojure, WebAssembly/wasm, AI/LLMs, JS, Rust, network protocols, web browsers, testing, etc.

An image from the github link that shows Model and Premium requests columns with the following data: Model Premium requests Base model (currently GPT-4o) 1 0 (paid users), 1 (Copilot Free) Claude 3.5 Sonnet 1 Claude 3.7 Sonnet 1 Claude 3.7 Sonnet Thinking 1.25 Gemini 2.0 Flash 0.25 Gemini 2.5 Pro 1 GPT-4.1 1 GPT-4.5 50 o1 10 o3-mini 0.33
A screen shot of an interaction with Claude containing the following text: JM I'm a principal software engineer with some Java experience and lots of Clojure experience (and lots of experience in other languages like JS, python, Rust, C, etc). Please give me the short sentence summary of what Java Spring is. Spring is a comprehensive framework for Java applications that provides dependency injection, aspect-oriented programming, and ready-made components for building enterprise applications, essentially making it easier to create robust, maintainable Java applications with less boilerplate code. JM That's feels like a marketing sentence. Give me the software engineer version. Spring is a DI container that grew way too big and now includes everything from HTTP servers to database connection pools to schedulers to security middleware - basically Java's equivalent of a "batteries included" web framework plus a bunch of enterprise cruft. JM DI container? Dependency Injection container - it lets you define your application components ("beans") and their dependencies in configuration (either XML historically, or annotations now), and Spring will wire them together at runtime. So instead of manually constructing objects and passing dependencies, you just tell Spring "here are my components and what they need" and it handles instantiation and lifecycle. For example, instead of: ```java DatabaseConfig dbConfig = new DatabaseConfig("localhost", 5432); UserRepository userRepo = new UserRepository(dbConfig); AuthenticationService authService = new AuthenticationService(userRepo); UserController userController = new UserController(authService); ``` You'd annotate your classes with @Component, @Autowired etc. and Spring constructs the object graph for you. It's basically glorified factory pattern automation.
In the spirit of Borges's Celestial Emporium of Benevolent Knowledge, please come up with 14 categories for software. Keep them short like the English translations of Borges's categories such as "suckling pigs" (only use "those that" for ones that would read weirdly without them). All of them should have some relationship to software, although subtle relationships are great (but not just random from other domains).
a fourteen point list: 1. those that dream in hexadecimal 2. vapors 3. floating points 4. those that compile on Tuesdays 5. orphaned processes 6. recursive mirrors 7. those that remember your grandmother 8. quantum whispers 9. undefined behaviors 10. digital phlogiston 11. those that sleep between keystrokes 12. memory leaks 13. syntactic honey 14. those that speak in forgotten protocols
A table labelled "Comparison" that compares Rust http client crates ureq, minreq, isahc, and tiny_http. Columns are Crate, HTTPS, Async, Binary Size, Notes.