Matthew Draper

@[email protected]

[Matthew Draper @_matthewd]

@keithpitt @toolmantim There’s definitely a “Useless Use of Cat” joke somewhere in there

[Matthew Draper @_matthewd]

@jankomarohnic @nateberkopec Pubgrub was most of the gain in the resolver, yes.

I haven’t kept up with Bundler dev in the time since, so probably totally out of date, but at the time, I believe Gel was also independently faster at download, install, and require… plus no need for ‘exec’

[Matthew Draper @_matthewd]

@nateberkopec @tenderlove I mean... 😅😅😅

[Matthew Draper @_matthewd]

@nateberkopec Overhead of the actual hash lookup maybe, but I imagine it’d be dwarfed by query construction — at least outside the fast-path on .find

[Matthew Draper @_matthewd]

@sj26 Unfortunately not… I got as far as quotes and have then been procrastinating.

My designer recommended https://t.co/eib02aCU2s, who are not your brand of local, but might show the shape of company to look for? 🤷🏻‍♂️

[Keith Pitt @keithpitt]

Here are @buildkite’s internal engineering principles on how UIs should be built with our majestic @rails monolith:

[Matthew Draper @_matthewd]

@nateberkopec Except when building a subquery. Accidental where(..: ….pluck(..)) makes me sad.

[Matthew Draper @_matthewd]

@nateberkopec @tenlinesofcode @JacobDaddario Genuinely curious about the sorts of invocations you're seeing for relation.present? that don't lead straight into .each

Previously fun-policed in https://t.co/Gc8dZMMRIe — I haven't changed my mind yet, but you see more apps than I do, so maybe I'm missing some common pattern?

[Matthew Draper @_matthewd]

@jhawthorn @tenderlove There’s also separately the small matter of “at 100+ max conns, you should almost certainly be using pgbouncer”… but that’s PG scaling wisdom rather than Rails. (And in a far future, with fine-grained/per-statement connection pooling inside AR, maybe not required?)

[Matthew Draper @_matthewd]

@jhawthorn @tenderlove I want to make the AR pool unlimited by default, to save the “max = however many threads I intend to spawn” setting (now that we do scale down an idle pool). That leaves the DB-side limit, but I guess at least you’d be getting outright “server says no” errors then 🤷🏻‍♂️

[Matthew Draper @_matthewd]

@tenderlove Urgh. Is it from a common enough model that you could potentially obtain a chunk of the centre console from a scrapyard?

[Matthew Draper @_matthewd]

@tenderlove I think 3d laser scanning is a thing that sometimes co-exists with those "bring a file and 3d print your thing" places

[Matthew Draper @_matthewd]

@_byroot That’s a stack dup not a string dup, though, so while imperfect I wouldn’t expect it to alone account for a real measurable difference?

[Jean Boussier @_byroot]

Since this comes up often: IMO the rule of thumb for whether or not you should yank a gem release is: don't.

Two exceptions:
- The gem was pushed by an attacker who took over your account.
- Legal reasons (e.g. copyright, etc).

1/4

[Matthew Draper @_matthewd]

@mauro_oto @nateberkopec Good point, that really wasn't clear. Does this help? https://t.co/B93HO9F1Tk

[Matthew Draper @_matthewd]

@searls At first glance I thought that emoji was a banana peel.

Read into that as you will.

[Matthew Draper @_matthewd]

@ThomasCountz @rails @github @code @fatkodima @_byroot ApplicationRecord is defined by your app by default, not by Active Record. So the script could define one itself, but it's not necessary.

[Matthew Draper @_matthewd]

@ryanbigg I swear every time we fix something like this it quietly uncovers latent bugs for some people, and allows many more to write a nicer thing in future… but only hearing from all the people who insist the now-deprecated behaviour was clearly more correct is just so exhausting 😕