[flagged]
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
Writing your own BEAM
11–20 of 94 posts
Re: Writing your own BEAM
#12[flagged]
I think its written for people who already know what the BEAM is. The BEAM is the VM for Erlang or Elixir, similar to how Java has the JVM and C# has .NET essentially.
I'm pretty sure that in this analogy, C# has the CLR.
Re: Writing your own BEAM
#13[flagged]
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
That's all it takes. When you're writing about a niche topic (and nearly everything and anything interesting is a niche topic) then explain your jargon. It's considerate, reminds people who are familiar but might have forgotten, and introduces people unfamiliar with it to what your topic is.
Sometimes people want to understand what they're reading about and not have to play a little "guess what this is about" game. Clarity is a quality of good writing.
Re: Writing your own BEAM
#14Earlier quoted context omitted.
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
> I was always fascinated with BEAM (Bogdan Erlang Abstract Machine, a VM for languages like Erlang and Gleam) and how it allowed easy spawning of processes that didn’t share state, allowed for sending and selectively receiving messages, and linking to each other thus enabling creation of supervision trees. That's all it takes. When you're writing about a niche topic (and nearly everything and anything interesting is…
Re: Writing your own BEAM
#15[flagged]
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
The tone in which people like the parent comment is disgraceful. I’m sorry this is hacker news and hackers know that BEAM is the Erlang VM, no introduction or explanation needed. It is respected and admired as a great piece of engineering to be studied by all hackers.
Re: Writing your own BEAM
#16Earlier quoted context omitted.
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
> I was always fascinated with BEAM (Bogdan Erlang Abstract Machine, a VM for languages like Erlang and Gleam) and how it allowed easy spawning of processes that didn’t share state, allowed for sending and selectively receiving messages, and linking to each other thus enabling creation of supervision trees. That's all it takes. When you're writing about a niche topic (and nearly everything and anything interesting is…
Re: Writing your own BEAM
#17Earlier quoted context omitted.
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
Agreed. The tone in which people like the parent comment is disgraceful. I’m sorry this is hacker news and hackers know that BEAM is the Erlang VM, no introduction or explanation needed. It is respected and admired as a great piece of engineering to be studied by all hackers.
Re: Writing your own BEAM
#18[flagged]
When can we be done with these cheap comments? It has really become tiring to have a comment tree on every HN post for people who don't know what the article is about. As the author often didn't submit their own article it is just a complaint with no possible resolution. Instead of taking a few seconds to find out what the article is about and maybe even clarifying it for your fellow readers, you are taking that time…
I still remember 14 years ago or so, when applied science posted his diy electron microscope build and a handful of top comments were low effort nerd snipes and criticisms.
Nothing to do about it, I don't think. Its the warty culture here.
Re: Writing your own BEAM
#19Earlier quoted context omitted.
[flagged]
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 ...
Re: Writing your own BEAM
#20Earlier quoted context omitted.
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 ...
[flagged]