cirwin

7 ms·

1.
Shell permission errors for busy coding agents(da.vidbuchanan.co.uk)
2 points by cirwin 9mo ago|0 comments
2.
by cirwin 10mo ago
We'd love to (and, tbh, likely will). Search had been a blocker, but that's coming soon; beyond that not sure that there's any reason other than inertia. Alacritty is totally fine, but excited for the Ghostty focus on perform
3.
by cirwin 1y ago
You can configure an arbitrary command to connect to ACP in your settings, maybe something like: {"agent_servers": { "Container Gemini": { "command": "ssh", "arguments": ["h
4.
Green Tea Garbage Collector(github.com)
108 points by cirwin 1y ago|11 comments
5.
by cirwin 1y ago
Author here. Seemed like the least bad of the options. Being able to comment out sections of a config file easily is a prime use-case; and that really implies using newlines as delimiters, and well, you fall into this trap..
6.
by cirwin 1y ago
We currently download node if the system version isn't recent enough (we used to always download it, but I fixed that...).
7.
by cirwin 1y ago
Zed maintainer here. We use node.js to run a number of language servers and formatters (which are often written in node due to the VSCode ancestry...). There've been a lot of requests to disable language servers by default; but I think
8.
by cirwin 1y ago
I’ve been working on https://conl.dev , which fixes/removes YAMLs problematic features. Trying to find a tag-line for it I like, maybe “markdown for config”?
9.
by cirwin 2y ago
This inspired me to write https://conl.dev I agree with his premise that TOML is not user friendly, but INI is not useful enough. CONL attempts to land in the gap
10.
by cirwin 2y ago
`go tool` doesn't require a rebuild, but it does checking that the tool is up-to-date (which requires doing at least a bit of work). This is one of the main advantages of using `go tool` over the "hope that contributors to have th
11.
by cirwin 2y ago
Primary contributor to the feature here. We went back on forth on this a lot , but it boiled down to wanting only one dependency graph per module instead of two. This simplifies things like security scanners, and other workflows that analy
12.
by cirwin 2y ago
For me (maintainer of Zed's vim mode) it comes down to a few things: 1. LSPs differ per-language, and so I'm never sure whether I'll get lucky today or not. It's more reliable for small changes to talk about them in term
13.
by cirwin 2y ago
I’ve been working on a configuration format [1] that looks surprisingly similar to this! That said, the expectation in CONL is that the entire structure is one document. A separate syntax for multiline comments also enables nice things like
14.
by cirwin 2y ago
Nice – I like your verbatim syntax for multiline strings! I went with indentation because a very common use-case in a configuration file is commenting out lines. Even with CSON-like comma rules, you still need to balance your {} and []s. In
15.
by cirwin 2y ago
Funnily enough, I've been working on solving the same problem concurrently. Though in my _very_ biased opinion; I think CONL is easier to read and write: https://github.com/ConradIrwin/conl value = example
16.
by cirwin 3y ago
I wrote something like this for contact auto completion - running in the browser we had to ensure that both tree construction was fast, and also that completion was instantaneous. So the next level of optimization is to amortize tree constr
17.
Next steps on protests and free speech [pdf](law.stanford.edu)
2 points by cirwin 3y ago|0 comments
18.
Report of the Committee on Freedom of Expression(2015) [pdf](provost.uchicago.edu)
2 points by cirwin 4y ago|0 comments
19.
by cirwin 5y ago
A failure rate of ~once every two years is so tiny compared to the rate of failure introduced by other things (from human error, on up); and for many time-related things being off by a second is irrelevant (or again tiny compared to all the
20.
by cirwin 5y ago
This is great! A few more exciting things are happening with file-systems in Chrome that will make this a lot better soon. Firstly OPFS gives you a private sandboxed filesystem you can access with `await navigator.storage.getDirectory()` to
21.
by cirwin 5y ago
Shameless plug, but I built https://github.com/superhuman/lrt as simply as possible, explicitly to avoid this kind of issue (which seem to plague tools in this space).
22.
by cirwin 6y ago
To do this well (for servers, which is the most common case) you need to keep the port open (and delay requests while recompilation is in progress) or clients can see transient errors. So it's probably not a language level concern, but
23.
Database observability for developers: introducing Cloud SQL Insights(cloud.google.com)
4 points by cirwin 6y ago|0 comments
24.
by cirwin 6y ago
We went through the same problem at Superhuman (and as I write our latest extension update has been pending review for 2 weeks, so maybe we're about to hit it again). Simeon on the mailing list was quite re-assuring, and I would recomm
25.
by cirwin 7y ago
Superhuman | Fullstack Engineer | San Francisco & Vancouver | Full-time | At Superhuman, we're rebuilding the inbox from the ground up to make it extremely fast, delightful, and intelligent — you'll feel like you have superpow
26.
by cirwin 7y ago
I like the idea of logging both for a bit! We’ve definitely seen CSS regressions too.
27.
by cirwin 8y ago
It’s pure CSS columns, and not updated since 2012 or so.. yay for the web. I’m surprised they’ve not caught on more, but it is quite hard to control where column breaks end up in a way that lends itself nicely to evenly lengthed columns and
28.
by cirwin 8y ago
Thanks jwilk! Indeed a lot of this information is now quite outdated - thankfully people (e.g. vim) are beginning to implement it natively, and so I have basically deleted all of my own code and can use existing plugins.
29.
by cirwin 8y ago
I’d be open to talking through a backend-focused role, though because we run a search engine and sql database in the browser realistically we end up doing most of the traditionally ‘backend’ work (like search and storage) in the clients. Th
30.
by cirwin 8y ago
Superhuman | Fullstack Engineer & Lead Designer | Early-Stage | Full-time | San Francisco | Onsite | $125-160k + equity • Product: The fastest email experience in the world for web & mobile. Beautiful, powerful, and programmable. •

More ›