Video

Great content 👌

Are you using a compiler? It is dealing with the concurrency you don't know is there, and interleaving operations to fit the cpu.

I don't think I've ever seen Joe so crazy before, and I loved every second of it 😂

"We"?

Next to the psychology of Jungs, Freud, Piaget -- there should be a school of psychology named after Prof Bartosz. He is absolutely crazy in a positive way.

Wow.. this is beautiful, like magic. "" Any sufficiently advanced technology is indistinguishable from magic ""

Simon Peyton Jones right next to Isaac Newton

🥰👏

Poor guy is massively uninformed as demonstrated by his complete unawareness of the Digital PDP-6 and PDP-10 family KA, KI, KL-10 processes providing commercially available time sharing starting in the 1960s. The major time sharing service CompuServe was based on PDP-10 mainframes running “the monitor” because the os never had a name for years. Eventually named TOPS-10. BBN added a paging box to create TENEX. PDP-10 time sharing user loads ranged from dozens up to just under a hundred users with uptimes of six months between re-boots. PDP-10s at national labs provided terminal front ends for clusters of CDC 6600/7600 mainframes, implemented the Ramada Inns inline reservation system. Bill Gates and Paul Allen learned to program on a Ten terminal.

Thank you for uploading this.

Really nice video apart from the fact you can't see the projector screen! It would be great to have the screen recorded and have that uploaded with voiceover

Analog computer cant be slow... There must be a design flaw in it or some other reason to give up on it to use as a flight simulator 😮

Otp

Otp

Great talk. Thank you for sharing!

W

Erlang doesn't have null? Why?

Have the same question why oops considered bad in consideration of functional programming, like adding opp in elixir is a bad idea ? If I'm correct. In some cases mutablity is required .

lol why are they laughing so hard??)))

At that time they still used TCP!!!!... today they don't even use software anymore!

This is not a nice presentation about the AGC, it's actually terrible. Sorry to say it... If you want nice ones try "xx7Lfh5SKUQ" and "B1J2RMorJXM". But the best one is Curios Mark fixing a real AGC "2KSahAoOLdU"

That was fascinating. But I actually wish it had been more of a discussion, because Joe Armstrong also has many interesting ideas.

This was interesting, but I found the presentation a bit disjointed.

Incredible

ITsMasqSKYen0z0oiParTean0BorLuzQwirqiEDwarDesPeedoJipooFin0SpuXtrashootERsawTeePirchFAwksr0ffOZappaDuzKoULABaBaLjYaTiVoLuzArcRedFooLAGasPinCApiToL0BellUSCooLYcaStowwwUN21tarGkldDigAnonzAWfeeGiFTen2ramTArinGodLord0FeNSeas0zuessGeeKAdAgolFBorlMaintolIBBspek2a1dreyPar0dok0nLANdaManonzBorl4poopeePeetee2bibzGnuArxCTexPlus11haREQwuoTorqz

0w0scheeReelINNsheepeeShagrazBorlFawksEF0LUmzP0zABelizMainTolivERhirzCul0BomapArFawksey2anonce4pay2rowLuzAKidKiLAbouyzeDEllair9K9UNfooNYfarMSpoJernMupit0FraGilWok0feeshbowLAg8prezENbooISPY0z0ffAz0wuvz!

learn trade off among write, space and read amplification, thks for sharing.

Sophie Wilson is a legend. Nobody else has influenced processor design as she did with the ARM. And her quips about Brexit were spot on too.

rip people with headphones

Great men!

We miss you Joe

Thanks for posting! Would it be possible to have captions available to us? Thanks.

As it turns out, dark red on brown wasn't very readable.

Excellent introductory video! Well done, sir.

I feel like a lot of people could chill right out if they knew joe had solved all their problems for them in the 80s

Still interesting in 2023! Does entity and models still part of Ecto?

Thanks man, I think you said reasonable things on writing a clean and decent library. Grazie mille!

All this shite and nothing built l0l.

everryone at everrely level of the company should learn about this

Logging in now to a *pause* state wide system. You're a voice over IP line?

This talk is great

I don't agree that a language should enforce limitations on programmers in favor of having maintainable code. Not everything is written for production. Ultimately, it should be the programmer's (or a company's) own right and responsibility to care about the future. If the language is structured to forbid things its designers consider bad, it will be an inconvenient language. It might work well for production, but would be a horrible choice for any sort of prototype or a small personal project. Flexibility should come first in a good general-purpose language. Don't treat programmers like fools that need strict guidance. If limitations could be beneficial, they should be opted in. EDIT: Moreover, even in production, there are cases where dirty hacks are beneficial. Debugging, for example, often requires to get your hands into somewhere they shouldn't be under normal conditions. Having a multi-language environment and forced separation prevents that. Simplicity is a great property, but it should be achieved constructively (i.e. not explicitly adding unnecessary features), not through explicit limitations

Amazing content from Martin as always. But even more than that, I am obsessed with the overall visual style/theme of these slides. It's just like the "`no make-up` make-up", probably took a lot of effort to appear as low effort. So good.

wow they said nothing for 70 minutes straight

😂❤

Interesting to see the damping of iterations per second as the system add procs. Should investigate all that jitter.

This talk made me angry, confused and happy at the same time

they won’t use it because it’s not Jewish.

One question - In the example which you have discussed suppose there is a network failure between A and B as well. so in that case what will be the expected behaviour? Will the entire cluster be paused OR cluster will continue to run with one node only serving the traffic?