Cool talk, hope to see more demystify content like this. Though the speech could be improved, but it's fine afterall.

Yes. And object orientation is antithetical to software engineering.

Really interesting stuff, lot of things i actually used, but didn't fully get. The presentation made some things clearer. Thanks

you don't have mutable data, data is always immutable, what is mutable is the memory, the storage where we put that data in. Variables & pointers are an abstraction on memory, for direct & indirect access respectively, and what functional programming is about is to make our code dependent on values and not on memory locations, traditionally the FP community call this, referential transparency, but the clever guys for the imperative world have given it a better name, value semantics.

ok, tell me you don't understand types without telling me you don't understand types. *types don't fix the understanding of anything.* *types are markets, tags that track code where certain assumptions about the code where made* so when you need to make changes you can follow the types and change all the places where you have changed your assumptions and understanding.

the anonymous tagged union is the breakthough

I have to admit, I love ML syntax, it looks so much cleaner to me than other languages, some people prefer the English looking stuff but for programming languages English looking stuff is sub-optimal for my taste. I still prefer S-expressions syntax. people don't understand how to code with Dynamic languages. the main mistake they make is to focus only on types, also if your reference as dynamic language is Python or Ruby then you are lost. Your reference should by Common Lisp & Smalltalk & Erlang, those are the real dynamic languages, Ruby & Python follow the same static philosophy of UNIX, even som lisps like Scheme & Emacs lisp & some smalltalks like GNU Smalltalk follow the static nature. Common Lisp & Squeak Smalltalk are the standard for Dynamic languages.

Thank you very much for this presentation

Thanks for a look in the F# kitchen. I am lucky for getting to use F# for my job. You are all doing a great job thanks!

This is an awesome video, just what is needed to enlighten things about Haskell-related stuff, and that it is really interesting and nice to do :)

Give us the BEAM and Roc will become the ultimate overlord 3000 language of all the predictable futures

Oh, wow. A couple months ago I was thinking about how it would be possible to write extensible software without compromising on security, the idea of platforms is super interesting, and could be this languages killer feature

@19:00: The type system can actually help you: type AddIns = "a" | "b" | "c" | "d"; type SelectedAddIns = { [key in AddIns]?: number; }; const coffeeForMe: { selectedAddIns: SelectedAddIns } = { selectedAddIns: { a: 1, x: 5, // <-- This is not covered by the type definition. Keys must be one of AddIns }, };

It's always the jump from the free monad to actually extensible effects that trips me. It's reasonable how you can handle a single effect by encoding it as a value and threading it, but the moment you introduce multiple effects things get quite complicated, specially the part where you track at the type level which effects have already been handled. Unfortunately this presentation did not get to that part 😞

The genius of that data structure. It's part of the niceness of JSON or dot files. Must've been tortuous for Microsoft engineers to stitch together COM, let alone the varying NET Frameworks (and their respective convoluted graphical kits)

Very effective talk 😂

1:07:00 The Pseudoinverse of a matrix is also defined for non-square matrix, that's why it is the Pseudoinverse and not the plain matrix inverse. Hmatrix.pinv supports that (like Numeric.LAPACK.Singular.pseudoInverseRCond).

1:00:00 I'd like to see how the famous proof of the uniqueness of the Pseudo inverse given the Penrose axioms can be writtenin Agda.

Just don't.

This language is so cool!

People have been using multiple languages since forever. Linker scripts, make files, autoconf, the list goes on. Also, how is this related to functional programming? It looks might it might be related to dataflow programming, but i don't see higher order functions

I love the mortgage calculator as an example of a responsive layout because when flipping the screen the layout itself doesn't change at all, everything just gets wider by a seemingly completely arbitrary amount so that nothing lines up anymore. I also love the color picker. It's very responsive until the available vertical space gets too small and it hits a debugger break point and freezes the application. Very production ready. It also really doesn't want to starts scrolling, it just shrinks and/or hides content.

I wasn't expecting this version of the language to be so good. the ! operator is beautiful

I'm tired of the hobby languages, what problem is Roc solving specifically? If there's no specific problem it solves it's a waste of time.

Really not a fan of the idea of "try->throw->catch-> try again inside the function that threw" idea near the end, that sounds like itd be extremely hard to reason through. Maybe resumes that affect the control flow of the thrower should explicitly be passed in as an argument and if they dont apply they go back up as normal and if they do they try the passed in thing

Roc has matured a lot since last time I watched Richard's talk. Will give it a try!

wow, this person need to speak more. really nice project.

Wow, that's big news about you joining Zed. Grats for that. Looks like Roc is ready for someone (probably me) to implement Bye Bye Hello World.

haskell + rust + typescript. very interesting

Richard is a fantastic presenter.

Sounds like mixture of OCaml and Nim with a platforms feature. Sounds great

A bit like Gleam without the BEAM?

Thanks for the talk and demo..😀 I'm looking forward to trying out the language.

Would it be possible to use Roc as a scripting language in a game? Writing a custom platform to provide all interactions with the game. And have it safely run on players pc?

It will be interesting to see the governance model for this language. I have used Elm in the past. Richard was also part of the Elm team. Elm is “public source” and not open source. You can not meaningfully contribute to the language if you are not part of the team. It is also the only language I know where FFI can only be used by packages that the language authors write. I will not use any language that has not reached 1.0 yet if I’m not comfortable that I can fix the bugs in the language that I run into.

it's unusual to follow along with a video where the person live coding is using 1 release ahead of what the github pushes for every package lol I guess this video will stay relevant for longer that way though

someone get this man a bag of money, its stuff like this that can take Fsharp to many more users

The REPL is broken on the front page: i.imgur.com/9biAk8A.png

Richard Feldman is such an engaging and captivating presenter. He comes across as congenial and curious and it's always a pleasure to watch his talks. Really rooting for roc and I can see it's getting to a point where I could start using it myself!

Very interesting. If I’m not mistaken, different platforms could have completely different implementations of Stdin and Stdout?

🔥

It is amazing, looks like a dream came true.

Wonderful talk, Richard is always on point, super engaging and insightful. Gotta turn off copilot though 😅

Cool! Thanks for share!

I'm very excited to watch this through. Roc, along with Zig, is one of the newer programming languages that's grabbing my attention!

Woo! Roc! 🎉

Bro just invented Free Monad

❤❤👆😃

Awesome talk! 1:01:41 was that a family guy reference I spotted? 😄

Thank you Kit! The progressive enhancements and your animations made it very easy to follow. Love your enthusiasm.