Satadru Pramanik, DO, MPH, MEng

I have personally had it bite me multiple times on a bunch of stuff. Enough that I would have been using blank a lot more than I have been using...

A function that routinely throws nomethod errors like `.empty?` does for stuff where it really shouldn't is IMHO broken.

_insert Joker meme..._

> fwiw, this is the [entire definition](https://justincypret.com/blog/activesupport-blank-vs-empty#blank-is-basically-an-alias-for-empty) of `.blank?`: > ```ruby > # lib/active_support/core_ext/object/blank.rb > class Object > def blank? > respond_to?(:empty?) ? !!empty? : !self > end > end...

> also why do we have code for editing package files in `lib/downloader.rb`??? > That's to automatically update hashes when building packages with version number updates. It's behind a force...

> > > fwiw, this is the [entire definition](https://justincypret.com/blog/activesupport-blank-vs-empty#blank-is-basically-an-alias-for-empty) of `.blank?`: > > > ```ruby > > > # lib/active_support/core_ext/object/blank.rb > > > class Object > > > def blank?...

You're removing the usage of the `.blank?` method in favor of streamlining. My logic is that I am insisting on keeping the method around because I have every intention of...

> my logic is that there's no need to use a helper method if we don't need to use it, and that it makes sense to limit checks to what...

> > Would it make sense to propose an upstream improvement to `empty` so it behaves like `blank`? It's confusing to have multiple functions when the proper expected behavior of...

> agree to disagree on this one-- i prefer to avoid defensive programming whenever possible, and i'd rather know exactly where my codebase is interacting with external data and the...