Lightnews — Scholar-powered news

Marc-André Giroux @xuorig.bsky.social · Sep 4

a cartoon cat wearing sunglasses has the word omg on its chest

ALT: a cartoon cat wearing sunglasses has the word omg on its chest

media.tenor.com

2

Marc-André Giroux @xuorig.bsky.social · Jun 13

Yep! City is a little wild already 😵‍💫

1

Marc-André Giroux @xuorig.bsky.social · Apr 16

classic 😛

1 1

Marc-André Giroux @xuorig.bsky.social · Mar 14

Bored of Rust vs X posts that compare a lang a team has been working with for years vs what can be explained by unfamiliarity with Rust. Oh no we unwrap() on a map get and it panics! Control for familiarity with the language, and I feel like a lot of stuff starts looking similar.

5

Marc-André Giroux @xuorig.bsky.social · Feb 1

Sounds similar to “learned helplessness”

1 1

Reposted by Marc-André Giroux

Jean Boussier @byroot.bsky.social · Jan 23

I want to write a post about Pitchfork, but before I can get to that I need to share some thoughts.

I suspect this one may be more controversial than the optimizing JSON series 😅.

byroot.github.io/ruby/perform...

The Mythical IO-Bound Rails App

When the topic of Rails performance comes up, it is commonplace to hear that the database is the bottleneck, so Rails applications are IO-bound anyway, hence Ruby performance doesn’t matter that much,...

byroot.github.io

4 22 59

Marc-André Giroux @xuorig.bsky.social · Jan 11

💯 yes

2

Marc-André Giroux @xuorig.bsky.social · Jan 10

🤣

1

Marc-André Giroux @xuorig.bsky.social · Jan 10

😅💦

1

Marc-André Giroux @xuorig.bsky.social · Jan 10

New post 🌶️ The MOIST Principle for GraphQL Schema Design

The MOIST Principle for GraphQL Schema Design

Why MOIST is preferable to DRY when it comes to GraphQL Schema Design

buff.ly

5 6 14

Marc-André Giroux @xuorig.bsky.social · Dec 21

Yeah, at least it’s super cacheable so not generally a huge issue (although the miss can be nasty in JS)

1 1

Marc-André Giroux @xuorig.bsky.social · Dec 21

Yeah I think that’s part of the true overhead 👍

Marc-André Giroux @xuorig.bsky.social · Dec 21

Most commonly this leads to data-loading issues. Note that a sufficiently complex codebase will lead to very similar problems no matter the API style. GraphQL does put them in front of you sooner in the process.

1

Marc-André Giroux @xuorig.bsky.social · Dec 21

"resolvers" are almost always at the source of issues. Compared with endpoint-based APIs, in GraphQL, most fields operate with very local information and have a smaller "horizon" for optimization.

1

Marc-André Giroux @xuorig.bsky.social · Dec 21

GraphQL is slow, they usually fail to identify what is slow, and are rarely describing GraphQL's true overhead. Now, I do think GraphQL doesn't do a great job at creating a "pit of success" as far as performance goes. A naively implemented GraphQL API is most likely going to have serious perf issues

1

Marc-André Giroux @xuorig.bsky.social · Dec 21

Serious take about GraphQL performance since that is very often brought up these days: GraphQL's inherent overhead is mostly limited to its parsing/validation step and its execution engine logic. Eliminating or keeping that to a minimum is important and generally easy. In practice, when people say

3 4

Marc-André Giroux @xuorig.bsky.social · Dec 21

2 1 13

Marc-André Giroux @xuorig.bsky.social · Nov 22

Sometimes it really feels like the GraphQL subreddit is half ads, half how to use Shopify’s API 🤣

1 9

Marc-André Giroux @xuorig.bsky.social · Nov 22

You the first time you log errors in Rust coming from languages with exceptions with stack traces:

[ERROR] There was an error in your code base, good luck.