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?
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.
> There's nothing in the underlying HTTP response from https://csvbase.com/meripaterson/stock-exchanges that tells me I can get an HTML or CSV version. Is there a JSON version available? What other variants exist? How do I know that this URL will deliver different responses?
Well, you can send a HEAD request with a given accept: header to find out what you’ll get without actually fetching the data. But it’s true that it would be nice to have the full set of possible responses advertised somehow.
Honestly, the thing about other sites using your GA tag seems like the biggest red flag/potential for some Google algorithm to have actively started penalizing you. The timing doesn’t quite track, but maybe some interaction between that and the spam update?
> It's not one thing that cause the drop but a combination of things
Let me propose a bold generalization based on observations of sites of all sizes wrestling with Google over the last 20 years, and to which there are certainly exceptions (this case may be one):
It’s always one thing.
Of course, there are always a multitude of improvements that can be made to nibble around the edges and get incremental improvements in various metrics. And a gradual change in traffic may have several simultaneous sources.
But when the effect is an identifiable precipitous drop in search traffic, almost all the time, it turns out there was a single reason, whether a change Google made or a change the site made.
This may be a totally unhelpful observation, and feel free to ignore it. But in these situations I’ve come to find it’s more fruitful to look for A Cause than to approach it as “a little here, a little there.”
