[flagged]
I feel like this is just an opportunity to either learn what it is or move on. That’s essentially what hn and “hacking” is, isn’t it? This post caught my eye because I was learning about BEAM just last week for the first time.
Writing your own BEAM
51–60 of 94 posts
Re: Writing your own BEAM
#52The BEAM is fascinating for many reasons, including being register-based. I really just wish the BEAM was portable in the way the JVM is. The BEAM hooks into so many system libraries, you must compile it on every flavor of linux instead of just unpacking a tarball. This means you either must use your distro package manager's version, or compile from scratch. If you want to control the exact version that's being used…
You want https://github.com/burrito-elixir/burrito
Burrito works very well in my experience. I've used it for distributing an implementation of breakout in Elixir with OpenGL and Metal rendering backends as a binary. Pretty neat!
Re: Writing your own BEAM
#53The BEAM is fascinating for many reasons, including being register-based. I really just wish the BEAM was portable in the way the JVM is. The BEAM hooks into so many system libraries, you must compile it on every flavor of linux instead of just unpacking a tarball. This means you either must use your distro package manager's version, or compile from scratch. If you want to control the exact version that's being used…
You want https://github.com/burrito-elixir/burrito
This is very neat, thanks for the link!
Digging into it, you can get "universal" BEAM tarballs from here[1]. It links against muslibc and appears to bring it's own openssl. Very cool.
Re: Writing your own BEAM
#54Earlier quoted context omitted.
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…
> I mean, it's literally a link on a web page. You click the link, it takes you to The BEAM Book's page.
Now instead of putting the details in the title, you have me reading paragraphs of text and clicking links to figure out what the author is talking about. Did I understand you correctly?
Re: Writing your own BEAM
#55[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…
> It has really become tiring to have a comment tree on every HN post
Has it actually? Why is this "tiring?"
> When can we be done with these cheap comments?
Do what most other people did. Write a cheap reply.
> you are taking that time to write a comment that only detracts from a possible conversation.
Just click the little [-].
> maybe you just close it and move on.
Ironic.
Re: Writing your own BEAM
#56I have learnt to love and embrace the BEAM. Wikipedia says "Originally BEAM was short for Bogdan's Erlang Abstract Machine, named after Bogumil "Bogdan" Hausman, who wrote the original version, but the name may also be referred to as Björn's Erlang Abstract Machine, after Björn Gustavsson, who wrote and maintains the current version." Whether the B is for Bogdan or Bjorn, there's something really fun and Space Quest-…
I like to think the B stands for BEAM.
Very cliché.
Re: Writing your own BEAM
#57The BEAM is fascinating for many reasons, including being register-based. I really just wish the BEAM was portable in the way the JVM is. The BEAM hooks into so many system libraries, you must compile it on every flavor of linux instead of just unpacking a tarball. This means you either must use your distro package manager's version, or compile from scratch. If you want to control the exact version that's being used…
Perhaps you should give Nix a try :)
Nix is enormously complicated, kind of unstable and not well documented.
I get that if you've gone through the pain of learning it you get a system with some very nice properties. But casually suggesting "maybe try nix" is a bit like telling someone who wants to listen to Mozart "maybe try playing a piano".
Re: Writing your own BEAM
#58Earlier quoted context omitted.
> 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…
> I mean, it's literally a link on a web page. You click the link, it takes you to The BEAM Book's page. Now instead of putting the details in the title, you have me reading paragraphs of text and clicking links to figure out what the author is talking about. Did I understand you correctly?
You are coming across as wilful, petulant and ignorant; hence stop digging the hole you are in. Don't argue for argument's sake.
We are not here to makeup for your shortcomings nor spoon-feed you knowledge in various domains.
People share whatever they want and if it is something i don't know anything about, i just do a quick Google search (eg. "what is BEAM in computer science") which immediately tells me what it is (especially the AI overview from Gemini at the beginning). You didn't even do this trivial step but are arguing that people should have anticipated your ignorance and handheld you; not going to happen ever.
Everything on HN can be categorized as one of; 1) Pointers to stuff(useful/useless/junk knowledge) 2) Opinions (clueless/beginner/intermediate/expert) 3) News. That's it; what you do with it is up to you.
Re: Writing your own BEAM
#59The BEAM is fascinating for many reasons, including being register-based. I really just wish the BEAM was portable in the way the JVM is. The BEAM hooks into so many system libraries, you must compile it on every flavor of linux instead of just unpacking a tarball. This means you either must use your distro package manager's version, or compile from scratch. If you want to control the exact version that's being used…
> The BEAM hooks into so many system libraries, you must compile it on every flavor of linux instead of just unpacking a tarball.
This isn't true, one can statically compile the BEAM for Linux exactly the same as the JVM. Here's an example: https://github.com/yoshi-monster/static_erlang/
Re: Writing your own BEAM
#60Earlier quoted context omitted.
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.
Erlang isn't even that obscure.