What is your favourite programming language?
1. |
 |
||
2. |
 |
||
3. |
 |
||
4. |
 |
||
5. |
 |
||
6. |
 |
||
7. |
 |
||
8. |
 |
||
9. |
 |
||
10. |
 |
||
11. |
|
||
12. |
 |
||
13. |
|
||
14. |
 |
||
15. |
|
||
16. |
|
||
17. |
|
||
18. |
|
||
19. |
 |
||
20. |
 |
||
21. |
|
||
22. |
 |
||
23. |
|
||
24. |
|
||
25. |
|
||
26. |
|
||
27. |
 |
||
28. |
|
||
29. |
 |
||
30. |
|
||
 |
Add a new answer! |
Topic Details
This topic was started by tdresser 
on May 5th, 2006. 170 grupies have voted on one or more of the 45 answers.
Tags: programming, technology
Comments |
Leave a comment
It's sad how quickly programmers and language publishers have jumped on the OOP bandwagon.
Yet people continue to wonder why code gets more and more bloated, slow, and buggy with each release. In theory OOP might be an OK idea, for large coding projects, produced by teams of programmers. But in reality, it just promotes lazy, buggy, slow, and otherwise crap programming.
See http://www.geocities.com/tablizer/oopbad.htm
When I think about the kind of fast, solid elegant code produced back in the day and look at the crap we have now, I'm just sickened.
If you look at the speed, and efficiency of some of the applications produced back in the days of slow processors and limited memory compared to what is crapped out of software houses now, it's sad.
Look at what people did on the C=64's and Apple II's and IBM PC's back in the day. Today's OOP programmer couldn't manage much more than "hello world" on them before running out of resources.