Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rbalicki
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
rbalicki
2y ago
Also NYC, also Miami. I never got this impression in the Bay Area when I lived there (10 years ago)
62.
▲
by
rbalicki
2y ago
I would think that once enforcement becomes automated (and thus applies to those with resources, who currently get away with it), there would be a lot of pressure on the legislature (by those who currently get away with it) to make the rule
63.
▲
by
rbalicki
2y ago
Genuine question: What is stopping some small percent of drivers from installing cameras and using ML to identify cars driving dangerously (e.g. speeding, running reds, changing multiple lanes at once, etc.), and when their license plate is
64.
▲
by
rbalicki
2y ago
Fragment composition. See my comment here https://news.ycombinator.com/item?id=40984066
65.
▲
by
rbalicki
2y ago
Certainly, if you can either force your clients to refresh their browsers or can tolerate clients breaking, that works! That might work great for internal tools, for example (as long as no work is lost when you refresh, or you can just expe
66.
▲
by
rbalicki
2y ago
You want to execute a single query for a given page for performance. But whether a field is included in the query should depend on whether a component uses that field. If you write the raw query without fragments, you introduce implicit cou
67.
▲
by
rbalicki
2y ago
> backend APIs Using GraphQL for service-to-service communication isn’t the sweet spot if you can deploy both services together. Rather, it’s great if the services are deployed on their own schedule. This is the case if one service is so
68.
▲
by
rbalicki
2y ago
I'm not sure I follow. Are you saying swr allows for fragments and deduplication? If you don't have fragments (in particular, if you have a single call to an swr hook at the root), then you have implicit deduplication. But then yo
69.
▲
by
rbalicki
2y ago
GraphQL gives you this. https://relay.dev/docs/guides/persisted-queries/
70.
▲
by
rbalicki
2y ago
GraphQL gives you the ability to compose fragments, so if the UserDetail component and UserPaymentInfo component both use the user’s name, it is loaded once. With ad hoc solutions like tRPC, you end up fetching the same field multiple times
71.
▲
by
rbalicki
2y ago
This solution works very well, and I’m surprised that others on this thread do not take advantage of persisted queries. Yes, it’s recreating REST, except that you don’t need to version endpoints, etc. The source of truth is the front end re
72.
▲
by
rbalicki
2y ago
Folks on this thread should check out Isograph: https://isograph.dev and https://www.youtube.com/watch?v=gO65JJRqjuc . GraphQL has a lot of advantages, the most important of which is data masking. In a properly s
73.
▲
by
rbalicki
3y ago
Thank you!
74.
▲
Isograph – the UI framework for teams that move fast – without breaking things
(isograph.dev)
3 points
by
rbalicki
3y ago
|
2 comments
75.
▲
by
rbalicki
3y ago
The problem with REST (or really, any current non GraphQL solution) is there is only an implicit link between the consumer of a field and the query declaration. So, REST queries are append only, especially at large organizations where incre
76.
▲
by
rbalicki
3y ago
It is unclear to me whether this "landed me a job", but in advance of working at big tech, I made a presentation about Smithy (www.smithy.rs), in which there was an engineer in the audience (employed at the same big tech co). I be
77.
▲
by
rbalicki
3y ago
Isograph is very much a work in progress, and more of an experiment to the improve developer experience of building GraphQL-backed apps than a production-ready framework. The other frameworks are production-ready. It has a lot of similariti
78.
▲
Isograph, GraphQL-powered React apps with great DevEx [video]
(youtube.com)
3 points
by
rbalicki
3y ago
|
2 comments
79.
▲
by
rbalicki
3y ago
This was an entertainingly written piece. Threads, as an MVP, does not yet have the ability to see only content from those you follow. That hardly means it won't. Already, activity from those you follow shows up first in your feed, so
80.
▲
Isograph: Build React apps backed by GraphQL data
(isograph.substack.com)
3 points
by
rbalicki
3y ago
|
0 comments
81.
▲
by
rbalicki
3y ago
Yes, the requirement that static constructors are used makes this substantially less ergonomic than it would otherwise be for the reasons you point out. Some of the React hooks in Isograph use this pattern, and as a result the constructor r
82.
▲
by
rbalicki
3y ago
In my opinion, this is a flawed proposal. The disposer should not be a method on the object, because it means it cannot pass around the resource without the risk that the recipient of the resource disposes it themselves. A safer alternative
83.
▲
by
rbalicki
3y ago
As someone who would like to use SQL to return a tree-like structure, how well does this scale (in terms of readability, performance, etc.) when the query is extremely large and nested? For example, if we are attempting to replace GraphQL w
84.
▲
by
rbalicki
3y ago
This word will soon be an OSS project/new startup/etc. Maldemoor. Brainslow. Chirminous. Hempress (if this isn't a smoke shop already...) All not bad.
85.
▲
by
rbalicki
3y ago
If I recall correctly, Datomic gives you the ability to query the database at a given timestamp. Are there other DBs with this feature that folks are aware of?
86.
▲
by
rbalicki
4y ago
The GP comment was written using ChatGPT- another project that wouldn't have happened without ChatGPT- and the training data cutoff was March, 2021.
87.
▲
by
rbalicki
4y ago
Your blog is my favorite tech blog! I especially liked the blog series that contained to mock a mockingbird. Thank you for your excellent contact over the years!
88.
▲
by
rbalicki
4y ago
oh, that's neat! I'll try that.
89.
▲
by
rbalicki
4y ago
I love being able to easily navigate between tabs (a/J and s/K for me), go back/forward (h and l), open the current tab in a new window, close the current tab, etc. though (of course) the killer feature is "link highligh
90.
▲
by
rbalicki
4y ago
I created my resume by building a one page website and having some script print it to PDF. Worked great, and was a nice talking point for interviews, until many years later I npm installed and it stopped working
More ›