thramp

6 ms·

1.
Will agents like Git any more than we do?(amplifypartners.com)
3 points by thramp 4mo ago|1 comments
2.
by thramp 4mo ago
For disclosure, Amplify is ERSC's lead investors, and I'm one of the cofounders of ERSC.
3.
by thramp 6mo ago
A couple of gentle corrections: > The document didn't mention a lawsuit and I was just responding to the above comment with only the context of the postmortem and pointing out that this particular article didn't claim anything
4.
by thramp 6mo ago
This is a disappointing look for Ruby Central. I have to get back to work, but their retroactive framing that Andre and Samuel's work on RV justified Ruby Central's subsequent actions is contradicted by their own admissions. By th
5.
by thramp 8mo ago
One of the rust-analyzer co-maintainers (Chayim Friedman) already rewrote it, but we can’t integrate it yet, as about 40 assists (the little lightbulbs?) still rely on mutation. If you want something Rowan-like, I think syntree and Biome’s
6.
by thramp 8mo ago
(Hi, I’m on the rust-analyzer team, but I’ve been less active for reasons that are clear in my bio.) > Language servers are powerful because they can hook into the language’s runtime and compiler toolchain to get semantically correct ans
7.
by thramp 8mo ago
We (the rust-analyzer team) have been aware of the slowness in Rowan for a while, but other things always took priority. Beyond allocation, Rowan is structured internally as a doubly-linked list to support mutating trees, but: 1. Mutation i
8.
by thramp 1y ago
I’d second Rain’s reply, but having gone from git to sapling to jujutsu, I feel like the jump from sapling to jujutsu was as big as the jump from git to sapling, in terms of “oh, this is a way nicer workflow”. I really like and miss Sapli
9.
by thramp 1y ago
(disclosure: I started a jj company but I don’t have anything to sell yet.) > Are there "central concepts" in the Jujutsu design? I think a central concept in jj is that everything is a commit: there’s no staging index, stash
10.
by thramp 2y ago
(I work on rust-analyzer) We don't share the query infrastructure in rust-analyzer, but rust-analyzer is a query-driven system. We use Salsa ( https://github.com/salsa-rs/salsa/ ), which is strongly inspired by
11.
by thramp 2y ago
Oh, that’s super clever integration with tracing. Feel free to send us a PR; we’ll link to this as a related project in the docs!
12.
by thramp 2y ago
That's a great point about allocation/memory management. As an example, rust-analyzer needs to free memory, but rustc's `free` is simply `std::process::exit`. If I remember correctly, the new trait solver's interner is a
13.
by thramp 2y ago
> Are they? I feel like intellisense is largely a subset of what a compiler already has to do. They are distinct! Well, not just intellisense, but pretty much everything. I'll paraphrase this blog post, but the best way to think abo
14.
by thramp 2y ago
I've responded on reddit before ( https://www.reddit.com/r/rust/comments/1eqqwa7/comment/lhwwn... ), but I'll restate and cover some other things here. > I have a maybe wrong and bad opin
15.
by thramp 2y ago
It's not a ridiculous argument! Not naming everything means that you can reserve naming things for when it actually makes a difference .
16.
by thramp 4y ago
the problem with this approaches like these that it requires blocking the runtime: https://github.com/jaboatman/tokio-scoped/blob/master/src/li... .
17.
by thramp 6y ago
fehler isn't deprecated, but _I_ did deprecate the similarly named https://github.com/rust-lang-nursery/failure/ with withoutboat's blessing. failure proceeded fehler by several years.
18.
by thramp 6y ago
> Otherwise, it is another "rewrite it in rust" post which is yet to materialise into a real project. I'm not sure you can reasonably said that "it is another 'rewrite it in rust' post..." if it's
19.
by thramp 6y ago
> This is based on her presentation and some dinner conversation at HPTS 2019, so I don't know if there's actually a paper I can point to. Thanks for the explanation! I just found http://www.hpts.ws/papers/
20.
by thramp 6y ago
> I think there are open possibilities in making leaderless single-round-trip consensus systems for log-oriented FSMs, which is what pretty much everyone WANTS. Woah, that's wild. Are there any pre-prints/papers/talks that
21.
by thramp 6y ago
I like the retrospective of this post! The "what ifs" that could've been taken are fun to think about. I think I might take a step further than this post does—I think some sort of Racket/Rust-style macro system should be
22.
by thramp 6y ago
I think this might be caused by autosave being enabled in VSCode, but this is just idle speculation.
23.
by thramp 6y ago
I was _just_ thinking of https://latacora.micro.blog/2020/03/12/the-soc-starting.html and https://sso.tax/ as I was writing my comment!
24.
by thramp 6y ago
This is a great change! One request: I wish that SAML was not an enterprise feature. SAML ought be a basic security feature like 2FA—it's especially valuable for open source teams who might use a mixture of services, and an easily acce
25.
by thramp 7y ago
The reason the `http` crate has a "bespoke hashmap implementation" is not because "performance", it's because _HTTP headers call for different behavior than `std::collections::HashMap`_. Some of the differences in b
26.
by thramp 7y ago
How so?
27.
by thramp 7y ago
Author here—while many systems are performance-sensitive, many others aren't. Personally, I don't enjoy writing Python at work due to its lack of misuse resistance more than any concerns about performance (although a large-enough
28.
by thramp 7y ago
Yep! Thank you so much! I really need to update the documentation, but I think `cross` ( https://github.com/rust-embedded/cross ), a drop-in cargo replacement, is the probably the best available solution for building mus
29.
by thramp 7y ago
Rust AWS Lambda Runtime author here: while the Rust runtime tends to beat all other runtimes, Go is _very_ close in terms of startup times.
30.
by thramp 7y ago
I'm happy to have helped on the AWS side!

More ›