Twitter | Search | |
Gary Bernhardt
the thirst quencher
68,974
Tweets
115
Following
26,218
Followers
Tweets
Gary Bernhardt 17m
Its conservative handling of nulls, no question. In python, [][0] raises an exception, but in Ruby it returns nil.
Reply Retweet Like
Gary Bernhardt 2h
RIP my notifications for three days now
Reply Retweet Like
Gary Bernhardt 2h
Replying to @galstar
I rarely write Python now, but unittest and its ilk are the state of the art. RSpec is syntactically impossible (and they like it that way).
Reply Retweet Like
Gary Bernhardt retweeted
amos 🍉 Sep 18
If your software is going to suck, this is the level of suck you should aspire to
Reply Retweet Like
Gary Bernhardt retweeted
Misty『Vote Yes 🏳️‍🌈』 Sep 17
Ora ora ora ora!
Reply Retweet Like
Gary Bernhardt 14h
Replying to @tpope
still among the greatest of tweets
Reply Retweet Like
Gary Bernhardt retweeted
Paige Bailey 2 Sep 16
"[Stopping math at Calc I] is roughly analogous to halting one's study of poetry at the level of grammar & syntax."
Reply Retweet Like
Gary Bernhardt Sep 18
Replying to @paulg @BrendanEich
What does it mean for a CEO to contribute attention, but not money, to a school?
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @tenderlove
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @schmonz
Yes, unless you modify the app to always send Connection: close, which would be an unfortunate constraint.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @schmonz
The forwarder needs to know when a new request starts (so it can restart), even if it's over the same connection as the previous request.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @schmonz
I wrote a little forwarder that restarts the server... then remember that, oh yeah, browsers don't close the connection after requests.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @ItizAdz
doubt it; when I describe the problem people just say "use guard", which literally does not solve the problem
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @garybernhardt
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @garybernhardt
To do it right, you have to trigger the server restart when the request begins, then forward the request only after the server restarts.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @garybernhardt
Watching files asynchronously to trigger restarts does not work. There's a race hole when the server is booting.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @dpkendal
that would be in-process with the server and so can't restart the server
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @theomn
Build a proxy, listen for HTTP requests, when one starts check for stale files, restart server if stale, and only *then* forward request.
Reply Retweet Like
Gary Bernhardt Sep 17
Replying to @theomn
That doesn't actually work, though. There's a race condition hole when you write a file, then reload the browser before the server comes up.
Reply Retweet Like
Gary Bernhardt Sep 17
Still can't believe that this doesn't exist.
Reply Retweet Like