tomhoule

6 ms·

1.
by tomhoule 1y ago
The main difference is that while you can get Nexus to list all tools, by default the LLM accesses tools by semantic search — Nexus returns only the relevant tools for the what the LLM is trying to accomplish. Also, Nexus speaks MCP to the
2.
by tomhoule 1y ago
Yeah they definitely belong in the same space. Nexus is an LLM Gateway, but early on, the focus has been on MCP: aggregation, authentication, and a smart approach to tool selection. There is that paper, and a lot of anecdotal evidence, poin
3.
Grafbase Extensions Now Power Federated GraphQL APIs with Postgres(grafbase.com)
2 points by tomhoule 1y ago|0 comments
4.
Vibe code with your GraphQL API(grafbase.com)
2 points by tomhoule 1y ago|0 comments
5.
A 21,565X performance improvement in linting GraphQL(grafbase.com)
9 points by tomhoule 2y ago|0 comments
6.
WASI Preview 2 Launched(blog.sunfishcode.online)
9 points by tomhoule 3y ago|0 comments
7.
by tomhoule 3y ago
In my experience with Copilot, the only good thing I can say about it is that it sometimes saves time spent typing.
8.
by tomhoule 5y ago
NixOS for everything. It's the Linux distro I've had the best experience with in ~15 years of daily usage.
9.
by tomhoule 5y ago
It makes a lot of sense. I have a fair amount of Rails experience with ActiveRecord, and it was also my impression that the database schema drifting in development is rarely a problem, but I now think it's a bit of a fuzzy feeling and
10.
by tomhoule 5y ago
As of now there is no strong opinionation in the tool — you could absolutely maintain a set of down migrations to recover from bad deployments next to your regular migrations, and apply the relevant one (manually, admittedly) in case of pro
11.
by tomhoule 5y ago
Yep we looked at Django ORM as an inspiration. I unfortunately don't have the bandwidth right now to write a lengthy thoughtful response, but quickly on a few points: - The replaying of the migrations history is exactly what we do, but
12.
by tomhoule 5y ago
No question that there are cases where down migrations are a solution that works. In my experience though, these cases are more limited than you might think. There are a lot of presuppositions that need to hold for a down migration to &quot
13.
by tomhoule 5y ago
I can clarify one point, relative to migration rollbacks. We indeed chose not to implement down migrations as they are in most other migration tools. Down migrations are useful in two scenarios: in development, when you are iterating on a m
14.
by tomhoule 6y ago
Ooh it's interesting you mention David Spivak's work, I got interested into it recently. Some of these ideas are being commercialized by https://conexus.com/ (he's a co-founder). You might also be interested
15.
by tomhoule 6y ago
(prisma migrate team member here) The development flow in migrate (the `migrate dev`) command is quite pedantic: it will check things like migrations missing from your migrations folder but already applied to the dev database, or migrations
16.
by tomhoule 6y ago
I can't claim to know the details, but my understanding is that the interaction of linear typing with dependent types is an open research problem (see the quantitative type theory papers, for example). It's also a burden on the us
17.
by tomhoule 6y ago
I am really enjoying lean 3 as a theorem prover; lean 4 as a programming language is a really intriguing/enticing prospect. The "functional but in place" paradigm is something quite new, as far as I can tell. For reference, s
18.
Leaning into Spivak's Calculus(tomhoule.com)
3 points by tomhoule 6y ago|0 comments
19.
by tomhoule 6y ago
Thanks for clarifying that the plan is to stop relying on it :) Is there a specific place/issue/ticket to discuss this? If time allows, I would be interested in helping out.
20.
by tomhoule 6y ago
I checked recently, and the Rust implementation of arrow — parquet as well — is sadly still not usable on projects using a stable version of the compiler because it relies on specialization. There are some Jira issues on this, but there doe