Keynote. Fortress Features and Lessons Learned | Guy Steele | JuliaCon 2016
The Julia Programming LanguageCited 3× on HN, 2016-2022
15K views · 10 years ago · talk · evergreen
Guy Steele's JuliaCon 2016 keynote on the Fortress language, its features and the lessons learned from the project.
Cited as the authoritative first-hand account of the Fortress experience and of numerical computing language design.
1:07:22Invited Talk - Guy Steele
ClojureTV
39K views • 9 years ago
1:12:122017 ACM PPoPP Keynote: It's Time for a New Old Language
Guy Steele
7K views • 9 years ago
54:12OOPSLA Conference: Growing a Language
Computer History Museum
24K views • 6 years ago
53:31Growing a Language, by Guy Steele
Bill Pugh
165K views • 14 years ago
48:19GopherCon 2014 Inside the Gophers Studio with Blake Mizerany
Confreaks
8K views • 12 years ago
54:55Dconf 2014 Day 2 Keynote: The Last Thing D Needs -- Scott Meyers
The D Language Foundation
19K views • 8 years ago
52:40Keynote. Professor Steven G. Johnson | JuliaCon 2019
The Julia Programming Language
18K views • 7 years ago
1:13:00Jonathan Blow - Jai Demo and Design Explanation (KEYNOTE) - Updated
LambdaConf
241K views • 1 year ago
2:07:18Demo: Base language, compile-time execution
Jonathan Blow
164K views • 12 years ago
1:01:04Introduction to Julia - Part 1 | SciPy 2014 | David Sanders
Enthought
80K views • 12 years ago
1:58:46Dynamic Languages Wizards Series - Panel on Language Design
Eduardo Cavazos
16K views • 14 years ago
58:24#Gamelab2018 - Jon Blow's Design decisions on creating Jai a new language for game programmers
Gamelab Conference
210K views • 8 years ago
1:55:24Ideas about a new programming language for games.
Jonathan Blow
530K views • 12 years ago
56:36GopherCon 2014 Opening Keynote by Rob Pike
Confreaks
38K views • 12 years ago
1:07:00Sydney Golang Meetup - Rob Pike - Go 2 Draft Specifications
Macquarie Group
57K views • 7 years ago
55:08Rust: A Language for the Next 40 Years - Carol Nichols
ChariotSolutions
367K views • 7 years ago
48:46Rust's Journey to Async/Await
InfoQ
90K views • 6 years ago
42:45RustConf 2017 - Closing Keynote: Safe Systems Software and the Future of Computing by Joe Duffy
Confreaks
2K views • 9 years ago
1:05:56Lang NEXT 2014 Panel Systems Programming in 2014 and Beyond
25msr
3K views • 8 years ago
35:24The Unreasonable Effectiveness of Multiple Dispatch | Stefan Karpinski | JuliaCon 2019
The Julia Programming Language
79K views • 7 years ago
3 comments from Hacker News
I think in the constellation of languages there's still more intersection of "feature dots" between the two than there is disjunction. Multimethods & numerics emphasis alone makes them uniquely similar, as the latter especially is not a feature that has been mined well in other languages. Some of the influence is quite conscious, too, from my reading. And here's a talk by Guy Steele about the Fortress experience, at JuliaCon: ▶ this video
Julia is great for numerical computing, but it's not as good as it can be, even in that area. Widening the community's base of expertise will help. I'll just list a few things that come to mind. Many Base functions are currently untyped, which means it's hard to abstract out the key properties that enable reuse, compiler optimizations, and parallelism. See [0] for a language expert's take on numerical computing, which involves defining traits like associativity that enable automatic parallelism by default. A stronger culture of functional programming could make your code faster and easier to understand. It's often (though not always) easier for tooling to optimize pure functions over immutable data structures (and arrays). Arrays are currently mutable, and there is too much emphasis on mutating functions. The iteration protocol can be made more memory-efficient for large collections and simpler, following Rust's implementation [1]. Macros are useful for high-performance computing [4], and Julia's macros can be made more composable [2]. In general, systems languages don't make language decisions lightly. They have committees, discuss how other languages do things, make proposals. This allows more perspectives on each decision. That would be an improvement over the more ad-hoc style of Julia development, as long as Julia can avoid adding every possible feature, which is a risk of expanding the decision-making body [3]. [0] ▶ this video [1] link [2] link [3] link [4] link
> It got shelved after Oracle bought Sun. Actually the actual real history is little more complex than that. JuliaCon 2016 (Keynote) | Fortress Features and Lessons Learned | Guy Steele ▶ this video It would be good if people on HN would separate a bit the Oracle hate with the facts.