And when you’re writing this program in this one’s language, now they’re tied together so the first program can’t go out and hunt and find other programs that implement the same service. They’re tied together. If this one’s language changes, it breaks this one. It’s really brutal, it doesn’t scale. And, worst of all, you have—it’s basically the machine code problem. You have a human doing low-level details that should be taken care of by the machine. So I’m pretty confident this is never going to happen. We’re not going to have API’s in the future.

10 March 2018 - But this was a current mind set because programmers did not see any value in learning something new. Today, I believe programmers are more open to adopt new technologies. For example, when a new language or library gets released which makes ...

Lambda the Ultimate

4 June 2017 - This talk by Bret Victor is an eye opener. It was delivered by Bret in 2013. He gave this talk assuming we are in 1973 and then talked about how future of programming will look like in 2013. He ta…

Answer: I'm sure there are other factors that contributed to them falling out of use, or being forgotten. What little I know about what affected this comes from some historical commentary I've read from someone who was a computer science researcher during this period that Victor discusses. Compu...

19 November 2013 - I'd disagree with your interpretation of the second portion of the presentation - coding environments themselves aren't the target; it's rather the applications that we end up building with them (I'm projecting off two examples, of course, but that's what gets lost when you're straining everything through that narrative conceit) - he asks for Bret Victor-style interfaces that make processes themselves transparent. (The closest such an interactive system manages to veer to a general-purpose language itself in his past work's been with a high-level interactive graphics library - "operations on visual objects", made transparent.)

21 January 2021 - For his recent DBX Conference talk, Victor took attendees back to the year 1973, donning the uniform of an IBM systems engineer of the times, delivering his presentation on an overhead projector. The ’60s and early ’70s were a fertile time for CS ideas, reminds Victor, but even more ...

30 July 2013 - For the first time in 20 years, we have a whole generation of programmers writing software which never runs on x86. As far as typing is concerned, Ruby has definitely pushed the boundaries of dynamic programming. Ruby has a fairly standard strong type system. Ruby's metaprogramming capabilities come from Smalltalk. As far as typed languages go, there are only hideous languages like Java and C#.

The best tech talks for developers

Bret Victor has ideas. https://youtu.be/8pTEmbeENF4 · There is a fundamental tension between “what computers understand how to do” and “the problems that humans are trying to solve with computers.” · Every programming language lies somewhere between one of these two fixed points.

3 October 2023 - In many (but certainly not all) of these domains, we already visualise (parts of) them in 2D (as charts), so I see no reason why this wouldn't apply here too · In my opinion, its not so important to solve the issue for every problem domain one might program in, but rather to do so for as many ...

17 February 2024 - The history and future of programming by Bret Victor In the beginning there were machine programmers. These were legends, such as John von Neumann who created foundational computational models in the …

10 May 2025 - No such item

2 weeks ago - He posits that people use computers ... future technology that can change its physical form. A major motivation for Victor's work is to make it easier and faster to use complex tools and ideas. As part of this project he wrote an essay about using interactive models when communicating about science, which popularized the term "explorable explanation". ↑ Victor, Bret...

14 July 2021 - It's too a comprehensive and far reaching essay for me to comment on in general, but I have a few random thoughts to share: · Right at the first example what immediately came to mind is simply having a better API. It's a boring but effective solution to say fill(color(r,g,b)). It also teaches ...

27 January 2023 - I'm much more curious about a programming paradigm that no longer uses text to communicate with computers but instead just directly manipulating data, receiving past, present, and future feedback of how it would change given your manipulations. Or to put it a different way "What if" feedback.

Login to LinkedIn to keep in touch with people you know, share ideas, and build your career.