I watch this every year or two. ❤

Still the best talk on color spaces!

this is insane

He speaks English so well😂. Really like his way of introducing the history of all those punch cards and TTYs. Plus, the idea of interactive programming is quite useful in my opinion.

Love this video

This is a little hard to take in, but i can see there us future here. Amazing possibilities for such low power. Thank you Chuck.

❤❤

Too bad the stabilizer project seems to be dead. Anyone knows an updated version for llvm18+?

Such a great composition, delivered step by step. Very useful. Thanks for sharing.

Interesting idea about smaller language layers preserving more symmetries

When I first heard of the cut and fold theorem which was 29/9/2024 I folded a square using disk packing and then cutted it are got a square. which was easy to understand but this video explains the other very well. Also I like how like 99.9% of people are constantly watching things that make them addicted and mindless. Meanwhile the 0.1% are watching videos like yours constantly. Hopefully the next comment is in a few years if not months.

Ironic to be watching this, as I just so happen to be re-compiling my whole Nix store as ``content-addressed``. This man was and this talk is simply BRILLIANT. I wonder how many people know about Unison, which brings some of these content-addressable goodness to the world of programming.

Some facts are already outdated. F.e. MongoDB supports multi-document transactions even across shards, but anyway great talk

Please don't ever remove this. ❤

The "GLR" approach is a good generalisation of what we've been doing since the 1970's: simply treating most things as expressions, and only later hoisting out a contained L-value reference if it's required by context. So "L-value expected" becomes a semantic error rather than a syntax error.

Flutter 💙

I really enjoyed this video. Great presentation, very well spoken. Funny, and smart. Great job!

👍👍

100rabbits is the best. Really pushed me towards learning more about local-first software

2024 and it is still not possible to wish away state. Many thanks for this work! <3

Rip to a real one

Genius! Way ahead of his time

The definitive guide on ACID properties.

What a brilliant talk - honestly i wish it were longer

Or you can do what common lisp (in particular SBCL) does, add type inference within the runtime itself, when you type a function in the REPL you get the type analysis, and is Hindle Millner analysis. Steel-Bank Common Lisp uses the type analysis to increase performance of the code, due to its standard definition you can add type hints respecting the syntax predefined in the 1980s using primitives like `declare` Or you can use what Verse a functional-logic programming language for video-games by Epic does, uses functions as contracts in Scheme to use as types, oops we go back to Lisp baby. Maybe JavaScript should've never acquired the filthy Java -ness.

I've nodded all the way, but what the heck should I do now? For my tiny brain it was too "abstract", I need examples. Wonderful to say who, when, where... show me how, I mean please show me...

Point-free programming == pipelining?

24:03 I like Doug but unfortunately he's dangerously wrong about zen buddhism and misattributing perhaps one meditation practice that the west has imported (as analytical westerners we are specifically vulnerable to 'infinite reflection' type amusement). The utility of such a practice is to tire that mode and induce a non-concept state of being (like the fly) which can be therapeutic to some.

'A' 5 STO what syntax is this? can someone enlighten me?

9:20 begin with concept of perception : funneling impinging triggers a concept

Programming languages aren’t even 100 years old; I believe there’s SO much room for improvement and new ideas. Really appreciate the talk!

Not long time ago I started to use emojis 🙂🔈⚠️⛔ in terminal output. Never felt better to read logs

Amazing speech, watched it in one breath with a smile on my face

i dont know the game but a game did random generation with counting user inputs. i think it is a pretty clever aproach if not exposed.

I’d like to play the contrary here and propose the hypothesis that if our software was properly architected replayability or as we call it in this video time, travel bugging would be a part of the architecture rather than an afterthought that we need external tools for

Great talk, cheers

7:57 wow this has aged incredibly well with LLMs being the same thing but even worse

Best I have seen on CQRS and Event soursing

Wow really great talk! I’m coming from a JS/TS background and this was really helpful in understanding some things about both C++ (a language I’ve only a cursory understanding of) and Swift (same level), and just systems programming language concepts in general.

The first ten minutes are the *best* explanation of continuations on youtube, hands-down. Jay has a very lucid style of explaining, no hand-waving there. Yes, the list syntax is weird, but you don't really have to know anything to read it. I watched hours worth of other videos on continuations that at some point relied on TypeScript or Haskell knowledge, and lost me that way. A bunch of the remaining 30 mins went over my head, too. Planning to digest and revisit. I think it's worth it.

(mapcar #'1+ '(1 2 3))

Amazing lecture! So many important ideas and discoveries shared in less than a hour! Thank you Philip!

Nice video professor Milano.

I've been developing software for 15 years now and I only now learned about shellcheck. So yeah, "Where has this been all the time?" Spot on :D

The one thing I have not been able to find anywhere on KZbin is what kind of programs did they use to program these games?!

Just found this trying to optimize a 6 hour playlist for a friend's wedding. Thank you so much for this!!

Excellent talk! I remembered this from watching it back in 2016 so it must have made an impression on me. So innovative!

This is why static typing is a trap. Semantics about entities and their relations should not be static but dynamic. That’s where flexibility and adaptability comes from. Too many devs throw that away due to fear. “We never let you run a certain kind of mistake” feels safe, but in reality, “we can correct any kind of mistake while the program runs” is safer, and unlocks so many possibilities. Thanks to Sussman for making that trade off so clear in this talk!

The best explanations of proof, type, and history of algorithms! Seems a category? Yes I guess. Thanks a million man.

Very helpful for newbies like me!