Object-oriented programming - Revision history

SdkbBot: Fixed consecutive punctuation error and general fixes (task 3)

2025-05-26T22:41:26Z

Fixed consecutive punctuation error and general fixes (task 3)

OAbot: Open access bot: url-access updated in citation with #oabot.

2025-05-25T01:03:44Z

Open access bot: url-access updated in citation with #oabot.

← Previous revision		Revision as of 01:03, 25 May 2025
Line 240:		Line 240:
	[[Paul Graham (computer programmer)\|Paul Graham]], a well-known computer scientist, believes big companies like OOP because it helps manage large teams of average programmers. He argues that OOP adds structure, making it harder for one person to make serious mistakes, but at the same time restrains smart programmers.<ref name="graham">{{Cite web\| last=Graham\| first=Paul\| title=Why ARC isn't especially Object-Oriented.\| url=http://www.paulgraham.com/noop.html\| publisher=PaulGraham.com\| access-date=13 November 2009\| author-link=Paul Graham (computer programmer)}}</ref> [[Eric S. Raymond]], a [[Unix]] programmer and [[open-source software]] advocate, argues that OOP is not the best way to write programs.<ref name="Eric S. Raymond 2003"/>		[[Paul Graham (computer programmer)\|Paul Graham]], a well-known computer scientist, believes big companies like OOP because it helps manage large teams of average programmers. He argues that OOP adds structure, making it harder for one person to make serious mistakes, but at the same time restrains smart programmers.<ref name="graham">{{Cite web\| last=Graham\| first=Paul\| title=Why ARC isn't especially Object-Oriented.\| url=http://www.paulgraham.com/noop.html\| publisher=PaulGraham.com\| access-date=13 November 2009\| author-link=Paul Graham (computer programmer)}}</ref> [[Eric S. Raymond]], a [[Unix]] programmer and [[open-source software]] advocate, argues that OOP is not the best way to write programs.<ref name="Eric S. Raymond 2003"/>

	Richard Feldman says that, while OOP features helped some languages stay organized, their popularity comes from other reasons.<ref>{{cite web \|last1=Feldman \|first1=Richard \|title=Why Isn't Functional Programming the Norm? \|website=[[YouTube]] \|date=30 September 2019 \|url=https://www.youtube.com/watch?v=QyJZzq0v7Z4&t=2069s \|language=en}}</ref> Lawrence Krubner argues that OOP doesn't offer special advantages compared to other styles, like functional programming, and can make coding more complicated.<ref name="lawrence">{{Cite web\| last=Krubner\| first=Lawrence\| title=Object Oriented Programming is an expensive disaster which must end\| url=http://www.smashcompany.com/technology/object-oriented-programming-is-an-expensive-disaster-which-must-end\| publisher=smashcompany.com\| access-date=14 October 2014\| archive-url=https://web.archive.org/web/20141014233854/http://www.smashcompany.com/technology/object-oriented-programming-is-an-expensive-disaster-which-must-end\| archive-date=14 October 2014\| url-status=dead}}</ref> [[Luca Cardelli]] says that OOP is slower and takes longer to compile than procedural programming.<ref name="badprop">{{Cite journal\| first=Luca\| last=Cardelli\|title=Bad Engineering Properties of Object-Oriented Languages \|url=http://lucacardelli.name/Papers/BadPropertiesOfOO.html\| year=1996\| access-date=21 April 2010\| doi=10.1145/242224.242415\| journal = ACM Comput. Surv.\| volume=28\| issn = 0360-0300\| pages = 150–es\| author-link=Luca Cardelli\| issue=4es\| s2cid=12105785}}</ref>		Richard Feldman says that, while OOP features helped some languages stay organized, their popularity comes from other reasons.<ref>{{cite web \|last1=Feldman \|first1=Richard \|title=Why Isn't Functional Programming the Norm? \|website=[[YouTube]] \|date=30 September 2019 \|url=https://www.youtube.com/watch?v=QyJZzq0v7Z4&t=2069s \|language=en}}</ref> Lawrence Krubner argues that OOP doesn't offer special advantages compared to other styles, like functional programming, and can make coding more complicated.<ref name="lawrence">{{Cite web\| last=Krubner\| first=Lawrence\| title=Object Oriented Programming is an expensive disaster which must end\| url=http://www.smashcompany.com/technology/object-oriented-programming-is-an-expensive-disaster-which-must-end\| publisher=smashcompany.com\| access-date=14 October 2014\| archive-url=https://web.archive.org/web/20141014233854/http://www.smashcompany.com/technology/object-oriented-programming-is-an-expensive-disaster-which-must-end\| archive-date=14 October 2014\| url-status=dead}}</ref> [[Luca Cardelli]] says that OOP is slower and takes longer to compile than procedural programming.<ref name="badprop">{{Cite journal\| first=Luca\| last=Cardelli\|title=Bad Engineering Properties of Object-Oriented Languages \|url=http://lucacardelli.name/Papers/BadPropertiesOfOO.html\| year=1996\| access-date=21 April 2010\| doi=10.1145/242224.242415\| journal = ACM Comput. Surv.\| volume=28\| issn = 0360-0300\| pages = 150–es\| author-link=Luca Cardelli\| issue=4es\| s2cid=12105785\| url-access=subscription}}</ref>

	===OOP in dynamic languages===		===OOP in dynamic languages===

The Sophocrat: Undid revision 1291279103, an unconstructive edit by 94.205.112.36 (talk)

2025-05-20T06:02:06Z

Undid revision 1291279103, an unconstructive edit by 94.205.112.36 (talk)

← Previous revision		Revision as of 06:02, 20 May 2025
Line 358:		Line 358:
	{{Reflist}}		{{Reflist}}

	==~~Furthereading~~==		==Further reading==
	* {{Cite book		* {{Cite book
	\|first=Martin		\|first=Martin

94.205.112.36: /* Furthereading */

2025-05-20T06:00:16Z

Furthereading

← Previous revision		Revision as of 06:00, 20 May 2025
Line 358:		Line 358:
	{{Reflist}}		{{Reflist}}

	==~~Further reading~~==		==Furthereading==
	* {{Cite book		* {{Cite book
	\|first=Martin		\|first=Martin

MrOllie: Reverted 1 edit by 1.46.93.98 (talk) to last revision by Citation bot

2025-04-20T00:55:52Z

Reverted 1 edit by 1.46.93.98 (talk) to last revision by Citation bot

← Previous revision		Revision as of 00:55, 20 April 2025
Line 1:		Line 1:
	{{short description\|Programming paradigm based on the concept of objects~~แปลภาษาไทยgoogle.com.mmm~~}}		{{short description\|Programming paradigm based on the concept of objects}}
	{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}		{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}
	{{Use dmy dates\|date=January 2020}}		{{Use dmy dates\|date=January 2020}}

1.46.93.98: Updated short description

2025-04-20T00:33:50Z

Updated short description

← Previous revision		Revision as of 00:33, 20 April 2025
Line 1:		Line 1:
	{{short description\|Programming paradigm based on the concept of objects}}		{{short description\|Programming paradigm based on the concept of objectsแปลภาษาไทยgoogle.com.mmm}}
	{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}		{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}
	{{Use dmy dates\|date=January 2020}}		{{Use dmy dates\|date=January 2020}}

Citation bot: Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Linked from User:LinguisticMystic/cs/outline | #UCB_webform_linked 1449/2277

2025-04-17T03:27:57Z

Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Linked from User:LinguisticMystic/cs/outline | #UCB_webform_linked 1449/2277

← Previous revision		Revision as of 03:27, 17 April 2025
Line 319:		Line 319:
	* [[Dependency inversion principle]]: Depend upon abstractions, not concretes.		* [[Dependency inversion principle]]: Depend upon abstractions, not concretes.

	[[GRASP (object-oriented design)\|GRASP]] (General Responsibility Assignment Software Patterns) is another set of software design rules, created by [[Craig Larman]], that helps developers assign responsibilities to different parts of a program:<ref>{{Cite web \|last=Karsh \|first=Patrick \|date=Jul 19, 2023 \|title=GRASP Principles: Object-Oriented Design Patterns \|url=https://patrickkarsh.medium.com/object-oriented-design-with-grasp-principles-8049fa63e52 ~~\|url-status=live~~ \|access-date=Mar 30, 2025 \|website=Medium}}</ref>		[[GRASP (object-oriented design)\|GRASP]] (General Responsibility Assignment Software Patterns) is another set of software design rules, created by [[Craig Larman]], that helps developers assign responsibilities to different parts of a program:<ref>{{Cite web \|last=Karsh \|first=Patrick \|date=Jul 19, 2023 \|title=GRASP Principles: Object-Oriented Design Patterns \|url=https://patrickkarsh.medium.com/object-oriented-design-with-grasp-principles-8049fa63e52 \|access-date=Mar 30, 2025 \|website=Medium}}</ref>

	* Creator Principle: allows classes create objects they closely use.		* Creator Principle: allows classes create objects they closely use.

Ryan Behrend: I added details about the GRASP Principles

2025-03-31T01:31:35Z

I added details about the GRASP Principles

← Previous revision		Revision as of 01:31, 31 March 2025
Line 319:		Line 319:
	* [[Dependency inversion principle]]: Depend upon abstractions, not concretes.		* [[Dependency inversion principle]]: Depend upon abstractions, not concretes.

	[[GRASP (object-oriented design)\|GRASP]] (General Responsibility Assignment Software Patterns) is another set of software design rules, created by [[Craig Larman]], that helps developers assign responsibilities to different parts of a program.		[[GRASP (object-oriented design)\|GRASP]] (General Responsibility Assignment Software Patterns) is another set of software design rules, created by [[Craig Larman]], that helps developers assign responsibilities to different parts of a program:<ref>{{Cite web \|last=Karsh \|first=Patrick \|date=Jul 19, 2023 \|title=GRASP Principles: Object-Oriented Design Patterns \|url=https://patrickkarsh.medium.com/object-oriented-design-with-grasp-principles-8049fa63e52 \|url-status=live \|access-date=Mar 30, 2025 \|website=Medium}}</ref>

			* Creator Principle: allows classes create objects they closely use.
			* Information Expert Principle: assigns tasks to classes with the needed information.
			* Low Coupling Principle: reduces class dependencies to improve flexibility and maintainability.

			* High Cohesion Principle: designing classes with a single, focused responsibility.
			* Controller Principle: assigns system operations to separate classes that manage flow and interactions.
			* Polymorphism: allows different classes to be used through a common interface, promoting flexibility and reuse.
			* Pure Fabrication Principle: create helper classes to improve design, boost cohesion, and reduce coupling.

	==Formal semantics==		==Formal semantics==

MrOllie: Reverted 1 edit by 197.184.169.61 (talk) to last revision by Citation bot

2025-03-21T14:01:39Z

Reverted 1 edit by 197.184.169.61 (talk) to last revision by Citation bot

@@ Line 547: / Line 547: @@
 ==External links==
 {{DEFAULTSORT:Object-Oriented Programming}}
 [[Category:Object-oriented programming| ]]

197.184.169.61 at 14:00, 21 March 2025

2025-03-21T14:00:29Z

@@ Line 547: / Line 547: @@
 ==External links==
 {{DEFAULTSORT:Object-Oriented Programming}}
 [[Category:Object-oriented programming| ]]

← Previous revision		Revision as of 00:55, 20 April 2025
Line 1:		Line 1:
	{{short description\|Programming paradigm based on the concept of objects~~แปลภาษาไทยgoogle.com.mmm~~}}		{{short description\|Programming paradigm based on the concept of objects}}
	{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}		{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}
	{{Use dmy dates\|date=January 2020}}		{{Use dmy dates\|date=January 2020}}

← Previous revision		Revision as of 00:33, 20 April 2025
Line 1:		Line 1:
	{{short description\|Programming paradigm based on the concept of objects}}		{{short description\|Programming paradigm based on the concept of objectsแปลภาษาไทยgoogle.com.mmm}}
	{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}		{{Redirect\|Object-oriented\|other meanings of object-oriented\|Object-orientation (disambiguation){{!}}Object-orientation}}
	{{Use dmy dates\|date=January 2020}}		{{Use dmy dates\|date=January 2020}}