PokeVideoPlayer v0.9-rev1 - licensed under gpl3-or-later
Views : 160,670
Genre: Science & Technology
Uploaded At Aug 29, 2024 ^^
warning: returnyoutubedislikes may not be accurate, this is just an estiment ehe :3
Rating : 4.935 (77/4,635 LTDR)
98.37% of the users lieked the video!!
1.63% of the users dislieked the video!!
User score: 97.56- Overwhelmingly Positive
RYD date created : 2024-10-10T00:34:50.38294Z
See in json
Top Comments of this video!! :3
They didn't have the idea of virtual machines back then, lol. Kids. BEAM was a play on JAM (Joe's Abstract Machine), a precursor to BEAM. JAM was a play on WAM (Warren Abstract Machine) a prolog abstract machine. Before that there was Pascal a decade earlier
5:30 sounds like MULTICS.
Not knocking Erlang, but there was a lot going on in the world of CS that Erlang inherited and evolved into a unique solution for its problemspace
50 |
7:52 Using chat gippity to look up facts, big yikes
Per Wikipedia: Early programming languages with pattern matching constructs include COMIT (1957), SNOBOL (1962), Refal (1968) with tree-based pattern matching, Prolog (1972), St Andrews Static Language (SASL) (1976), NPL (1977), and Kent Recursive Calculator (KRC) (1981).
124 |
Great video! Erlang is a fantastic technology which definitely deserves more attention! And Elixir has brought some new energy to the whole ecosystem!
One remark about "let it crash", though. It's a common misconception, but it's not there to allow for avoiding proper handling of edge cases.
When you think of it in general, there are two types of errors: those you can avoid (logic aka programmer errors) and those you can't (hardware failures: disks malfunctioning, network packets dropped, etc.). ""Let it crash" utilises process supervision, i.e. restarts of some parts of an application. If data doesn't change and there's a logic error in the code (an edge case missed), then it's as likely to occur after a restart as it does in the first place, i.e. "let it crash" doesn't solve programmer errors, because trying again doesn't solve the problem in code. It's there for the errors one cannot avoid and cannot foresee, like corrupted network packets, faulty hardware, or others components' nondeterministic misbehaviour.
Happy to see Erlang and Elixir material on YouTube!
18 |
My hat's off to the Swedish engineers for inventing something that satisfied an immediate need, and unforeseenly carried on to spark on further inventions. I was in an industry where parallel processing of data was almost required, this was the final years of the transputer. It was close, we could have chosen Erlang, but the processor speed slope took us to conventional toolchains and at first single thread workloads.
7 |
Well actuallllllly...... Erlang was 1986, the "official" birthdate of the internet was 1983, so technically the internet existed before Erlang :) Now if you mean 'The Web' or the 'WWW' then yes, because WWW was 1989. It's a common mistake people make, The Internet != The WWW. The WWW runs on-top of The Internet.
106 |
prolog (72) was a year earlier than ml (73) and had pattern matching, plus there were apparently older languages on ibm mainframes that also had it - at least wikipedia says s, and i'm a lot more inclined to believe that than whatever chatgpt hallucinated, Theo pls (edit: oop, not the first to see that)
10 |
10:14 Hot swapping in java is actually possible but there are a lot of constrains. Small changes can be done quickly without any effort (especially useful when debugging larger applications), but removing / adding classes etc. is normally not possible. There are projects tho that managed to aid in this manner but I can't remember how well they work.
29 |
7:37 At a glance of that article, "Core Erlang" isn't normal Erlang; it's an intermediate representation produced by the compiler that programmers woudn't normally see.
9 |
@swodaw1247
1 month ago
theo should grow his mustache out and cosplay as dr eggman
505 |