Comment by MeetingsBrowser 18 hours ago
I think there are plenty of context clues in the first few sentences.
> ... fascinated with BEAM, how it allowed easy spawning of processes ...
> ... the appeal of BEAM languages ...
> ... haven’t read The BEAM Book yet ...
> ... examples are written in Elm ...
That’s one reason Apache shouldn’t have used essentially the same name as a well-known VM released more than 20 years prior.
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?
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.
Who would look at something called The BEAM Book with a link to [1] and think that it refers to a book with a completely different title?
Because of you ask a person who works on Beam about “the Beam book” thats the one they are going to recommend. Who knows that the BEAM book is literally called “the BEAM Book”? There are many books like that, “the SRE book” is actually Site Reliability Engineering: How Google Runs Production Systems, etc.
> Who knows that the BEAM book is literally called “the BEAM Book”?
I mean, it's literally a link on a web page. You click the link, it takes you to The BEAM Book's page. This is why the WWW was invented, someone uses hypertext to create a link to something related to a reference. You click on the link, and you learn about what it is.
This keeps web pages from having to all include a full encyclopedia and dictionary and translations in 100 languages in every page. You use the technology of last century to create and integrate into a web of related content, where the links (ideally, but not always) contain additional related and informative content without the need to copy the contents of every page into every other page.
Those context clues do nothing for people who have no idea about BEAM but know about Beam and just think it's an uppercase version of it.
> ... fascinated with BEAM, how it allowed easy spawning of processes ...
beam runner spawns worker processes very easily
> ... the appeal of BEAM languages ...
You can write Beam workflows in Java, Python, Go and Scala
> ... haven’t read The BEAM Book yet ...
https://www.amazon.com/Streaming-Systems-Where-Large-Scale-P...
> ... examples are written in Elm ...
Hm, maybe they added Elm SDK for the Beam, but why?...