Artwork

Yigit Konur에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Yigit Konur 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Player FM -팟 캐스트 앱
Player FM 앱으로 오프라인으로 전환하세요!

What Languages Fix - The Problems Solved by Programming Languages

2:40
 
공유
 

Manage episode 383380166 series 3528180
Yigit Konur에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Yigit Konur 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

"This article written by Paul Graham in 2002 serves as a guide for those curious about which problem each programming language solves. Graham explains what needs different programming languages were created to meet or what problems to solve, and he also reveals the advantages and disadvantages of these languages against each other. This article is quite enlightening for those who want to better understand the relationship between programming languages.

---

# What Languages Fix (The Problems Solved by Programming Languages)

February 2002

Kevin Kelleher suggested an interesting way to compare programming languages: to describe each in terms of the problem it fixes. The surprising thing is how many, and how well, languages can be described this way.

**Algol**: Assembly language is too low-level.

**Pascal**: Algol doesn't have enough data types.

**Modula**: Pascal is too wimpy for systems programming.

**Simula**: Algol isn't good enough at simulations.

**Smalltalk**: Not everything in Simula is an object.

**Fortran**: Assembly language is too low-level.

**Cobol**: Fortran is scary.

**PL/1**: Fortran doesn't have enough data types.

**Ada**: Every existing language is missing something.

**Basic**: Fortran is scary.

**APL**: Fortran isn't good enough at manipulating arrays.

**J**: APL requires its own character set.

**C**: Assembly language is too low-level.

**C++**: C is too low-level.

**Java**: C++ is a kludge. And Microsoft is going to crush us.

**C**: Java is controlled by Sun.

**Lisp**: Turing Machines are an awkward way to describe computation.

**Scheme**: MacLisp is a kludge.

**T**: Scheme has no libraries.

**Common Lisp**: There are too many dialects of Lisp.

**Dylan**: Scheme has no libraries, and Lisp syntax is scary.

**Perl**: Shell scripts/awk/sed are not enough like programming languages.

**Python**: Perl is a kludge.

**Ruby**: Perl is a kludge, and Lisp syntax is scary.

**Prolog**: Programming is not enough like logic.

---

Relevant Keywords: comparison of programming languages, problems solved by programming languages, evolution of programming languages, Algol, Pascal, Modula, Simula, Smalltalk, Fortran, Cobol, PL/1, Ada, Basic, APL, J, C, C++, Java, Lisp, Scheme, T, Common Lisp, Dylan, Perl, Python, Ruby, Prolog, programming language fixes."

  continue reading

215 에피소드

Artwork
icon공유
 
Manage episode 383380166 series 3528180
Yigit Konur에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Yigit Konur 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

"This article written by Paul Graham in 2002 serves as a guide for those curious about which problem each programming language solves. Graham explains what needs different programming languages were created to meet or what problems to solve, and he also reveals the advantages and disadvantages of these languages against each other. This article is quite enlightening for those who want to better understand the relationship between programming languages.

---

# What Languages Fix (The Problems Solved by Programming Languages)

February 2002

Kevin Kelleher suggested an interesting way to compare programming languages: to describe each in terms of the problem it fixes. The surprising thing is how many, and how well, languages can be described this way.

**Algol**: Assembly language is too low-level.

**Pascal**: Algol doesn't have enough data types.

**Modula**: Pascal is too wimpy for systems programming.

**Simula**: Algol isn't good enough at simulations.

**Smalltalk**: Not everything in Simula is an object.

**Fortran**: Assembly language is too low-level.

**Cobol**: Fortran is scary.

**PL/1**: Fortran doesn't have enough data types.

**Ada**: Every existing language is missing something.

**Basic**: Fortran is scary.

**APL**: Fortran isn't good enough at manipulating arrays.

**J**: APL requires its own character set.

**C**: Assembly language is too low-level.

**C++**: C is too low-level.

**Java**: C++ is a kludge. And Microsoft is going to crush us.

**C**: Java is controlled by Sun.

**Lisp**: Turing Machines are an awkward way to describe computation.

**Scheme**: MacLisp is a kludge.

**T**: Scheme has no libraries.

**Common Lisp**: There are too many dialects of Lisp.

**Dylan**: Scheme has no libraries, and Lisp syntax is scary.

**Perl**: Shell scripts/awk/sed are not enough like programming languages.

**Python**: Perl is a kludge.

**Ruby**: Perl is a kludge, and Lisp syntax is scary.

**Prolog**: Programming is not enough like logic.

---

Relevant Keywords: comparison of programming languages, problems solved by programming languages, evolution of programming languages, Algol, Pascal, Modula, Simula, Smalltalk, Fortran, Cobol, PL/1, Ada, Basic, APL, J, C, C++, Java, Lisp, Scheme, T, Common Lisp, Dylan, Perl, Python, Ruby, Prolog, programming language fixes."

  continue reading

215 에피소드

모든 에피소드

×
 
Loading …

플레이어 FM에 오신것을 환영합니다!

플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.

 

빠른 참조 가이드