As a musician, I’d say no. Sure, you don’t get the significance of “what is this Dorian thing” unless Scarborough Fair is playing, but nothing in the article really applies to hearing music.
> As a musician, I’d say no. Sure, you don’t get the significance of “what is this Dorian thing” unless Scarborough Fair is playing, but nothing in the article really applies to hearing music.
I don't know what's with the current flagging/downvoting trends on HN, comments get dead before I can reply.
That said, your view seems rather extreme. What would be the downside of illustrating at least some of the samples with audio clips?
Have never tasted it in my life and it already looks delicious. I love thick, flat noodles. I undercook fettuccine and ensure they stick together but I wonder if that would provide the same experience.
I used to work on public safety radio systems. Things which seem like minor issues like clipping the beginning of a transmission every now and then are showstopper defects in that space.
It’s because it can be the difference between “Shoot” and “Don’t shoot.”
Filter means to remove, not to add. Like `filter()` in Python or Swift being given a condition and a list and returning everything that meets the condition.
In image processing "filtering" has for over 30 years meant any algorithmic manipulation of an image as a whole (exhibit A: Photoshop's "Filters" menu). Simplest filters are also filters in the signal processing sense, but the meaning in this context is considerably broader than that.
I reckon filters were initially intended to remove specific frequencies/noise and the term grew from there. Which is how ffmpeg and other software ended up with video filters that don't actually remove anything.
Someone else mentioned lens filters as a possible source for the term but I'm pretty sure the signal processing term is at least partially responsible for the current usage.
I ran into something similar with maven builds today. Filtering resources with maven means replacing text in the resource with text from maven properties.
Hold on, what? Okay, return false if they aren't equal, then open another process to repeat this method once again in the shell... I can't guess the reason. Would you know if there is any reason this might have been done?
I wouldn't know the real reason for sure, but this seems plausible:
1) They got tired of having to modify C code and wait for the deploy cycle to modify the filter
2) Using, for example, the database would be more work than calling a shell script. On top of that, it might actually be beyond the abilities of the programmer involved.
3) The C code executes on an arbitrary machine. Hence the ssh to a specific machine, so that the shell script would only have to be maintained in one place