Downloaded 69 times
Uploaded byThoughtWorks
Present and Future of Programming Languages - ola bini
The document discusses the evolution of programming languages, from machine language to high-level languages like Ruby and Java, illustrating how each serves specific purposes while reflecting a balance of the software's nature. It touches on different paradigms and design philosophies in programming, hinting at the future developments in languages, including Ruby 2.0. The text emphasizes the importance of language expressiveness, design choices, and the ongoing need for diverse programming paradigms.
More Related Content
Similar to Present and Future of Programming Languages - ola bini
Present and Future of Programming Languages - ola bini
- 1. OLA BINI http://olabini.com söndag, 2010 mars 21
- 2. The Tao gavebirth to machine language Machine language gave birth to the assembler söndag, 2010 mars 21
- 3. The assembler gavebirth to the compiler Now there are ten thousand languages söndag, 2010 mars 21
- 4. Each language hasits purpose, however humble Each language expresses the Yin and Yang of software Each language has its place within the Tao söndag, 2010 mars 21
- 5. But do notprogram in COBOL if you can avoid it söndag, 2010 mars 21
- 6.
- 7.
- 8. Greenspun's Tenth Ruleof Programming söndag, 2010 mars 21
- 9. General purpose languages Special purpose languages Domain specific languages söndag, 2010 mars 21
- 10. Where are wenow? söndag, 2010 mars 21
- 11.
- 12.
- 13.
- 14. “Scripting” languages Pragmatic languages söndag, 2010 mars 21
- 15. Where did wecome from? söndag, 2010 mars 21
- 16. Ruby lineage söndag, 2010mars 21
- 17. a, b, c= 42, 69, 25 söndag, 2010 mars 21
- 18. def foo yield 42 3.times do |n| yield n*25 end end foo { |x| puts x } söndag, 2010 mars 21
- 19.
- 20. /^(d{3})-(d{4})$/ =~ phone_number söndag,2010 mars 21
- 21. $x = 42 @me = other @@foo += 2 söndag, 2010 mars 21
- 22. Global swearing $/ = “%” $= = true puts $! söndag, 2010 mars 21
- 23. puts “hello” unlessmoon == :full söndag, 2010 mars 21
- 24.
- 25. class MyNumber <Number; end söndag, 2010 mars 21
- 26. foo.send :answer?, 42 söndag,2010 mars 21
- 27. puts obj.methods.grep /=$/ söndag,2010 mars 21
- 28.
- 29. class Foo include ExampleMethods end baz.extend ExampleMethods söndag, 2010 mars 21
- 30. Lisp Machine Lisp söndag,2010 mars 21
- 31. def incrementor(x) lambda do next, x = x, x+1 next end end i = incrementor(10) i.call # => 10 i.call # => 11 i.call # => 12 söndag, 2010 mars 21
- 32.
- 33.
- 34. Good design isnot innovation Good design is choosing what to include - and what to not include söndag, 2010 mars 21
- 35.
- 36.
- 37.
- 38.
- 39. Object oriented programming söndag,2010 mars 21
- 40. Domain specific languages söndag,2010 mars 21
- 41.
- 42. Ceremony vs Essence söndag,2010 mars 21
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51. First class söndag, 2010mars 21
- 52. Focused or multiparadigm? söndag,2010 mars 21
- 53. Where are wegoing? söndag, 2010 mars 21
- 54. Is concurrency reallya large problem? söndag, 2010 mars 21
- 55.
- 56. More programming languages- not fewer söndag, 2010 mars 21
- 57.
- 58.
- 59. Higher level söndag, 2010mars 21
- 60. Slowness and wastefulness söndag,2010 mars 21
- 61.
- 62. Text based languages? söndag,2010 mars 21
- 63. AST languages? söndag, 2010mars 21
- 64.
- 65.
- 66.
- 67.
- 68.
- 69. It’s going tobe interesting söndag, 2010 mars 21
- 70. Where is Rubygoing? söndag, 2010 mars 21
- 71. Ruby 2.0 söndag, 2010mars 21
- 72. I don’t know söndag,2010 mars 21
- 73. Easier to modifythe language söndag, 2010 mars 21
- 74. Canonical AST söndag, 2010mars 21
- 75. Simplify the core? söndag,2010 mars 21
- 76.
- 77.
- 78.
- 79.
- 80.
- 81. The future söndag, 2010mars 21