kshay

I like how he didn’t explicitly request 22. It was more like “anything 1-255 would be great... oh, by the way, I happen to be using 22...”

It seems like the U should be “Unambiguous” rather than “Ubiquitous”?

So basically Perl autovivification for Python?

Glider was the Flappy Bird of its day!

I’ve been using it for most of those years, and still use it every day. We recently had to wrangle a bunch of 400Mb+ XML files, and everyone else’s editor struggled even to open them, while I happily regexed my way around extracting various data.

However, I reluctantly have to say that when working with TypeScript codebases specifically, I do feel the lack of IDE features for recognizing imports and cross-referencing symbols across files. Any other BBEdit diehards in this position? What have you ended up doing?

I’m going to hear the Paul Simon lyric as “Don’t I know you from the megachiropteran’s party?” from now on

Hmm, pretty sure the Beav was long gone from the airwaves by 1969…

Yes, exactly. “Bake your mocks into your third-party library implementations” is an interesting idea and might be a useful thing to do, but it’s certainly not “testing without mocks.”

> The factory should create a “Nulled” instance that disables all external communication, but behaves normally in every other respect....

>...For example, calling LoginClient.createNull().getUserInfo(...) should return a default response without actually talking to the third-party login service.

So... a mock.