Advertisement · 728 × 90

Posts by Marc-André Giroux

Yikes

5 months ago 2 0 0 0
Preview
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
7 months ago 2 0 0 0

Yep! City is a little wild already 😵‍💫

10 months ago 0 0 1 0

classic 😛

1 year ago 1 0 1 0

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.

1 year ago 5 0 0 0

Sounds similar to “learned helplessness”

1 year ago 1 0 1 0
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,...

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...

1 year ago 59 22 4 1
Advertisement

💯 yes

1 year ago 2 0 0 0

🤣

1 year ago 1 0 0 0

😅💦

1 year ago 1 0 0 0
Preview
The MOIST Principle for GraphQL Schema Design Why MOIST is preferable to DRY when it comes to GraphQL Schema Design

New post 🌶️ The MOIST Principle for GraphQL Schema Design

1 year ago 15 6 5 1

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

1 year ago 1 0 1 0

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

1 year ago 0 0 0 0

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 year ago 0 0 1 0

"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 year ago 0 0 1 0

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 year ago 0 0 1 0

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

1 year ago 4 0 3 0
Advertisement
Post image
1 year ago 14 1 2 0

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

1 year ago 9 1 0 0

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.

1 year ago 0 0 0 0
Post image
1 year ago 3363 562 83 90

Eventually showed up :)

1 year ago 1 0 0 0

@support.bsky.team hmm none of my likes/follows seem to persist for some reason. Are there ongoing issues?

1 year ago 0 0 2 0

It was wild! Fun to bump into each other on slack 😅

1 year ago 1 0 1 0
Advertisement

Ah its at build time 😄

1 year ago 1 0 1 0

And then the uncached case slowly gets to 700ms because why not and destroys you when it ultimately happens 🤣

1 year ago 1 0 1 0
Post image

I'm way too late on the halloween memes, but it fit too well. Fun profiling afternoon 🙃

1 year ago 8 0 0 0
Preview
Rust Heap Profiling with Jemalloc Enabling Jemalloc heap dumps using jemallocator

New post www.magiroux.com/rust-jemallo...

2 years ago 0 0 0 0

Hello world

2 years ago 4 0 0 0