Skip to content
Hallway
0:00 / 0:00

#roc#elm

Richard Feldman, "Pushing Boundaries with Roc"

Houston FPUG

954 subscribers • 3 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Lobsters.
  • Presented by Richard Feldman

Intermediate. Assumes working knowledge.

11K views4 years ago1 recommendation

Programming languagesLanguage design and type systemsFunctional programming

Richard Feldman compares Roc with imperative languages to show how the purely functional language pushes the boundaries of performance and developer experience.

Roc is a purely functional programming language. It’s currently in a pre-release stage of development, but it already has a lot of interesting characteristics. This talk walks through three code bases for the same application – one written in Roc, and the other two in popular imperative languages (one dynamically typed and one statically typed), and shows how Roc is pushing the boundaries of what’s been possible in traditional dynamically typed or statically typed languages.

Why it's here

1 person recommends this

What people say. Recommended for its deep dive into the design goals and features of the Roc programming language.

Moments people linked to

restrictedchoiceon Lobsters • Recommends

Pushing Boundaries with Roc
12View on Lobsters

u/renatoathaydesin r/Zig • Mentions

On “What about Zig don't you like?”

I think the best way to go about it is like the Roc language does it. It has a strict, sound type system, but you are allowed to run a program that has type errors if explicitly asked to, and it "might" work if the errors are never reached in the execution path. Extremely useful during early development. You can write functions that are not even implemented yet while you design your program... then implement only partially and run it to test the parts you've implemented. This video explains it well: link to this video I think Zig already has something almost like this as I think the compiler just "skips" compiling stuff that's not used yet? Would be nice to expand that to be more like Roc.
2View on Reddit

u/stroboroboin r/dotnet • Mentions

On “How to compile broken code?”

…for prototyping. TDD has originally become big in dynamic languages, and the workflow would be test first, implementation second. Partial type checking is actually a feature of the Roc programming language, which would replace broken code with an exception – when you ask for it. Maybe you'd be interested in this talk, that touches on the subject: link to this video…
-1View on Reddit