Comment by MeetingsBrowser
Comment by MeetingsBrowser 16 hours ago
This feels like willful ignorance.
Can you really read the blog without realizing that there is a possibility this isn’t referring to Apache beam?
Comment by MeetingsBrowser 16 hours ago
This feels like willful ignorance.
Can you really read the blog without realizing that there is a possibility this isn’t referring to Apache beam?
I think it’s an insecurity response— lashing out to distract themselves from feeling needlessly embarrassed for encountering something new or getting confused about something.
I hope you're not accusing the original commenter here of "lashing out" for wanting one definition at the start.
I was speaking more generally, but sure, I think the behavior fits. BEAM has a lot more surface area than Apache Beam does here — just do a site search for beam and see how far you have to go to see the Apache project. It’s ridiculous to expect the author of a blog post targeted at people interested in BEAM to disambiguate between them. Additionally, it’s a BEAM conference talk converted to a blog post and it says so right at the beginning of the article with a link to the conference. Thirdly, whoever submitted the link expecting a technical crowd to put in a modicum of effort to figure things out from context is completely reasonable. And how arbitrary is expecting the line to be drawn at your level of need? Shouldn’t project managers be able to read the article without having to look up VM meaning Virtual Machine? Or that functional programming isn’t any programming that uses a function? So yeah, I do not think it’s valid to criticize an author of a blog post aimed at people who already understand the subject for not putting a 1000’ overview at the top.
Nearly every personal blog post submitted here written for people that use a less-mainstream tool/environment/language draws aggressively obtuse comments by people mad that the author didn’t anticipate their lack of knowledge.