Earlier quoted context omitted.
Very cliché.
Hey it’s a classic for a reason.
Because people are unoriginal.
Writing your own BEAM
71–80 of 94 posts
Re: Writing your own BEAM
#72Earlier quoted context omitted.
Hey Dylan, you’re being an ass. Their tone was disgraceful, let me explain by giving you an example of how posts should be made. “Hey! This looks interesting, quick search on Google didn’t explain what the BEAM is as well as I would like, can someone let me know what this is about in layman’s terms?” This is inviting people to talk about the topic at hand. It puts the responsibility of knowing something squarely on t…
So, question. Are you upset the blog author did go put in an extra sentence to say what BEAM is? Is that playing into the disgrace?
Oh do get a hobby Dylan.
Re: Writing your own BEAM
#73Re: Writing your own BEAM
#74Earlier quoted context omitted.
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".
How is it unstable? It's one of the most reliable pieces of software I have used honestly.
In any case 'nix-shell -p erlang|elixir' does not seem too complicated to me.
Re: Writing your own BEAM
#75Earlier quoted context omitted.
> You're looking at where I told someone not be rude That’s just it, you didn’t tell them not to be rude. You hid behind nebulous shunning of “gatekeeping”. >I want them to recognize that a lot of qualified people don't in fact already know that specific thing Again, you didn’t actually do that though, did you? Instead you used the term colloquially meant to signal they are creating a “hostile” environment > Also, if…
> Again, you didn’t actually do that though, did you? Instead you used the term colloquially meant to signal they are creating a “hostile” environment > nebulous I think you have an incorrect idea of what the word gatekeeping means. It's not nebulous. It's saying they're doing a bad thing (being rude/synonym) by applying incorrect and artificial criteria about who is in a group (which I quoted). Both versions of my c…
No I understand clearly, it’s a weasel word and I dislike it. You use it to mask a personal attack (calling him an “ass”), shun behavior, and avoid the actual conflict of directly addressing what was said. Its annoying passive aggressive bullshit verbiage.
Calling out “gatekeeping” is virtue signaling at its very core.
Re: Writing your own BEAM
#76Did not know about it much before but apparently was doing something similar (in spirit) when experimenting with simple task execution queues in go. This is quite interesting and given that hot code reloading is a thing in beam it might be something to explore further.
Re: Writing your own BEAM
#77Re: Writing your own BEAM
#78Earlier quoted context omitted.
Hey Dylan, you’re being an ass. Their tone was disgraceful, let me explain by giving you an example of how posts should be made. “Hey! This looks interesting, quick search on Google didn’t explain what the BEAM is as well as I would like, can someone let me know what this is about in layman’s terms?” This is inviting people to talk about the topic at hand. It puts the responsibility of knowing something squarely on t…
So, question. Are you upset the blog author did go put in an extra sentence to say what BEAM is? Is that playing into the disgrace?
Re: Writing your own BEAM
#79Earlier quoted context omitted.
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.
Re: Writing your own BEAM
#80The 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 is fascinating for many reasons, including being register-based.
> I really just wish the BEAM was portable in the way the JVM is.
Inferno is both register based and highly portable using the same tool chain as Plan 9 which runs seamlessly across multiple architectures. This eventually evolved into the Go tooling as Rob Pike came up with the Plan 9 design and worked on it with Ken Thompson. https://seh.dev/go-legacy/
Unfortunately Inferno was never fully completed and bit-rotted a bit but it still builds on systems with 32 bit support. There are various forks and even an attempted 64 bit version. To me its a great design as it not only runs on bare metal but also has a hosted option so it runs under Plan 9, Windows, MacOS/Unix/BSD/Linux. Talk about a portable OS...