Programming model - Revision history

85.92.168.90: /* References */

2025-03-17T12:02:15Z

References

← Previous revision		Revision as of 12:02, 17 March 2025
Line 18:		Line 18:
	\| author = Barcelona Supercomputing Center		\| author = Barcelona Supercomputing Center
	}}</ref>		}}</ref>


	==References==		==References==

AntiCompositeNumber: Added {{More citations needed}} tag

2025-01-18T23:03:16Z

Added {{More citations needed}} tag

← Previous revision		Revision as of 23:03, 18 January 2025
Line 2:		Line 2:
	{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}		{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}

			{{More citations needed\|date=January 2025}}
	A '''programming model''' is an [[execution model]] coupled to an [[API]] or a particular pattern of code. In this style, there are actually two execution models in play: the execution model of the base [[programming language]] and the execution model of the programming model. An example is [[Apache_Spark\|Spark]] where [[Java_language\| Java]] is the base language, and Spark is the programming model. Execution may be based on what appear to be [[Programming library\|library]] calls. Other examples include the [[POSIX Threads]] library and Hadoop's [[MapReduce]].<ref>{{cite web		A '''programming model''' is an [[execution model]] coupled to an [[API]] or a particular pattern of code. In this style, there are actually two execution models in play: the execution model of the base [[programming language]] and the execution model of the programming model. An example is [[Apache_Spark\|Spark]] where [[Java_language\| Java]] is the base language, and Spark is the programming model. Execution may be based on what appear to be [[Programming library\|library]] calls. Other examples include the [[POSIX Threads]] library and Hadoop's [[MapReduce]].<ref>{{cite web
	\| url = https://www.ibm.com/analytics/hadoop/mapreduce		\| url = https://www.ibm.com/analytics/hadoop/mapreduce

Jessica22664: Importing Wikidata short description: "Area of research"

2025-01-18T21:15:47Z

Importing Wikidata short description: "Area of research"

← Previous revision		Revision as of 21:15, 18 January 2025
Line 1:		Line 1:
			{{Short description\|Area of research}}
	{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}		{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}

DB1729: Restored revision 1164512825 by DanCherek (talk): Restore better version

2024-09-19T04:21:06Z

Restored revision 1164512825 by DanCherek (talk): Restore better version

← Previous revision		Revision as of 04:21, 19 September 2024
Line 1:		Line 1:
	{{Short description\|TOS Model}}
	{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}		{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}

Line 12:		Line 11:
	What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.		What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

	In [[parallel computing]], the execution model often done via parallel programming models rather than parallel languages. The terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web		In [[parallel computing]], the execution model often must expose features of the hardware in order to achieve high performance. The large amount of variation in parallel hardware causes a concurrent need for a similarly large number of parallel execution models. It is impractical to make a new language for each execution model, hence it is a common practice to invoke the behaviors of the parallel execution model via an API. So, most of the programming effort is done via parallel programming models rather than parallel languages. The terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web
	\| url = http://compss.bsc.es/		\| url = http://compss.bsc.es/
	\| title = COMP Superscalar Programming Model		\| title = COMP Superscalar Programming Model

2600:6C58:F0:1410:2D80:5516:A3F7:23F0: Added short description

2024-09-19T00:04:09Z

Added short description

← Previous revision		Revision as of 00:04, 19 September 2024
Line 1:		Line 1:
			{{Short description\|TOS Model}}
	{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}		{{About\| the definition of the term 'programming model'\| classification of programming languages\| Programming paradigm}}

2806:108E:11:E595:D673:9B82:F050:B8B: [{"MMS":{"_id":"1","thread_id":"3","date":"1704082775","date_sent":"170 4082775","msg_box":"1","read":"1","m_id":"7dea52d0-c02f-4c32-859c-c5002 135b06a","sub":"","sub_cs":"106","ct_t":"text\/plain","m_type":"132","m _size":"0","tr_id":"proto:Co4BCiJjb20uZ29vZ2xlLmFuZHJvaWQuYXBwcy5tZXNzY WdpbmcuEmgSZho+CiJ0ZWxjZWwtYWRlbGFudGEtbWVnYXMtcmNzQHJibS5nb29nEg9BZGVs YW50YSBUZWxjZWwaByMzNzQ3NEYqJDdkZWE1MmQwLWMwMmYtNGMzMi04NTljLWM1MDAyMTM 1YjA2YQ==","ct_cls":"135","locked":"0","sub_id":"1","seen":"1","crea

2024-08-11T02:21:24Z

[{"MMS":{"_id":"1","thread_id":"3","date":"1704082775","date_sent":"170 4082775","msg_box":"1","read":"1","m_id":"7dea52d0-c02f-4c32-859c-c5002 135b06a","sub":"","sub_cs":"106","ct_t":"text\/plain","m_type":"132","m _size":"0","tr_id":"proto:Co4BCiJjb20uZ29vZ2xlLmFuZHJvaWQuYXBwcy5tZXNzY WdpbmcuEmgSZho+CiJ0ZWxjZWwtYWRlbGFudGEtbWVnYXMtcmNzQHJibS5nb29nEg9BZGVs YW50YSBUZWxjZWwaByMzNzQ3NEYqJDdkZWE1MmQwLWMwMmYtNGMzMi04NTljLWM1MDAyMTM 1YjA2YQ==","ct_cls":"135","locked":"0","sub_id":"1","seen":"1","crea

← Previous revision		Revision as of 02:21, 11 August 2024
Line 11:		Line 11:
	What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.		What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

	In [[parallel computing]], the execution model often must expose features of the hardware in order to achieve high performance. The large amount of variation in parallel hardware causes a concurrent need for a similarly large number of parallel execution models. It is impractical to make a new language for each execution model, hence it is a common practice to invoke the behaviors of the parallel execution model via an API. So, most of the programming effort is done via parallel programming models rather than parallel languages. The terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web		In [[parallel computing]], the execution model often done via parallel programming models rather than parallel languages. The terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web
	\| url = http://compss.bsc.es/		\| url = http://compss.bsc.es/
	\| title = COMP Superscalar Programming Model		\| title = COMP Superscalar Programming Model

DanCherek: /* top */ remove editorializing

2023-07-09T15:32:00Z

top: remove editorializing

← Previous revision		Revision as of 15:32, 9 July 2023
Line 11:		Line 11:
	What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.		What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

	In [[parallel computing]], the execution model often must expose features of the hardware in order to achieve high performance. The large amount of variation in parallel hardware causes a concurrent need for a similarly large number of parallel execution models. It is impractical to make a new language for each execution model, hence it is a common practice to invoke the behaviors of the parallel execution model via an API. So, most of the programming effort is done via parallel programming models rather than parallel languages. ~~Unfortunately, the~~ terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web		In [[parallel computing]], the execution model often must expose features of the hardware in order to achieve high performance. The large amount of variation in parallel hardware causes a concurrent need for a similarly large number of parallel execution models. It is impractical to make a new language for each execution model, hence it is a common practice to invoke the behaviors of the parallel execution model via an API. So, most of the programming effort is done via parallel programming models rather than parallel languages. The terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web
	\| url = http://compss.bsc.es/		\| url = http://compss.bsc.es/
	\| title = COMP Superscalar Programming Model		\| title = COMP Superscalar Programming Model

74.73.224.126: Undid revision 1160265530 by 2402:8100:279C:CCAD:686E:8081:E161:7626 (talk)

2023-06-15T17:33:51Z

Undid revision 1160265530 by 2402:8100:279C:CCAD:686E:8081:E161:7626 (talk)

← Previous revision		Revision as of 17:33, 15 June 2023
Line 7:		Line 7:
	\| website = [[IBM]]		\| website = [[IBM]]
	\|access-date=2020-04-19		\|access-date=2020-04-19
	}}</ref> In both cases, the [[execution model]] of the programming model is ~~free~~ different from that of the base language in which the code is written. For ~~with~~ ~~exampe~~		}}</ref> In both cases, the [[execution model]] of the programming model is different from that of the base language in which the code is written. For example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.
	example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.

	What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.		What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

2402:8100:279C:CCAD:686E:8081:E161:7626 at 11:33, 15 June 2023

2023-06-15T11:33:35Z

← Previous revision		Revision as of 11:33, 15 June 2023
Line 7:		Line 7:
	\| website = [[IBM]]		\| website = [[IBM]]
	\|access-date=2020-04-19		\|access-date=2020-04-19
	}}</ref> In both cases, the [[execution model]] of the programming model is different from that of the base language in which the code is written. For example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.		}}</ref> In both cases, the [[execution model]] of the programming model is free different from that of the base language in which the code is written. For with exampe
			example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.

	What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.		What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

Citation bot: Add: website. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_toolbar

2022-05-03T18:06:23Z

Add: website. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_toolbar

← Previous revision		Revision as of 18:06, 3 May 2022
Line 5:		Line 5:
	\| title = What is MapReduce		\| title = What is MapReduce
	\| author = IBM		\| author = IBM
			\| website = [[IBM]]
	\|access-date=2020-04-19		\|access-date=2020-04-19
	}}</ref> In both cases, the [[execution model]] of the programming model is different from that of the base language in which the code is written. For example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.		}}</ref> In both cases, the [[execution model]] of the programming model is different from that of the base language in which the code is written. For example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But such behavior can be invoked from C syntax, by making what appears to be a call to a normal C library.